Want to suggest an edit, report an issue, or fork the skills? Head to
getcargohq/cargo-skills on
GitHub.
The skills
The set is one skill per CLI command domain, plus acargo router that ties them together and a cargo-gtm outcome skill that
routes real-world GTM goals to the right capability skill:
1. Install the CLI
Skills drive the CLI, so it has to be installed and authenticated first. Follow the Quickstart, then confirm:2. Install the skills
.skills/ directory with the Cargo 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: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
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.

