using-medusa-cloud — Claude Code skill for Medusa Cloud deploys
A skill that teaches an agent to run Medusa Cloud through the mcloud CLI: deploys, failed builds, environments, variables. Useful for CI/CD work.
npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a claude-codeWhat using-medusa-cloud does
The skill is an operational guide for agents touching Medusa Cloud infrastructure via mcloud. It ships with three reference files: setup.md for CLI install and auth, debugging-deployments.md for failure recipes and log analysis, environments-and-variables.md for environment lifecycle and variables. The agent loads the matching file before any multi-step workflow.
Deployment status routes the debugging. build-failed sends you to mcloud deployments build-logs <id>. deployment-failed means the runtime crashed after a good build, so read mcloud logs --deployment <id>. timed-out needs both, build logs first. A second table picks between mcloud environments redeploy <env> for environment-side fixes and mcloud environments trigger-build <env> when the source branch changed.
The constraints matter more than the recipes. mcloud login, mcloud use without flags, and delete without --yes all need a TTY, so they break in CI, Docker, or piped input. Variable changes do not apply on their own: after variables set or variables delete you still need a redeploy or a new build. Production environments cannot be deleted at all. And --json does not combine with --follow, so programmatic log ingestion wants bounded --from/--to windows instead.
What it helps with
- find out why a Medusa Cloud build failed
- switch context to the right organization and environment
- apply environment variables after editing them
- decide between redeploy and trigger-build
- reproduce a build-failed run locally with
mcloud local build
Example prompts for the agent
- check the build logs of the last deployment and tell me what broke
- deploy the current changes to production and report the status
- set this environment variable and restart the runtime
How to install using-medusa-cloud
1Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a claude-code2Manually: put the files in place
~/.claude/skills/using-medusa-cloud/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/using-medusa-cloud/
1Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a codex2Manually: put the files in place
.agents/skills/using-medusa-cloud/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a cursor2Manually: put the files in place
.cursor/skills/using-medusa-cloud/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install medusajs/medusa-agent-skills using-medusa-cloud2Manually: put the files in place
.github/skills/using-medusa-cloud/SKILL.md1Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a gemini-cli2Platform CLI
gemini skills install https://github.com/medusajs/medusa-agent-skills --path plugins/medusa-cloud/skills/using-medusa-cloudManually: put the files in place
.devin/skills/using-medusa-cloud/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -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 using-medusa-cloud
How do I install using-medusa-cloud in Claude?
Run npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a claude-code. The skill lands at ~/.claude/skills/using-medusa-cloud/SKILL.md.
What does using-medusa-cloud do?
It gives an agent the rules for managing Medusa Cloud resources through the mcloud CLI: deployments, environments, variables, log analysis, and CI/CD workflows.
Why does mcloud use fail in CI?
Without flags the command is interactive and needs a TTY. Pass --organization, --project, and --environment explicitly.
