New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

mcloud Environments

by medusajs in medusajs/medusa-agent-skills

Runs mcloud environments commands to list, inspect, create, delete, redeploy or rebuild environments in Medusa Cloud projects.

No licenceAuto-check passedDevOps & Cloud

Install mcloud Environments

skills CLI
$ npx skills add medusajs/medusa-agent-skills --skill mcloud-environments -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install medusajs/medusa-agent-skills mcloud-environments --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/medusajs/medusa-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/medusa-cloud/skills/mcloud-environments .claude/skills/mcloud-environments && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
mcloud-environments
GitHub stars
225
Token cost
~1.2k tokens
SKILL.md length
302 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
None found

At a glance

Runs mcloud environments commands to list, inspect, create, delete, redeploy or rebuild environments in Medusa Cloud projects.

  • Listing the environments in a project
  • SKILL.md covers Constraints, Commands, Redeploy vs Trigger-Build… and Examples
  • Calls jq
  • Redeploying after changing an environment variable

What it does

Wraps the mcloud environments command group for managing the life of an environment: list, get, create, delete, redeploy and trigger-build. Commands accept an organization and a project, falling back to the active context, and can print JSON. Creating an environment needs a name and the Git branch to track, with an optional custom subdomain.

The skill documents several rules. Production environments cannot be deleted, so check the type with environments get --json first. Delete needs --yes when not running interactively. Redeploy, which re-runs the existing build after a variable or infrastructure change, is not interchangeable with trigger-build, which starts a new build from source. Tool access is limited to mcloud environments, mcloud use and jq.

When your agent uses it

  • Listing the environments in a project
  • Redeploying after changing an environment variable
  • Starting a fresh build from source
  • Creating a long-lived environment tied to a branch

Example prompts

  • “List all environments in my Medusa Cloud project as JSON.”
  • “Redeploy the staging environment, I just changed a variable.”
  • “Create an environment named qa that tracks the release branch.”

Requirements

  • The mcloud CLI
  • A Medusa Cloud organization and project
  • Pre-approved tools (allowed-tools): Bash(mcloud environments*), Bash(mcloud use*), Bash(jq*)

What it can do on your machine

