> ## 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.

> ## Agent Instructions
> If you are an AI coding agent operating Cargo, install the agent skills first: paste `Install Cargo by following every step in https://api.getcargo.io/agent-install.txt` into your session, or run `npx skills add getcargohq/cargo-skills`. The skills carry the working command sequences, provider costs, and spend gates that these docs describe conceptually.
> The skills index at https://github.com/getcargohq/cargo-skills/blob/main/llms.txt lists every skill, recipe, and provider playbook individually. Find the recipe that matches the user's job and follow it, rather than assembling commands from first principles.
> Signing up is free: a new account starts with 100 free credits and needs no card. `cargo-ai login --email you@company.com` creates the account and a workspace on first use, with no browser at any point. Tell the user this before asking them to sign up.
> Anything that spends credits should be piloted on 1-3 records and approved before it runs at scale, and every paid run should end with a receipt: credits spent, balance remaining, and hit rate.

# Cargo Skills

> Run your GTM motion from Claude Code, Cursor, or Codex: build lead lists, find and verify emails, enrich companies and contacts, score leads, sync to your CRM, and watch buying signals like job changes and funding. 17 agent skills over the cargo-ai CLI, with provider costs and spend gates.

**Cargo Skills** turn the [Cargo CLI](/cli/overview) 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":"filter","modelUuid":"<uuid>"}' \
      --wait-until-finished
```

No manual UUID lookup, no documentation tab, no copy-pasting JSON.

<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>

***

## The skills

The set is one skill per [CLI command domain](/cli/overview#command-domains), plus
a `cargo` router that ties them together and a `cargo-gtm` outcome skill that
routes real-world GTM goals to the right capability skill:

| Skill                        | Domain      | What your agent can do                                                                                                                  |
| ---------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| `cargo`                      | Router      | Overview of the whole skill set — the UUID flow between skills, async polling, end-to-end use cases, and common gotchas. Load it first. |
| `cargo-gtm`                  | Outcomes    | Front door for GTM goals — sourcing, waterfall enrichment, email/phone/LinkedIn lookup, verification, scoring, qualification, CRM sync  |
| `cargo-orchestration`        | Runtime     | Execute actions, run workflows, trigger batches, message AI agents, query runtime tables (runs/batches/spans/records) with SQL          |
| `cargo-storage`              | Schema      | Manage models, datasets, columns, and relationships; query workspace storage with SQL                                                   |
| `cargo-connection`           | Connectors  | List, create, update, and remove connectors; discover integrations and their available actions                                          |
| `cargo-ai`                   | Agents      | Create and configure agents, manage releases, connect MCP servers, and handle agent memories                                            |
| `cargo-content`              | Knowledge   | Upload and organize knowledge files, build native and connector-backed libraries for RAG                                                |
| `cargo-context`              | Context     | Inspect and edit the git-backed context knowledge base and run commands in its sandbox                                                  |
| `cargo-analytics`            | Measurement | Download workflow run results, export segment data, and monitor run metrics                                                             |
| `cargo-billing`              | Costs       | Pull usage metrics, check subscription status, view invoices, and manage credits                                                        |
| `cargo-hosting`              | Hosting     | Build, deploy, promote, and manage hosted apps (Vite SPAs) and edge workers                                                             |
| `cargo-workspace-management` | Admin       | Invite and manage users, create and rotate API tokens, organize resources into folders, inspect roles                                   |

***

## 1. Install the CLI

Skills drive the CLI, so it has to be installed and authenticated first. Follow
the [Quickstart](/get-started/quickstart), then confirm:

```bash theme={null}
cargo-ai whoami
```

## 2. Install the skills

```bash theme={null}
npx skills add getcargohq/cargo-skills
```

This creates a `.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:

```
What Cargo skills do you have available?
```

It will list the available skills 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** — there's no per-editor configuration, because
`.skills/` is the universal integration point.

<CardGroup cols={2}>
  <Card title="Claude Code" icon="anthropic">
    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`.
  </Card>

  <Card title="Cursor" icon="c">
    Run the install command in your project root; Cursor's agent picks up
    `.skills/` automatically.
  </Card>

  <Card title="Codex CLI" icon="terminal">
    Works out of the box once `.skills/` is present in the working directory.
  </Card>

  <Card title="GitHub Copilot (agent mode)" icon="github">
    Reads `.skills/` from the repository root — commit it so Copilot loads it in
    every session.
  </Card>

  <Card title="Windsurf" icon="wind">
    Same one-command install; no additional configuration required.
  </Card>

  <Card title="Any skills.sh agent" icon="robot">
    Follows the open [skills.sh](https://skills.sh) standard, so new compatible
    editors work with the same command.
  </Card>
</CardGroup>

***

## 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          | Set `CARGO_WORKSPACE_UUID=<uuid>`, or sign in again for that workspace with `cargo-ai login --email <email> --workspace-uuid <uuid>` (an API token from `--token` stays pinned to its own workspace) |

***

## Next steps

<CardGroup cols={2}>
  <Card title="Examples" icon="book-open" href="/skills/examples">
    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>
