Mcloud Local
Execute mcloud local build to reproduce a Cloud build on the local machine. Use when debugging a build-failed deployment without pushing to the tracked branch, iterating on a build fix, or testing build-variable changes locally. Requires Docker and must run inside the project's Git repo.
Install
/plugin marketplace add medusajs/medusa-agent-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add medusajs/medusa-agent-skills --skill mcloud-localgit clone --depth 1 https://github.com/medusajs/medusa-agent-skills.git /tmp/medusa-agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/medusa-agent-skills/plugins/medusa-cloud/skills/mcloud-local ~/.claude/skills/mcloud-localPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Cloud CLI: Local Command Execute `mcloud local build` to run a Cloud build on the local machine, mirroring how Cloud builds the project. Use it to debug `build-failed` deployments without pushing changes and waiting for a full Cloud build. ## Constraints - **No `--json` flag.** `local build` streams plaintext build output and signals the result through its **exit code** (`0` = success). Do not parse its output as JSON. - **Requires Docker installed and running**, and must run from **inside the project's Git repository**. - Reproduces `build-failed` (build) failures only — not `deployment-failed` (runtime) failures. For runtime failures, use `mcloud logs --deployment <id>`. - Available since mcloud CLI v0.1.10. - The Docker build cache is **disabled by default** so variable changes always invalidate the cache; pass `--docker-cache` to enable it. ## Command ### local build Run a Cloud build locally. Infers the root path and build variables from the linked Cloud project and environment. Builds the backend by default; pass `--type storefront` for the storefront. ```bash mcloud local build \ --organization <org-id> \ --project <project-id-or-handle> \ --environment <environment-handle> ``` **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) - `-e/--environment <handle>` — Environment whose variables are used (falls back to active context)
Details
- Skill name
mcloud-local- Repository
- medusajs/medusa-agent-skills
- Path
plugins/medusa-cloud/skills/mcloud-local/SKILL.md- Repo updated
- 13 November 2026
FAQ
What does the Mcloud Local skill do?
Execute mcloud local build to reproduce a Cloud build on the local machine. Use when debugging a build-failed deployment without pushing to the tracked branch, iterating on a build fix, or testing build-variable changes locally. Requires Docker and must run inside the project's Git repo.
How do I install the Mcloud Local skill?
Claude Code plugin: /plugin marketplace add medusajs/medusa-agent-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Mcloud Local popular?
It lives in medusajs/medusa-agent-skills, which has 237 GitHub stars and 29 forks.
Related skills
Building Admin Dashboard Customizations
237medusajs/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
237medusajs/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.
Building with Medusa
237medusajs/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.
Upstream Fix and Pin
423mizchi/skills
自分の依存ライブラリにバグや欠けている機能があり、上流に PR を出して取り込まれるまで下流プロジェクトを動かしたいときの運用。git ref pin(branch HEAD SHA → merge SHA)、`link:` への退避判断、SHA 取り扱い、pnpm v10 の build script gating まで含む。
Maintainer Persona
423mizchi/skills
Write an issue or PR for a repository you do not own so its maintainers can triage it. Measures the target's own history (reviewers, gates, body length, headings, language, how first-time PRs fare) into an editable persona file, branches by context (OSS first-time / OSS returning / another team inside your org), drafts in Japanese and translates only after approval when the target writes English, checks with a fresh reader and a slop lint baselined on the maintainers' own PRs, and gates the send. Use when filing upstream issues, sending a fix or failing-test PR to another project or team, or r
Apm Package Author
206thomast1906/github-copilot-agent-skills
Create, maintain, and troubleshoot APM (Agent Package Manager) manifests for distributing GitHub Copilot skills, agents, and MCP servers. USE FOR: creating apm.yml root manifests; creating packages/* sub-manifests; bundling MCP server config into a package; installing packages from a GitHub repo; troubleshooting APM install errors (missing .vscode/mcp.json, Codex CLI warnings, cached installs). DO NOT USE FOR: general GitHub Copilot customization questions; creating SKILL.md files (use skill-creator); writing MCP server code.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.