Read from SKILL.md and the folder at commit 066132d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(mcloud environments*)
    • Bash(mcloud use*)
    • Bash(jq*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

mcloud Environments loads about 1.2k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 302 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 302 words (~1,169 tokens).

“Execute mcloud environments commands to manage environment lifecycle and deployments.”

— opening of SKILL.md by medusajs
name
mcloud-environments
allowed-tools
Bash(mcloud environments*), Bash(mcloud use*), Bash(jq*)

Read the full SKILL.md on GitHub

Files

Just SKILL.md in plugins/medusa-cloud/skills/mcloud-environments of medusajs/medusa-agent-skills.

Open the folder on GitHubat commit 066132d

Compare with similar skills

mcloud Environments next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

mcloud Environments compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
mcloud Environments this skillmedusajs/medusa-agent-skills225—~1.2kAutomated safety check: PassNone
Vercel Deploybytedance/deer-flow83k10 repos~797Automated safety check: PassMIT
Deploy to Vercelvercel-labs/agent-skills32k11 repos~2.9kAutomated safety check: NotesNone
Twenty App Operationstwentyhq/twenty58k—~1.9kAutomated safety check: PassCustom licence
GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb6.7k—~4kAutomated safety check: NotesApache-2.0
Vercel CLI With Tokensvercel-labs/agent-skills32k7 repos~2.6kAutomated safety check: NotesNone

Similar skills

  • Vercel Deploy

    bytedance/deer-flow

    Deploys a project to Vercel with one script and no login, then returns a live preview URL and a claim link for moving the deployment into your own Vercel account.

    83k GitHub starsUsed in 10 repos~797 tokens
    DevOps & CloudAuto-check passed

  • Deploy to Vercel

    vercel-labs/agent-skills

    Official

    Deploys applications to Vercel as previews by default, picking a deploy method from the project's link state, git remote and team.

    32k GitHub starsUsed in 11 repos~2.9k tokens
    DevOps & CloudAuto-check: notes

  • Twenty App Operations

    twentyhq/twenty

    Operates an existing Twenty app: managing remotes, syncing, building, deploying, reading logs, running tests and setting up CI/CD, with confirmation for production.

    58k GitHub stars~1.9k tokensUpdated today
    DevOps & CloudAuto-check passed

  • GreptimeDB Dev Docker Image

    GreptimeTeam/greptimedb

    Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.

    6.7k GitHub stars~4k tokensUpdated 2 days ago
    DevOps & CloudAuto-check: notes

  • Vercel CLI With Tokens

    vercel-labs/agent-skills

    Official

    Deploys and manages Vercel projects through the CLI using an access token from the environment or a .env file instead of interactive login.

    32k GitHub starsUsed in 7 repos~2.6k tokens
    DevOps & CloudAuto-check: notes

  • Vercel

    remotion-dev/remotion

    Official

    Set up a Codex monitor for Vercel deployments and preview URLs.

    62k GitHub stars~1.2k tokensUpdated today
    DevOps & CloudAuto-check passed

More from medusajs/medusa-agent-skills

All 16 skills in this repo

  • Medusa Internal Admin Agents

    medusajs/medusa-agent-skills

    Walks through adding an AI agent for store operators to a Medusa project: data models, module service, agent runtime, streaming API route and admin chat UI.

    225 GitHub stars~1.9k tokensUpdated 2 days ago
    Auto-check passed

  • Learning Medusa

    medusajs/medusa-agent-skills

    Interactive tutorial where the agent teaches Medusa development by guiding you through building a brands feature, with lessons and verification checkpoints.

    225 GitHub stars~4.1k tokensUpdated 2 days ago
    Auto-check passed

  • Medusa Cloud CLI Authentication

    medusajs/medusa-agent-skills

    Runs the mcloud commands for logging in, checking who is authenticated, and choosing the active organization, project and environment.

    225 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • Medusa Cloud Deployments CLI

    medusajs/medusa-agent-skills

    Lists Medusa Cloud deployments, fetches one deployment's details and reads backend or storefront build logs through the mcloud CLI to debug failed builds.

    225 GitHub stars~883 tokensUpdated 2 days ago
    Auto-check passed

  • Medusa Cloud Local Build

    medusajs/medusa-agent-skills

    Reproduces a Medusa Cloud build on your machine with mcloud local build, to debug build-failed deployments without pushing or waiting on Cloud.

    225 GitHub stars~1k tokensUpdated 2 days ago
    Auto-check: notes

  • Mcloud Logs

    medusajs/medusa-agent-skills

    Execute mcloud logs to fetch and stream runtime logs for Cloud environments.

    225 GitHub stars~811 tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about mcloud Environments

What does mcloud Environments do?

Runs mcloud environments commands to list, inspect, create, delete, redeploy or rebuild environments in Medusa Cloud projects. Wraps the mcloud environments command group for managing the life of an environment: list, get, create, delete, redeploy and trigger-build. Commands accept an organization and a project, falling back to the active context, and can print JSON.

When should I use mcloud Environments?

mcloud Environments fits situations like: listing the environments in a project; redeploying after changing an environment variable; starting a fresh build from source; creating a long-lived environment tied to a branch.

How do I install mcloud Environments in Claude Code?

Run `npx skills add medusajs/medusa-agent-skills --skill mcloud-environments -a claude-code`. Or copy the skill folder (plugins/medusa-cloud/skills/mcloud-environments in medusajs/medusa-agent-skills) into .claude/skills/mcloud-environments in your project. Claude Code loads it when a task matches its description.

How do I install mcloud Environments in Codex?

Run `npx skills add medusajs/medusa-agent-skills --skill mcloud-environments -a codex`. Or copy the skill folder (plugins/medusa-cloud/skills/mcloud-environments in medusajs/medusa-agent-skills) into .agents/skills/mcloud-environments in your project. Codex loads it when a task matches its description.

Can I use mcloud Environments in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add medusajs/medusa-agent-skills --skill mcloud-environments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mcloud-environments, .gemini/skills/mcloud-environments, .github/skills/mcloud-environments and .opencode/skills/mcloud-environments in your project.

What does mcloud Environments need to run?

Going by SKILL.md and its folder, mcloud Environments needs the command-line tools its instructions call (jq). Our summary lists: The mcloud CLI; A Medusa Cloud organization and project. Its frontmatter pre-approves these tools: Bash(mcloud environments*), Bash(mcloud use*), Bash(jq*).

Does mcloud Environments access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is mcloud Environments safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does mcloud Environments use?

No licence was found for mcloud Environments or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does mcloud Environments use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to mcloud Environments?

Skills that share tags, products or a category with mcloud Environments: Vercel Deploy (bytedance/deer-flow, 83k stars), Deploy to Vercel (vercel-labs/agent-skills, 32k stars), Twenty App Operations (twentyhq/twenty, 58k stars) and GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains mcloud Environments?

medusajs (a GitHub organization) maintains it in medusajs/medusa-agent-skills, which has 225 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 5, 2026.

Source: medusajs/medusa-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.