mcloud-environments
Execute mcloud environments commands to list, get, create, delete, redeploy, or trigger builds for Cloud environments. Use when managing environment lifecycle, redeploying after variable changes, or starting new builds from source.
- Installs
- 1.3K
- Last 24h
- +14
- Trending rank
- #7138
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/medusajs/medusa-agent-skills --skill mcloud-environments- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads mcloud-environments automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Cloud CLI: Environments Commands
Execute mcloud environments commands to manage environment lifecycle and deployments.
Constraints
- Production environments cannot be deleted. Always check
typeviaenvironments get --jsonbefore attempting delete in automation. - Use
--yesfor destructive operations (delete) in non-interactive contexts. redeployvstrigger-buildare not interchangeable — choose the right one based on where the fix is.
Commands
environments list
List all environments in a project.
mcloud environments list --organization <org-id> --project <project-id-or-handle> --json
Options:
-o/--organization <id>— Organization ID (falls back to active context)-p/--project <id-or-handle>— Project ID or handle (falls back to active context)--json— Output as JSON
environments get
Retrieve a single environment by its ID or handle.
mcloud environments get <environment-id-or-handle> --organization <org-id> --project <project-id-or-handle> --json
Arguments:
environment— Environment ID or handle (required)
Options:
-o/--organization <id>,-p/--project <id-or-handle>,--json
environments create
Create a new long-lived environment.
mcloud environments create \
--organization <org-id> \
--project <project-id-or-handle> \
--name "Staging" \
--branch develop \
--json
Options:
-o/--organization <id>,-p/--project <id-or-handle>-n/--name <name>— Environment name (required)-b/--branch <branch>— Git branch to track (required)--custom-subdomain <subdomain>— Optional custom subdomain--json— Output as JSON
environments delete
Delete an environment. Cannot delete production environments.
mcloud environments delete <environment-id-or-handle> \
--organization <org-id> \
--project <project-id-or-handle> \
--yes
Arguments:
environment— Environment ID or handle (required)
Options:
-o/--organization <id>,-p/--project <id-or-handle>-y/--yes— Skip confirmation prompt (required in non-interactive mode)--json— Output as JSON
environments redeploy
Re-run an existing build for the active deployment. Use when the fix is environment-side (variable change, infra issue) — does NOT start a new build.
mcloud environments redeploy <environment-id-or-handle> \
--organization <org-id> \
--project <project-id-or-handle> \
--json
Arguments:
environment— Environment ID or handle (required)
Options:
-o/--organization <id>,-p/--project <id-or-handle>,--json
Requires the environment to have an active deployment. If it doesn't, use
trigger-buildfirst.
environments trigger-build
Start a new build from the tracked branch. Use when the fix is committed code — creates a new deployment.
mcloud environments trigger-build <environment-id-or-handle> \
--organization <org-id> \
--project <project-id-or-handle> \
--json
Arguments:
environment— Environment ID or handle (required)
Options:
-o/--organization <id>,-p/--project <id-or-handle>,--json
Redeploy vs Trigger-Build Decision
| Command | When to use |
|---|---|
redeploy | Fix is environment-side (variable change, infra config) — reruns existing build |
trigger-build | Fix is in source code on the tracked branch — starts a new build |
Examples
# List all environments
mcloud environments list --json
# Get environment details and check type before deleting
mcloud environments get staging --json | jq '{id, name, type, status}'
# Create a new environment tracking the develop branch
mcloud environments create --name "Staging" --branch develop --json
# Delete a non-production environment
mcloud environments delete staging --yes
# Redeploy after a variable change
mcloud environments redeploy production --json
# Trigger a fresh build from source
mcloud environments trigger-build production --json
# Find environment handles by name
mcloud environments list --json \
| jq -r '.[] | select(.name == "Production") | .handle'
# Verify new build started
mcloud deployments list --environment production --limit 5 --json \
| jq '.[] | {id, backend_status, updated_at}'
FAQ
What does the mcloud-environments skill do?
Execute mcloud environments commands to list, get, create, delete, redeploy, or trigger builds for Cloud environments. Use when managing environment lifecycle, redeploying after variable changes, or starting new builds from source.
How do I install mcloud-environments?
Run npx skills add https://github.com/medusajs/medusa-agent-skills --skill mcloud-environments in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/mcloud-environments/ (personal) or .claude/skills/mcloud-environments/ (project).
Which AI agents can use mcloud-environments?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is mcloud-environments safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains mcloud-environments?
It is published by medusajs in medusajs/medusa-agent-skills, and it is an official skill from the maker of the technology it covers. It has 1,333 recorded installs.
More from medusajs/medusa-agent-skills
storefront-best-practices
medusajs/medusa-agent-skills
ALWAYS use this skill when working on ecommerce storefronts, online stores, shopping sites. Use for ANY storefront component including checkout pages, cart, payment flows, product pages, product listings, navigation, homepage, or ANY page/component in a storefront. CRITICAL for adding checkout, implementing cart, integrating Medusa backend, making a store agent-friendly for AI shopping agents, or building any ecommerce functionality. Framework-agnostic (Next.js, SvelteKit, TanStack Start, React, Vue). Provides patterns, decision frameworks, backend integration guidance.
building-with-medusa
medusajs/medusa-agent-skills
Load automatically when planning, researching, or implementing ANY Medusa backend features (custom modules, API routes, workflows, data models, module links, business logic). REQUIRED for all Medusa backend work in ALL modes (planning, implementation, exploration). Contains architectural patterns, best practices, and critical rules that MCP servers don't provide.
building-admin-dashboard-customizations
medusajs/medusa-agent-skills
Load automatically when planning, researching, or implementing Medusa Admin dashboard UI (widgets, custom pages, forms, tables, data loading, navigation). REQUIRED for all admin UI work in ALL modes (planning, implementation, exploration). Contains design patterns, component usage, and data loading patterns that MCP servers don't provide.
building-storefronts
medusajs/medusa-agent-skills
Load automatically when planning, researching, or implementing Medusa storefront features (calling custom API routes, SDK integration, React Query patterns, data fetching). REQUIRED for all storefront development in ALL modes (planning, implementation, exploration). Contains SDK usage patterns, frontend integration, and critical rules for calling Medusa APIs.
db-migrate
medusajs/medusa-agent-skills
Run database migrations in Medusa
db-generate
medusajs/medusa-agent-skills
Generate database migrations for a Medusa module
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available