buddy — Claude Code skill: deploy and CI/CD via bdy CLI
A skill that teaches your agent to drive Buddy cloud through bdy: sandboxes, artifacts, tunnels, domains and pipelines.
npx skills add buddy/buddy-plugin --skill buddy -a claude-codeWhat buddy does
The skill hands the agent a working map of the Buddy platform, reached through the bdy command line. Sandboxes come first: create one, copy the project over, install dependencies, then start the app as a managed service so you get status, logs and restarts instead of a bare process. Other sections cover artifacts — BUCKET for static sites and build output, CONTAINER for Docker images — plus tunnels, domains, distributions and CI/CD pipelines.
Some rules are non-negotiable. An app inside a sandbox has to bind to 0.0.0.0; on 127.0.0.1 the endpoint simply won't answer. Project copies should skip node_modules and .git and let the sandbox install packages itself. A static site needs its entry file named index.html, or visitors get a directory listing. Tunnel commands hold the terminal, so they belong in the background.
Login stays with you. The agent can't walk through interactive OAuth, so when a command answers Token not provided or Not logged in, run bdy login yourself in a separate terminal. The same goes for bdy artifact docker login before pushing images. bdy whoami shows whether the session is alive, and the skill also reads it to find the project context — a sandbox can't exist outside a project.
What it helps with
- spin up a cloud sandbox and run an app in it
- publish a build as an artifact with a public URL
- expose a local service to the internet through a tunnel
- point a custom domain at a service or artifact
- start a CI/CD pipeline and read its run logs
Example prompts for the agent
- Deploy this app to a Buddy sandbox and show me the public URL
- Publish the
distfolder as artifact[email protected] - Open a tunnel to
localhost:3000with HTTP Basic Auth
How to install buddy
1Skills CLI (Vercel)
npx skills add buddy/buddy-plugin --skill buddy -a claude-code2Manually: put the files in place
~/.claude/skills/buddy/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/buddy/
1Skills CLI (Vercel)
npx skills add buddy/buddy-plugin --skill buddy -a codex2Manually: put the files in place
.agents/skills/buddy/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add buddy/buddy-plugin --skill buddy -a cursor2Manually: put the files in place
.cursor/skills/buddy/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install buddy/buddy-plugin buddy2Manually: put the files in place
.github/skills/buddy/SKILL.md1Skills CLI (Vercel)
npx skills add buddy/buddy-plugin --skill buddy -a gemini-cli2Platform CLI
gemini skills install https://github.com/buddy/buddy-plugin --path skills/buddyManually: put the files in place
.devin/skills/buddy/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add buddy/buddy-plugin --skill buddy -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 buddy
How do I install buddy in Claude Code?
Run npx skills add buddy/buddy-plugin --skill buddy -a claude-code. The skill lands at ~/.claude/skills/buddy/SKILL.md.
What does the buddy skill do?
It gives the agent instructions for the bdy CLI: sandboxes, artifacts, tunnels, domains, distributions and CI/CD pipelines.
Why do commands return "Token not provided"?
The agent can't complete interactive OAuth. Run bdy login in a separate terminal and check the session with bdy whoami.
