Azure Bicep Skill
timothywarner-org/claude-code
A skill your agent uses when authoring, reviewing, or refactoring Azure Bicep code.
Manages Medusa Cloud resources through the Cloud CLI (mcloud).
Install Using Medusa Cloud
$ npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install medusajs/medusa-agent-skills using-medusa-cloud --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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/using-medusa-cloud .claude/skills/using-medusa-cloud && rm -rf skills-srcUse ~/.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/
Install the "using-medusa-cloud" agent skill from https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/using-medusa-cloud into .claude/skills/using-medusa-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-medusa-cloud", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/using-medusa-cloudType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install medusajs/medusa-agent-skills using-medusa-cloud --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/medusajs/medusa-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/medusa-cloud/skills/using-medusa-cloud .agents/skills/using-medusa-cloud && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "using-medusa-cloud" agent skill from https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/using-medusa-cloud into .agents/skills/using-medusa-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-medusa-cloud", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install medusajs/medusa-agent-skills using-medusa-cloud --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/medusajs/medusa-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/medusa-cloud/skills/using-medusa-cloud .cursor/skills/using-medusa-cloud && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "using-medusa-cloud" agent skill from https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/using-medusa-cloud into .cursor/skills/using-medusa-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-medusa-cloud", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/medusajs/medusa-agent-skills.git --path plugins/medusa-cloud/skills/using-medusa-cloud--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install medusajs/medusa-agent-skills using-medusa-cloud --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/medusajs/medusa-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/medusa-cloud/skills/using-medusa-cloud .gemini/skills/using-medusa-cloud && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "using-medusa-cloud" agent skill from https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/using-medusa-cloud into .gemini/skills/using-medusa-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-medusa-cloud", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install medusajs/medusa-agent-skills using-medusa-cloudInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/medusajs/medusa-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/medusa-cloud/skills/using-medusa-cloud .github/skills/using-medusa-cloud && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "using-medusa-cloud" agent skill from https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/using-medusa-cloud into .github/skills/using-medusa-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-medusa-cloud", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install medusajs/medusa-agent-skills using-medusa-cloud --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/medusajs/medusa-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/medusa-cloud/skills/using-medusa-cloud .opencode/skills/using-medusa-cloud && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "using-medusa-cloud" agent skill from https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/using-medusa-cloud into .opencode/skills/using-medusa-cloud/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "using-medusa-cloud", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
using-medusa-cloud- GitHub stars
- 228
- Token cost
- ~1.1k tokens
- SKILL.md length
- 452 words
- Files
- 4
- Skills in repo
- 16
- Repo updated
- First seen
- Licence
- None found
At a glance
Manages Medusa Cloud resources through the Cloud CLI (mcloud).
- Debugging deployments
- SKILL.md covers Constraints, CRITICAL: Load Reference Files…, Quick Reference and Common Pitfalls, plus 1 more section
- Calls jq; needs MCLOUD_TOKEN
- Managing environments
What it does
Using Medusa Cloud is an agent skill from medusajs/medusa-agent-skills. Manages Medusa Cloud resources through the Cloud CLI (mcloud). Use when deploying, debugging deployments, managing environments, environment variables, or any Medusa Cloud operation. CRITICAL for mcloud commands, deployment failures, build logs, Cloud setup, and CI/CD workflows.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `reference/debugging-deployments.md`, `reference/environments-and-variables.md` and `reference/setup.md`).
It sits in DevOps & Cloud, covering Deployment, CI/CD and Debugging. The repository describes itself as: Agent skills and commands for Medusa best practices and conventions.
When your agent uses it
- Debugging deployments
- Managing environments
- Environment variables
- Any Medusa Cloud operation
Example prompts
- “Use the using-medusa-cloud skill to manage Medusa Cloud resources through the Cloud CLI (mcloud)”
- “/using-medusa-cloud”
Requirements
- Docker
- A credential in MCLOUD_TOKEN
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 nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
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 these keys or tokens, usually read from environment variables:
MCLOUD_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Using Medusa Cloud loads about 1.1k tokens when it runs. Until then it costs about 75 tokens; SKILL.md has 452 words of instructions outside code blocks.
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 452 words (~1,104 tokens).
“Operational guide for AI agents managing Medusa Cloud infrastructure through the mcloud CLI. Covers setup, deployments, debugging, environments, and variables.”
- name
- using-medusa-cloud
Files
SKILL.md and 3 other files in plugins/medusa-cloud/skills/using-medusa-cloud of medusajs/medusa-agent-skills.
- SKILL.md
- reference/debugging-deployments.md
- reference/environments-and-variables.md
- reference/setup.md
Open the folder on GitHubat commit 066132d
Compare with similar skills
Using Medusa Cloud 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Using Medusa Cloud this skillmedusajs/medusa-agent-skills | 228 | — | ~1.1k | Automated safety check: Pass | None | |
| Azure Bicep Skilltimothywarner-org/claude-code | 224 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Env Managerbobmatnyc/claude-mpm | 155 | — | ~2k | Automated safety check: Notes | MIT | |
| Phase 9 Deploymentww-w-ai/bkit-claude-code | 601 | — | ~2.7k | Automated safety check: Notes | Apache-2.0 | |
| Nextjs Deploymentgiuseppe-trisciuoglio/developer-kit | 356 | — | ~2.3k | Automated safety check: Notes | MIT | |
| CD Pipeline GeneratorArabelaTso/Skills-4-SE | 253 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Env Manager
bobmatnyc/claude-mpm
Environment variable validation, synchronization, and management across local development, CI/CD, and deployment platforms
Phase 9 Deployment
ww-w-ai/bkit-claude-code
Deploy to production — CI/CD pipelines, environment config, deployment strategies.
Nextjs Deployment
giuseppe-trisciuoglio/developer-kit
Provides comprehensive patterns for deploying Next.js applications to production.
CD Pipeline Generator
ArabelaTso/Skills-4-SE
Generate GitHub Actions deployment workflows for automated deployment to staging and production environments on cloud platforms (AWS, GCP, Azure).
- Official
Azure Devtest Labs
MicrosoftDocs/Agent-Skills
Expert knowledge for Azure DevTest Labs development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations…
More from medusajs/medusa-agent-skills
All 16 skills in this repoMedusa 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.
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.
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.
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.
mcloud Environments
medusajs/medusa-agent-skills
Runs mcloud environments commands to list, inspect, create, delete, redeploy or rebuild environments in Medusa Cloud projects.
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.
Related
Categories
Questions about Using Medusa Cloud
What does Using Medusa Cloud do?
Manages Medusa Cloud resources through the Cloud CLI (mcloud). Using Medusa Cloud is an agent skill from medusajs/medusa-agent-skills. Manages Medusa Cloud resources through the Cloud CLI (mcloud).
When should I use Using Medusa Cloud?
Using Medusa Cloud fits situations like: debugging deployments; managing environments; environment variables; any Medusa Cloud operation.
How do I install Using Medusa Cloud in Claude Code?
Run `npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a claude-code`. Or copy the skill folder (plugins/medusa-cloud/skills/using-medusa-cloud in medusajs/medusa-agent-skills) into .claude/skills/using-medusa-cloud in your project. Claude Code loads it when a task matches its description.
How do I install Using Medusa Cloud in Codex?
Run `npx skills add medusajs/medusa-agent-skills --skill using-medusa-cloud -a codex`. Or copy the skill folder (plugins/medusa-cloud/skills/using-medusa-cloud in medusajs/medusa-agent-skills) into .agents/skills/using-medusa-cloud in your project. Codex loads it when a task matches its description.
Can I use Using Medusa Cloud 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 using-medusa-cloud -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/using-medusa-cloud, .gemini/skills/using-medusa-cloud, .github/skills/using-medusa-cloud and .opencode/skills/using-medusa-cloud in your project.
What does Using Medusa Cloud need to run?
Going by SKILL.md and its folder, Using Medusa Cloud needs the command-line tools its instructions call (jq) and credentials named MCLOUD_TOKEN. Our summary lists: Docker; A credential in MCLOUD_TOKEN.
Does Using Medusa Cloud 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 Using Medusa Cloud 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 Using Medusa Cloud use?
No licence was found for Using Medusa Cloud or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Using Medusa Cloud use?
About 1.1k tokens (SKILL.md is roughly 4.4k 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 Using Medusa Cloud?
Skills that share tags, products or a category with Using Medusa Cloud: Azure Bicep Skill (timothywarner-org/claude-code, 224 stars), Env Manager (bobmatnyc/claude-mpm, 155 stars), Phase 9 Deployment (ww-w-ai/bkit-claude-code, 601 stars) and Nextjs Deployment (giuseppe-trisciuoglio/developer-kit, 356 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Using Medusa Cloud?
medusajs (a GitHub organization) maintains it in medusajs/medusa-agent-skills, which has 228 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.