> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getcargo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Cargo Skills

> Install Cargo Skills and control your entire Cargo workspace with natural language prompts.

<Note>
  Want to suggest an edit, report an issue, or fork the skills? Head to
  [getcargohq/cargo-skills](https://github.com/getcargohq/cargo-skills) on
  GitHub.
</Note>

Without skills, an agent has to guess CLI commands, flags, and UUID discovery patterns. With Cargo Skills installed, it already knows them — 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.

***

## 1. Install the CLI

```bash theme={null}
npm install -g @cargo-ai/cli
cargo-ai login --token <your-api-token>
cargo-ai whoami
```

Get your API token from **Settings > API** in your Cargo workspace. Token values are shown only once — store immediately in a secrets manager.

<Tip>
  To target a specific workspace: `cargo-ai login --token <token> --workspace-uuid <uuid>`
</Tip>

***

## 2. Install the skills

```bash theme={null}
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](https://skills.sh) standard works with the same install command: **Claude Code**, **Cursor**, **GitHub Copilot** (agent mode), **Windsurf**, and **Codex CLI**. No per-editor configuration is needed — `.skills/` is the universal integration point.

For Claude Code specifically, persist your token in your shell profile so it's available from any working directory:

```bash theme={null}
export CARGO_API_TOKEN=<your-api-token>  # add to ~/.zshrc or ~/.bashrc
```

***

## Troubleshooting

| Symptom                           | Fix                                                                                      |
| --------------------------------- | ---------------------------------------------------------------------------------------- |
| Agent says it has no Cargo skills | Run `npx skills add getcargohq/cargo-skills` in the project root and restart the session |
| `cargo-ai: command not found`     | Run `npm install -g @cargo-ai/cli`                                                       |
| `Unauthorized` errors             | Run `cargo-ai whoami` to confirm the active token and workspace                          |
| Wrong workspace targeted          | Re-authenticate: `cargo-ai login --token <token> --workspace-uuid <uuid>`                |

***

## Next steps

<CardGroup cols={2}>
  <Card title="Cookbook" icon="book-open" href="/cli/cookbook">
    Eight worked examples: run tools, trigger plays, query the warehouse, build
    workflows, deploy agents, and more.
  </Card>

  <Card title="CLI Overview" icon="terminal" href="/cli/overview">
    Command reference, UUID flows, filter syntax, async patterns, and gotchas.
  </Card>

  <Card title="Cargo Skills on GitHub" icon="github" href="https://github.com/getcargohq/cargo-skills">
    Browse skill source, report issues, or contribute improvements.
  </Card>

  <Card title="skills.sh standard" icon="book" href="https://skills.sh">
    Learn how skills work and how to author your own packages.
  </Card>
</CardGroup>