mcloud-environments — Claude Code skill: manage environments
Manage mcloud environments from your agent: inspect, create, or remove them, then rerun a deployment or start a fresh build. Useful when changing environment settings or shipping committed code.
npx skills add medusajs/medusa-agent-skills --skill mcloud-environments -a claude-codeWhat mcloud-environments does
The skill runs mcloud environments commands to list project environments, retrieve one environment’s details, create a long-lived environment linked to a Git branch, or delete an environment. Non-interactive deletion uses --yes. Production environments cannot be deleted, so check the environment type before attempting that operation.
Choose redeploy when the change is in the environment, such as updated variables or infrastructure configuration. It reruns the existing build and requires an active deployment. For committed changes on the tracked branch, trigger-build starts a new build and creates a deployment. The commands also support JSON output.
What it helps with
- list project environments
- inspect an environment by ID or handle
- create an environment linked to a Git branch
- rerun a deployment after changing variables
- start a fresh build from committed code
Example prompts for the agent
- List this project’s environments as JSON.
- Create a
Stagingenvironment that tracksdevelop. - Redeploy
productionafter its variables change; start a new build if the fix is in the tracked code.
How to install mcloud-environments
1Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill mcloud-environments -a claude-code2Manually: put the files in place
~/.claude/skills/mcloud-environments/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/mcloud-environments/
1Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill mcloud-environments -a codex2Manually: put the files in place
.agents/skills/mcloud-environments/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill mcloud-environments -a cursor2Manually: put the files in place
.cursor/skills/mcloud-environments/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install medusajs/medusa-agent-skills mcloud-environments2Manually: put the files in place
.github/skills/mcloud-environments/SKILL.md1Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill mcloud-environments -a gemini-cli2Platform CLI
gemini skills install https://github.com/medusajs/medusa-agent-skills --path plugins/medusa-cloud/skills/mcloud-environmentsManually: put the files in place
.devin/skills/mcloud-environments/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add medusajs/medusa-agent-skills --skill mcloud-environments -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 mcloud-environments
How do I install mcloud-environments in Claude Code?
Run npx skills add medusajs/medusa-agent-skills --skill mcloud-environments -a claude-code. The skill file is located at ~/.claude/skills/mcloud-environments/SKILL.md.
What does mcloud-environments do?
It runs mcloud commands to inspect, create, and delete environments, rerun an existing deployment, or start a new build.
When should I use redeploy instead of trigger-build?
Use redeploy for environment-side changes; an active deployment is required. Use trigger-build for code changes on the tracked branch, which start a new build.
