using-medusa-cloud
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.
What this skill does
# Managing Medusa Cloud Resources Operational guide for AI agents managing Medusa Cloud infrastructure through the `mcloud` CLI. Covers setup, deployments, debugging, environments, and variables. ## Constraints - **Always pass `--json`** when parsing CLI output. Plaintext output is for humans and may change without warning. - **Confirm context before mutating.** Run `mcloud whoami --json` before any state change. - **Read before you write.** Run a `get` or `list` before any `delete`, `redeploy`, or `trigger-build`. - **Use `--yes` for destructive operations.** `delete` commands require `--yes` in non-interactive mode. - **Production environments cannot be deleted.** `mcloud environments delete` errors on production by design. - **Never pass `--reveal` unless the user explicitly asks.** Secret values appear in terminal scrollback and logs. - **`--json` and `--follow` are incompatible.** Use bounded time windows (`--from`/`--to`) with `--json` for programmatic log ingestion. ## CRITICAL: Load Reference Files When Needed **Load these references based on what you're doing:** - **Setting up the CLI?** → MUST load `setup.md` first - **Debugging a failed deployment?** → MUST load `debugging-deployments.md` first - **Managing environments or variables?** → MUST load `environments-and-variables.md` first **Minimum requirement:** Load at least one reference file before executing multi-step workflows. ## Quick Reference ### Authentication Check Always verify auth and scope before mutating state: ```bash mcloud whoami --json | jq -e '.auth.kind != "none" and .organization.id != null' ``` Exit code `0` = authenticated and scoped. Non-zero = stop and ask the user. ### Set Context Once ```bash mcloud use \ --organization org_123 \ --project proj_123 \ --environment production ``` > **CRITICAL:** `mcloud use` without flags is interactive and fails in CI/Docker/piped input. Always pass flags. ### Deployment Status Routing Route on `backend_status` (or `storefront_status`): | Status | Meaning | Logs to check | |--------|---------|---------------| | `build-failed` | Build step failed | `mcloud deployments build-logs <id>` | | `deployment-failed` | Runtime crashed after build | `mcloud logs --deployment <id>` | | `timed-out` | Exceeded time budget | Both: build-logs first, then runtime logs | ### Redeployment Decision | Command | When to use | |---------|-------------| | `mcloud environments redeploy <env>` | Fix is environment-side (variable change, infra) — reruns existing build | | `mcloud environments trigger-build <env>` | Fix is in source code on the tracked branch — starts new build | ## Common Pitfalls - **TTY-only commands.** `mcloud login`, `mcloud use` (without flags), and `delete` without `--yes` require a TTY. They fail in CI, Docker, or piped input. - **`MCLOUD_TOKEN` precedence.** When set, file-based credentials are ignored and `mcloud login` is rejected. Unset it to switch accounts. - **Personal vs org access keys.** Personal keys require `--organization`; org keys are pre-scoped. - **`organizations list` requires personal auth.** Org access keys return 401 on this command. - **Build IDs vs deployment IDs.** `depl_*` = deployment ID; anything else = build ID (resolved to latest deployment). `mcloud logs --deployment` accepts both; other commands take build IDs only. ## Reference Files ``` setup.md - CLI installation, authentication, context setup debugging-deployments.md - Build/deployment failure recipes and log analysis environments-and-variables.md - Environment lifecycle and variable management ```
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.