Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Lists Medusa Cloud deployments, fetches one deployment's details and reads backend or storefront build logs through the mcloud CLI to debug failed builds.
Install Medusa Cloud Deployments CLI
$ npx skills add medusajs/medusa-agent-skills --skill mcloud-deployments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install medusajs/medusa-agent-skills mcloud-deployments --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/mcloud-deployments .claude/skills/mcloud-deployments && 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 "mcloud-deployments" agent skill from https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/mcloud-deployments into .claude/skills/mcloud-deployments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcloud-deployments", 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/mcloud-deploymentsType 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 mcloud-deployments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install medusajs/medusa-agent-skills mcloud-deployments --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/mcloud-deployments .agents/skills/mcloud-deployments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mcloud-deployments" agent skill from https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/mcloud-deployments into .agents/skills/mcloud-deployments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcloud-deployments", 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 mcloud-deployments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install medusajs/medusa-agent-skills mcloud-deployments --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/mcloud-deployments .cursor/skills/mcloud-deployments && 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 "mcloud-deployments" agent skill from https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/mcloud-deployments into .cursor/skills/mcloud-deployments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcloud-deployments", 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/mcloud-deployments--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 mcloud-deployments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install medusajs/medusa-agent-skills mcloud-deployments --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/mcloud-deployments .gemini/skills/mcloud-deployments && 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 "mcloud-deployments" agent skill from https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/mcloud-deployments into .gemini/skills/mcloud-deployments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcloud-deployments", 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 mcloud-deploymentsInstalls 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 mcloud-deployments -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/mcloud-deployments .github/skills/mcloud-deployments && 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 "mcloud-deployments" agent skill from https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/mcloud-deployments into .github/skills/mcloud-deployments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcloud-deployments", 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 mcloud-deployments -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 mcloud-deployments --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/mcloud-deployments .opencode/skills/mcloud-deployments && 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 "mcloud-deployments" agent skill from https://github.com/medusajs/medusa-agent-skills/tree/main/plugins/medusa-cloud/skills/mcloud-deployments into .opencode/skills/mcloud-deployments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mcloud-deployments", 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
mcloud-deployments- GitHub stars
- 227
- Token cost
- ~883 tokens
- SKILL.md length
- 252 words
- Files
- 1
- Skills in repo
- 15
- Repo updated
- First seen
- Licence
- None found
At a glance
Lists Medusa Cloud deployments, fetches one deployment's details and reads backend or storefront build logs through the mcloud CLI to debug failed builds.
- Listing recent deployments for a Medusa Cloud project
- SKILL.md covers Constraints, Commands, Deployment Statuses and Examples
- Calls jq
- Checking why a deployment shows build-failed
What it does
The skill wraps three mcloud deployments commands. List returns recent deployments for a project, 20 by default and up to 200, with filters for environment, environment type (production, long-lived or preview), commit SHA and pagination offset. Get returns one deployment by ID, and build-logs fetches the backend log by default or the storefront log when asked.
Rules for the agent: always pass --json when parsing output because plain text may change, check context with mcloud whoami --json if the organization and project are not known, and use deployment IDs in the depl_ format or build IDs, which resolve to their latest deployment. A status table explains the lifecycle from created, building and built through deploying and deployed, plus build-failed, which points to build logs, deployment-failed, which points to runtime logs, timed-out and canceled. Tool permissions are limited to mcloud deployments and jq.
When your agent uses it
- Listing recent deployments for a Medusa Cloud project
- Checking why a deployment shows build-failed
- Finding the deployment for a specific commit
Example prompts
- “List the latest deployments for my production environment and show their statuses.”
- “Get the build logs for the most recent failed deployment and tell me what broke.”
- “Read the storefront build log for the newest preview deployment.”
Requirements
- The mcloud CLI, logged in to a Medusa Cloud organization
- jq for parsing JSON output
- Pre-approved tools (allowed-tools): Bash(mcloud deployments*), 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 deployments*)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
Medusa Cloud Deployments CLI loads about 883 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 252 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 252 words (~883 tokens).
“Execute mcloud deployments commands to inspect deployments and their build logs.”
- name
- mcloud-deployments
- allowed-tools
- Bash(mcloud deployments*), Bash(jq*)
Files
Just SKILL.md in plugins/medusa-cloud/skills/mcloud-deployments of medusajs/medusa-agent-skills.
Open the folder on GitHubat commit 066132d
Compare with similar skills
Medusa Cloud Deployments CLI 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 |
|---|---|---|---|---|---|---|
| Medusa Cloud Deployments CLI this skillmedusajs/medusa-agent-skills | 227 | — | ~883 | Automated safety check: Pass | None | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Vercelremotion-dev/remotion | 62k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
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.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
- Official
Vercel
remotion-dev/remotion
Set up a Codex monitor for Vercel deployments and preview URLs.
AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
More from medusajs/medusa-agent-skills
All 15 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.
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.
Mcloud Logs
medusajs/medusa-agent-skills
Execute mcloud logs to fetch and stream runtime logs for Cloud environments.
Related
Works with
Categories
Questions about Medusa Cloud Deployments CLI
What does Medusa Cloud Deployments CLI do?
Lists Medusa Cloud deployments, fetches one deployment's details and reads backend or storefront build logs through the mcloud CLI to debug failed builds. The skill wraps three mcloud deployments commands. List returns recent deployments for a project, 20 by default and up to 200, with filters for environment, environment type (production, long-lived or preview), commit SHA and pagination offset.
When should I use Medusa Cloud Deployments CLI?
Medusa Cloud Deployments CLI fits situations like: listing recent deployments for a Medusa Cloud project; checking why a deployment shows build-failed; finding the deployment for a specific commit.
How do I install Medusa Cloud Deployments CLI in Claude Code?
Run `npx skills add medusajs/medusa-agent-skills --skill mcloud-deployments -a claude-code`. Or copy the skill folder (plugins/medusa-cloud/skills/mcloud-deployments in medusajs/medusa-agent-skills) into .claude/skills/mcloud-deployments in your project. Claude Code loads it when a task matches its description.
How do I install Medusa Cloud Deployments CLI in Codex?
Run `npx skills add medusajs/medusa-agent-skills --skill mcloud-deployments -a codex`. Or copy the skill folder (plugins/medusa-cloud/skills/mcloud-deployments in medusajs/medusa-agent-skills) into .agents/skills/mcloud-deployments in your project. Codex loads it when a task matches its description.
Can I use Medusa Cloud Deployments CLI 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-deployments -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-deployments, .gemini/skills/mcloud-deployments, .github/skills/mcloud-deployments and .opencode/skills/mcloud-deployments in your project.
What does Medusa Cloud Deployments CLI need to run?
Going by SKILL.md and its folder, Medusa Cloud Deployments CLI needs the command-line tools its instructions call (jq). Our summary lists: The mcloud CLI, logged in to a Medusa Cloud organization; jq for parsing JSON output. Its frontmatter pre-approves these tools: Bash(mcloud deployments*), Bash(jq*).
Does Medusa Cloud Deployments CLI 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 Medusa Cloud Deployments CLI 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 Medusa Cloud Deployments CLI use?
No licence was found for Medusa Cloud Deployments CLI or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Medusa Cloud Deployments CLI use?
About 883 tokens (SKILL.md is roughly 3.5k 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 Medusa Cloud Deployments CLI?
Skills that share tags, products or a category with Medusa Cloud Deployments CLI: Kubeshark Installer (kubeshark/kubeshark, 12k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars) and Vercel (remotion-dev/remotion, 62k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Medusa Cloud Deployments CLI?
medusajs (a GitHub organization) maintains it in medusajs/medusa-agent-skills, which has 227 GitHub stars. The repository holds 15 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.