hummingbot-deploy

What This Skill Does

The hummingbot-deploy skill is a specialized automation tool designed for the OpenClaw AI agent to manage the lifecycle of your Hummingbot trading infrastructure. It automates the deployment of the Hummingbot API, the Hummingbot MCP server (for integration with AI assistants), and the Condor terminal/Telegram UI. By leveraging this skill, you move from manual environment configuration to a streamlined, agent-driven deployment process that handles complex dependency checks, Docker network configuration, and secure credential setup.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/fengtality/hummingbot-deploy

Before initiating, ensure your system meets the requirements: Docker, Docker Compose, Git, and Make. The agent will first run a mandatory environment check script. For fresh installations, it clones the repository, sets up environment variables (handling both TTY and non-TTY containerized environments), and executes the deployment sequence. If the API is already installed, the agent will verify existing logs for 'Uvicorn running' before deciding whether to proceed with a fresh redeployment.

Use Cases

This skill is perfect for algorithmic traders who need to initialize a headless trading server in the cloud, developers building agents that require real-time market data access via the Hummingbot API, and users who want a unified command-line and Telegram interface to manage their Hummingbot bots across multiple exchanges.

Example Prompts

1. "OpenClaw, please deploy the complete Hummingbot infrastructure for me, including the Condor Telegram bot."
2. "I need to set up a new Hummingbot API server on this container. Can you handle the deployment?"
3. "Check if my Hummingbot API is running correctly and reinstall it if it is not responding."

Tips & Limitations

Always check your API_PASS and CONFIG_API_PASS credentials after deployment. When deploying in a non-interactive container, the skill automatically generates a standard .env file; ensure you update these values for production security. Note that while this skill streamlines deployment, you remain responsible for your exchange API keys. Ensure that your Docker environment has sufficient permissions to mount volumes for bot configurations, as the BOTS_PATH needs persistent storage to avoid losing strategy states during container updates.