Skip to main content
Cargo Skills turn the Cargo CLI into something your AI agent can drive on its own. Each skill is a prompt package that encodes the CLI’s commands, flags, UUID-discovery patterns, and gotchas — so instead of guessing, your agent already knows exactly how to run tools, trigger plays, query the warehouse, and deploy agents. You just describe what you want: 
"Trigger the MQL scoring play on all leads added this week."
  → cargo-ai orchestration play list
  → cargo-ai orchestration batch create --workflow-uuid <uuid> \
      --data '{"kind":"segment","segmentUuid":"<uuid>"}' \
      --wait-until-finished
No manual UUID lookup, no documentation tab, no copy-pasting JSON.
Want to suggest an edit, report an issue, or fork the skills? Head to getcargohq/cargo-skills on GitHub.

​
The seven skills

Each skill maps to one command domain of the CLI:
SkillDomainWhat your agent can do
cargo-cli-orchestrationRuntimeRun tools on single records, trigger batch plays across segments, chat with AI agents, query the data warehouse with SQL, fetch live segment data
cargo-cli-storageSchemaInspect model DDL, create and update columns (custom, computed, metric, lookup), manage datasets, set model relationships
cargo-cli-connectionConnectorsAuthenticate connector instances, list available integrations and their action slugs, discover native actions
cargo-cli-aiAgentsCreate and configure agents, manage releases (draft → deploy), upload files for RAG, connect MCP servers, inspect memories
cargo-cli-analyticsMeasurementDownload run results, export segment data to files, pull per-node error rates and success metrics
cargo-cli-billingCostsTrack credit consumption by workflow, connector, or agent; check subscription status; view invoices
cargo-cli-workspaceAdminInvite users, create and rotate API tokens, organize resources into folders, manage roles

​
1. Install the CLI

Skills drive the CLI, so it has to be installed and authenticated first. Follow Install & authenticate, then confirm: 
cargo-ai whoami

​
2. Install the skills

npx skills add getcargohq/cargo-skills
This creates a .skills/ directory with seven skill files your agent reads automatically. Commit it so every team member and CI environment shares the same setup without a separate install step.

​
3. Verify

Ask your agent: 
What Cargo skills do you have available?
It will list the seven domains and what it can do with each.

​
Supported agents & editors

Any tool that follows the skills.sh standard works with the same install command — there’s no per-editor configuration, because .skills/ is the universal integration point.

Claude Code

Persist your token in your shell profile so it’s available from any working directory: export CARGO_API_TOKEN=<your-api-token> in ~/.zshrc or ~/.bashrc.

Cursor

Run the install command in your project root; Cursor’s agent picks up .skills/ automatically.

Codex CLI

Works out of the box once .skills/ is present in the working directory.

GitHub Copilot (agent mode)

Reads .skills/ from the repository root — commit it so Copilot loads it in every session.

Windsurf

Same one-command install; no additional configuration required.

Any skills.sh agent

Follows the open skills.sh standard, so new compatible editors work with the same command.

​
Troubleshooting

SymptomFix
Agent says it has no Cargo skillsRun npx skills add getcargohq/cargo-skills in the project root and restart the session
cargo-ai: command not foundRun npm install -g @cargo-ai/cli
Unauthorized errorsRun cargo-ai whoami to confirm the active token and workspace
Wrong workspace targetedRe-authenticate: cargo-ai login --token <token> --workspace-uuid <uuid>

​
Next steps

Examples

Worked examples: run tools, trigger plays, query the warehouse, build workflows, deploy agents, and more.

CLI Overview

Command reference, UUID flows, filter syntax, async patterns, and gotchas.

Cargo Skills on GitHub

Browse skill source, report issues, or contribute improvements.

skills.sh standard

Learn how skills work and how to author your own packages.