mcloud-auth
---
What this skill does
--- name: mcloud-auth description: Execute mcloud authentication and context commands: login, logout, whoami, use, version, and signup. Use when setting up the CLI, switching accounts, verifying auth state, setting the active org/project/environment context, or checking the CLI version. allowed-tools: Bash(mcloud whoami*), Bash(mcloud use*), Bash(mcloud version*), Bash(mcloud logout*), Bash(jq*) --- # Cloud CLI: Auth and Context Commands Execute authentication and context commands for the Medusa Cloud CLI. ## Constraints - `mcloud login`, `mcloud signup`, and `mcloud use` (without flags) require a **TTY** — they fail in CI, Docker, or piped input. Use `MCLOUD_TOKEN` or pass flags explicitly instead. - When `MCLOUD_TOKEN` is set, file-based credentials are ignored and `mcloud login` is rejected. Unset it to switch accounts. - Always verify auth before any state-changing command: `mcloud whoami --json | jq -e '.auth.kind != "none"'` ## Commands ### whoami Show authenticated user, auth method, and active context (organization, project, environment). ```bash mcloud whoami --json ``` **Options:** - `--json` — Output as JSON **Use to verify auth and scope:** ```bash mcloud whoami --json | jq -e '.auth.kind != "none" and .organization.id != null' ``` Exit code `0` = authenticated and scoped. Non-zero = stop and prompt the user. ### use Set the active organization, project, and/or environment so subsequent commands skip those flags. ```bash mcloud use \ --organization <org-id> \ --project <project-id-or-handle> \ --environment <environment-handle> ``` **CRITICAL:** `mcloud use` without flags is interactive and fails in CI/Docker/piped input. Always pass flags explicitly. **Options:** - `-o/--organization <id>` — Set active organization - `-p/--project <id-or-handle>` — Set active project - `-e/--environment <handle>` — Set active environment - `--clear` — Clear all active context - `--json` — Output as JSON **Clear context:** ```bash mcloud use --clear ``` ### version Print CLI version and platform metadata. ```bash mcloud version --json ``` **Options:** - `--json` — Output as JSON ### login Authenticate with Medusa Cloud. Opens a browser to complete auth. > **TTY required.** Cannot be run in CI, Docker, or non-interactive environments. Use `MCLOUD_TOKEN` instead for non-interactive auth. ```bash mcloud login ``` **Non-interactive alternative:** ```bash export MCLOUD_TOKEN=<access-key> ``` **Options:** - `-t/--token <token>` — Authenticate using an access key without browser (non-interactive) - `--json` — Output as JSON ### logout Remove stored credentials. ```bash mcloud logout --json ``` **Options:** - `--json` — Output as JSON ### signup Create a new Medusa Cloud account. Opens a browser. > **TTY required.** Cannot be run in non-interactive environments. ```bash mcloud signup ``` ## Auth Methods | Method | When to use | |--------|-------------| | `mcloud login` (browser) | Interactive setup; requires TTY | | `mcloud login --token <key>` | Non-interactive login with access key | | `MCLOUD_TOKEN=<key>` env var | CI/CD, Docker, scripted environments | ## Examples ```bash # Check authentication and active context mcloud whoami --json # Verify auth before running commands mcloud whoami --json | jq -e '.auth.kind != "none" and .organization.id != null' # Set full context (org + project + environment) mcloud use \ --organization org_123 \ --project my-store \ --environment production # Set context by resolving names ORGANIZATION_ID=$(mcloud organizations list --json | jq -r '.[] | select(.name == "My Org") | .id') PROJECT_HANDLE=$(mcloud projects list --organization "$ORGANIZATION_ID" --json | jq -r '.[] | select(.name == "My Store") | .handle') ENVIRONMENT_HANDLE=$(mcloud environments list --organization "$ORGANIZATION_ID" --project "$PROJECT_HANDLE" --json | jq -r '.[] | select(.name == "Production") | .handle') mcloud use \ --organization "$ORGANIZATION_ID" \ --project "$PROJECT_HANDLE" \ --environment "$ENVIRONMENT_HANDLE" # Clear context mcloud use --clear # Check CLI version mcloud version --json # Non-interactive login with token mcloud login --token <access-key> # Logout mcloud logout ```
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.