Index of every page on this site: llms.txt
All skills
medusajs avatar

/mcloud-projects

@c5a56b4 official
by Medusamedusajs/medusa-agent-skills237 stars
29
Run it yourself

Execute mcloud projects commands to list, get, or delete Cloud projects. Use when discovering projects, resolving project handles by name, or retrieving project details including linked environments.

Use this Skill: https://skilld.dev/gh/medusajs/medusa-agent-skills/mcloud-projects

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈54 tokens for metadata: the name and description. ≈752 when used: this file.

Description uses 2.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈217 characters, or 2.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Cloud CLI: Projects Commands

Execute mcloud projects commands to manage Cloud projects.

Constraints

  • projects delete is irreversible — removes all associated environments, deployments, and resources. Always confirm the project ID/handle before deleting.
  • Use --yes with delete in non-interactive contexts (scripts, pipelines, agents).

Commands

projects list

List projects in an organization. If --organization is omitted (and no active context org is set), lists projects across all organizations you have access to, grouped by organization.

mcloud projects list --organization <org-id> --json

Options:

  • -o/--organization <id> — Organization ID (falls back to active context; if unset, lists across all your organizations)
  • --json — Output as JSON

projects get

Retrieve a single project by its ID or handle.

mcloud projects get <project-id-or-handle> --organization <org-id> --json

Arguments:

  • project — Project ID or handle (required)

Options:

  • -o/--organization <id> — Organization ID (falls back to active context; required)
  • --json — Output as JSON

projects delete

Delete a project by its ID or handle. Irreversible.

mcloud projects delete <project-id-or-handle> \
  --organization <org-id> \
  --yes

Arguments:

  • project — Project ID or handle (required)

Options:

  • -o/--organization <id> — Organization ID (falls back to active context; required)
  • -y/--yes — Skip confirmation prompt (required in non-interactive mode)
  • --json — Output as JSON

Project Fields (JSON)

Field Description
id Project ID
handle URL-safe project handle (used in most commands)
name Display name
status ready when healthy
region Deployment region (e.g. us-east-1)
repository Linked GitHub repository (owner/repo)
root_path Root path within the repository
organization Owning organization (id, name, created_at)
environments Array of associated environments (each may include storefront_environments)

Examples

# List all projects in an organization
mcloud projects list --organization org_123 --json

# Set context to a project by name
PROJECT_HANDLE=$(
  mcloud projects list --organization org_123 --json \
    | jq -r '.[] | select(.name == "My Store") | .handle'
)
mcloud use --project "$PROJECT_HANDLE"

# Get project details including environments
mcloud projects get my-store --organization org_123 --json

# List all environment handles for a project
mcloud projects get my-store --organization org_123 --json \
  | jq -r '.environments[].handle'

# Find project handle by name
mcloud projects list --organization org_123 --json \
  | jq -r '.[] | select(.name == "My Store") | .handle'

# Delete a project (irreversible — confirm before running)
mcloud projects delete old-project --organization org_123 --yes

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides instructions for managing Cloud projects using the mcloud CLI. It includes appropriate warnings for destructive operations and uses standard tools for data processing. No security issues were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at c5a56b4. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 4 months ago
What it can do
Runs commands
All 3 allowed tools
Bash(mcloud projects*)Bash(mcloud use*)Bash(jq*)

README badge

README badge for medusajs/medusa-agent-skills/mcloud-projects