Execute mcloud organizations commands to list or get Cloud organizations. Use when discovering organizations, resolving organization IDs by name, or retrieving organization details including members and subscription.
npx skills add https://github.com/medusajs/medusa-agent-skills --skill mcloud-organizations
Execute mcloud organizations commands to list and retrieve Cloud organizations.
organizations list requires personal auth (browser login or personal access key). Organization access keys return 401 on this command.MCLOUD_TOKEN using an org access key, use mcloud whoami --json to get the organization ID instead.List all organizations your account has access to.
mcloud organizations list --json
Options:
--json — Output as JSONRetrieve a single organization by ID. Returns metadata, subscription details, and members.
mcloud organizations get <organization-id> --json
Arguments:
organization — Organization ID (required)Options:
-o/--organization <id> — Override the organization in active context (must match the argument)--json — Output as JSON| Field | Description |
|-------|-------------|
| id | Organization ID |
| name | Organization display name |
| billing_email | Billing contact email |
| status | active or otherwise |
| members | Array of member objects with id, role, user.email |
| subscription | Current plan, period, and is_active flag |
| account_holder | Billing account holder details |
# List all organizations
mcloud organizations list --json
# Set context to first organization
ORGANIZATION_ID=$(
mcloud organizations list --json \
| jq -r '.[0].id'
)
mcloud use --organization "$ORGANIZATION_ID"
# Find organization ID by name
ORGANIZATION_ID=$(
mcloud organizations list --json \
| jq -r '.[] | select(.name == "My Organization") | .id'
)
# Get organization details (subscription, members)
mcloud organizations get org_123 --json
# List member emails
mcloud organizations get org_123 --json \
| jq -r '.members[].user.email'
# Check subscription plan
mcloud organizations get org_123 --json \
| jq '{plan: .subscription.plan.name, status: .subscription.is_active}'
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take medusajs/mcloud-organizations from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.