mcloud-variables
Execute mcloud variables commands to list, get, set, and delete environment variables for a Cloud environment. Use when inspecting, reading, creating, updating, deleting, or exporting environment variables. Never pass --reveal unless the user explicitly requests secret values.
- Installs
- 1.3K
- Last 24h
- +14
- Trending rank
- #7125
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/medusajs/medusa-agent-skills --skill mcloud-variables- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads mcloud-variables automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Cloud CLI: Variables Commands
Execute mcloud variables commands to inspect and manage environment variables for Cloud environments.
Constraints
- Never pass
--revealunless the user explicitly asks. Secret values appear in terminal scrollback, log aggregators, and process listings. - Variable changes need a deploy to apply.
set/deletedon't rebuild or redeploy. Runmcloud environments redeploy <env>for a runtime variable, ormcloud environments trigger-build <env>for a build variable (a redeploy reuses the existing image and won't pick up build-variable changes). - System variables can't be deleted, and
deleterequires--yesin non-interactive mode. - Looking up or creating a variable by key requires
--projectand--environment(or the equivalent in active context). Referencing by ID (var_...) works without project/environment context. setanddeleterequire mcloud CLI v0.1.10+.
Commands
variables list
List all environment variables for a Cloud environment.
mcloud variables list \
--organization <org-id> \
--project <project-id-or-handle> \
--environment <environment-handle> \
--json
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 handle (falls back to active context)-t/--type <backend|storefront>— Which variable set to list (default:backend)--scope <build|runtime>— Filter by scope; repeatable (default: both scopes)--include-system— Include system variables Medusa auto-injects (default:false)--reveal— Print secret values in plaintext instead of masking (use only when explicitly asked)--dotenv— Output.env-formattedKEY=VALUElines instead of a table--json— Output as JSON
variables get
Retrieve a single variable by its ID (var_...) or key.
# By key (requires project + environment context)
mcloud variables get ADMIN_CORS \
--organization <org-id> \
--project <project-id-or-handle> \
--environment <environment-handle> \
--json
# By ID (works without project/environment context)
mcloud variables get var_01XYZ --json
Arguments:
variable— Variable ID (var_...) or key (required)
Options:
-o/--organization <id>,-p/--project <id-or-handle>,-e/--environment <handle>-t/--type <backend|storefront>— Which variable set to read (default:backend)--reveal— Print secret value in plaintext (use only when explicitly asked)--json— Output as JSON
variables set
Create or update one or more variables. The CLI updates when you reference an existing key or a var_... ID, and creates otherwise.
# Single variable
mcloud variables set API_KEY pk_123 \
--organization <org-id> \
--project <project-id-or-handle> \
--environment <environment-handle>
# Multiple at once
mcloud variables set -v API_KEY=pk_123 -v CLIENT_ID=my_app
# From a .env file
mcloud variables set --env-file .env
Arguments:
variable— Variable ID (var_...) or key to set (omit when using--var/--env-file)value— Value to set (required when avariableargument is passed)
Options:
-o/--organization <id>,-p/--project <id-or-handle>,-e/--environment <handle>-t/--type <backend|storefront>— Which variable set to write (default:backend)-v/--var <KEY=VALUE|ID=VALUE>— A variable to set; repeatable--env-file <path>— Set all variables from a.envfile--secret,--no-secret— Mark as secret (default:falsefor new variables)--build,--no-build— Available at build time (default:falsefor new variables)--runtime,--no-runtime— Available at runtime (default:truefor new variables)--json— Output as JSON
Redeploy (runtime) or trigger-build (build) afterward — see Constraints.
variables delete
Delete a variable by its ID (var_...) or key. Irreversible; system variables can't be deleted.
mcloud variables delete API_KEY \
--organization <org-id> \
--project <project-id-or-handle> \
--environment <environment-handle> \
--yes
Arguments:
variable— Variable ID (var_...) or key to delete (required)
Options:
-o/--organization <id>,-p/--project <id-or-handle>,-e/--environment <handle>-t/--type <backend|storefront>— Which variable set to delete from (default:backend)-y/--yes— Skip confirmation prompt (required in non-interactive mode)--json— Output as JSON
Variable Fields (JSON)
| Field | Description |
|---|---|
id | Variable ID (var_...) |
key | Variable name (e.g. ADMIN_CORS) |
value | Variable value (masked if is_secret and --reveal not passed) |
is_secret | Whether the variable is treated as a secret |
is_build | Available at build time |
is_runtime | Available at runtime |
environment_id | The environment ID this variable belongs to |
source | user for user-set variables, system for auto-injected ones |
Examples
# List all variables for the active environment
mcloud variables list --json
# List only runtime variables, including system ones
mcloud variables list --scope runtime --include-system --json
# List storefront variables
mcloud variables list --type storefront --json
# Get a variable by key (with active context)
mcloud variables get DATABASE_URL --json
# Get a variable by ID (no env context needed)
mcloud variables get var_01XYZ --json
# Set a single variable, then redeploy to apply (runtime)
mcloud variables set REDIS_URL redis://cache:6379
mcloud environments redeploy production
# Set a secret build-only variable, then trigger a build to apply
mcloud variables set STRIPE_SECRET_KEY sk_live_123 --secret --build --no-runtime
mcloud environments trigger-build production
# Set multiple variables from a .env file
mcloud variables set --env-file .env
# Delete a variable (irreversible — confirm before running)
mcloud variables delete OLD_FLAG --yes
# Only reveal secrets when user explicitly asks
mcloud variables get STRIPE_SECRET_KEY --reveal --json | jq -r '.value'
# Export all variables to a .env file (user must explicitly request --reveal)
mcloud variables list --reveal --dotenv > .env
# Check if a specific variable exists
mcloud variables list --json | jq '.[] | select(.key == "REDIS_URL")'
FAQ
What does the mcloud-variables skill do?
Execute mcloud variables commands to list, get, set, and delete environment variables for a Cloud environment. Use when inspecting, reading, creating, updating, deleting, or exporting environment variables. Never pass --reveal unless the user explicitly requests secret values.
How do I install mcloud-variables?
Run npx skills add https://github.com/medusajs/medusa-agent-skills --skill mcloud-variables in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/mcloud-variables/ (personal) or .claude/skills/mcloud-variables/ (project).
Which AI agents can use mcloud-variables?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is mcloud-variables safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains mcloud-variables?
It is published by medusajs in medusajs/medusa-agent-skills, and it is an official skill from the maker of the technology it covers. It has 1,335 recorded installs.
More from medusajs/medusa-agent-skills
storefront-best-practices
medusajs/medusa-agent-skills
ALWAYS use this skill when working on ecommerce storefronts, online stores, shopping sites. Use for ANY storefront component including checkout pages, cart, payment flows, product pages, product listings, navigation, homepage, or ANY page/component in a storefront. CRITICAL for adding checkout, implementing cart, integrating Medusa backend, making a store agent-friendly for AI shopping agents, or building any ecommerce functionality. Framework-agnostic (Next.js, SvelteKit, TanStack Start, React, Vue). Provides patterns, decision frameworks, backend integration guidance.
building-with-medusa
medusajs/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.
building-admin-dashboard-customizations
medusajs/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
medusajs/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.
db-migrate
medusajs/medusa-agent-skills
Run database migrations in Medusa
db-generate
medusajs/medusa-agent-skills
Generate database migrations for a Medusa module
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available