sealos-deploy — Claude Code skill: what it does, how to install
Deploys workspace code to Sealos Cloud from a Brain Devbox sandbox using MCP tools. Needed when running in SEALAI_DEPLOY_MODE=managed.
npx skills add labring/sealos-skills --skill sealos-deploy -a claude-codeWhat sealos-deploy does
The skill functions as the executor half of a deployment pipeline managed by Brain on Sealos Cloud. It activates strictly when SEALAI_DEPLOY_MODE is set to managed or when explicitly called. The agent reviews the project, pulls store templates for standard apps, or builds custom code with Kaniko without needing a local Docker daemon.
All configurations write to $SEALAI_DEPLOY_WORKSPACE/.sealos/template/index.yaml under the app.sealos.io/v1/Template specification. Custom user inputs are declared under spec.inputs so the Brain platform collects them through its own forms. The workflow stays non-interactive: the agent calculates the SHA-256 digest of the manifest and triggers the template_ready MCP tool to hand over control.
Execution stops immediately with a fatal error if either template_ready or deployment_completed MCP tools are missing. Outside a Brain Devbox sandbox, standard deployments should use the sibling use-sealos skill instead.
What it helps with
- build container images with Kaniko without a Docker daemon
- generate canonical templates at .sealos/template/index.yaml
- coordinate non-interactive deployments with Brain via MCP tools
- deploy sandbox workspaces into a target Sealos namespace
Example prompts for the agent
- /sealos-deploy
- Deploy the current workspace to Sealos using the managed pipeline
- Run the managed deployment executor for this Brain Devbox project
How to install sealos-deploy
1Skills CLI (Vercel)
npx skills add labring/sealos-skills --skill sealos-deploy -a claude-code2Manually: put the files in place
~/.claude/skills/sealos-deploy/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/sealos-deploy/
1Skills CLI (Vercel)
npx skills add labring/sealos-skills --skill sealos-deploy -a codex2Manually: put the files in place
.agents/skills/sealos-deploy/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add labring/sealos-skills --skill sealos-deploy -a cursor2Manually: put the files in place
.cursor/skills/sealos-deploy/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install labring/sealos-skills sealos-deploy2Manually: put the files in place
.github/skills/sealos-deploy/SKILL.md1Skills CLI (Vercel)
npx skills add labring/sealos-skills --skill sealos-deploy -a gemini-cli2Platform CLI
gemini skills install https://github.com/labring/sealos-skills --path plugins/sealos/skills/sealos-deployManually: put the files in place
.devin/skills/sealos-deploy/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add labring/sealos-skills --skill sealos-deploy -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about sealos-deploy
How to install sealos-deploy in Claude Code?
Run npx skills add labring/sealos-skills --skill sealos-deploy -a claude-code. The file will be placed in ~/.claude/skills/sealos-deploy/SKILL.md.
What does sealos-deploy do?
It classifies workspace code, handles Kaniko container builds, generates Sealos deployment manifests, and orchestrates the release via Brain MCP tools.
When should you use sealos-deploy instead of use-sealos?
Use sealos-deploy only when SEALAI_DEPLOY_MODE is set to managed inside a Brain Devbox sandbox. For manual or local deployments, use use-sealos.
