From claw-ops
Deploy any Claw fleet bot. Use when user says 'deploy', 'push to production', 'update bot', 'release', 'ship it', or mentions deploying DB, Nook, Lettabot, NanoClaw, or M-Bot.
How this skill is triggered — by the user, by Claude, or both
Slash command
/claw-ops:bot-deployThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Deploy any bot in the Claw fleet to its target environment.
Deploy any bot in the Claw fleet to its target environment.
Determine which bot to deploy from user context. Look up the bot in references/bot-deploy-profiles.md to get:
If the user does not specify a bot, ask. Do not guess.
Run any pre-deploy checks listed in the bot's profile. If a check fails, stop and report the failure. Do not proceed with a broken build.
Load the matching transport reference file:
references/transport-docker-compose.md -- DB, M-Botreferences/transport-rsync.md -- Nookreferences/transport-railway.md -- Lettabotreferences/transport-container-build.md -- NanoClawFollow the transport guide step by step. Do not skip steps.
Run the deploy commands from the transport guide. Show each command and its output. If any command fails, stop and diagnose before continuing.
Run the post-deploy check from the bot's profile. Use /bot-health if available, or the custom check specified in the profile. Confirm the bot is alive and responding.
Summarize:
npx claudepluginhub thamam/clawhub-marketplace --plugin claw-opsPerforms first-time setup of a ClaudeClaw instance: installs dependencies, authenticates messaging channels, registers the main channel, and starts background services.
Guides reliable deployments in environments without CI/CD platforms using shell scripts, blue-green switching, smoke tests, and rollback.
Deploys apps to Render by analyzing codebases, generating render.yaml blueprints, and providing dashboard deeplinks. For Git-backed services, Docker images, databases, and cron jobs.