cargo-gtm

• cargo-gtm

  — application library. The front door for any GTM task ("build a TAM list", "find 5 fintech CTOs", "monitor job changes"). Routes via internal recipes (

  ../cargo-gtm/recipes/*.md

  ) and provider playbooks (

  ../cargo-gtm/provider-playbooks/*.md

  ).
• Capability skills — standard library. One per CLI domain (orchestration, storage, connection, AI, content, context, analytics, billing, hosting, workspace management). Loaded by

  cargo-gtm

  , or directly when you need a specific CLI domain.

cargo-gtm

cargo-gtm

references/glossary.md

conjonction

Automated by the Cargo installer. Jobs 1 and 3 (refresh + session register/finalize) run on their own when the

SessionStart

/

SessionEnd

hooks scaffolded by

curl -fsSL https://api.getcargo.io/install.sh | sh

are present. Do them by hand only when those hooks aren't installed. Job 2 (reporting) is always your responsibility — it can't be automated.

• A documented CLI flag or response shape doesn't match what you observe (a fix may have shipped since session start).
• The user explicitly asks ("bump cargo", "make sure I'm on latest").

--help

cargo-ai workspaceManagement report create \
  --title "<one-line summary of the problem>" \
  --description "<exact command(s) tried, errorMessage, expected vs actual, UUIDs involved>"

• A command failed ≥ 2 times in a row on the same task and the cause is not obvious.
• The CLI is being misused and the correct usage is not discoverable from the skills, examples, or

  --help

  .
• A documented behavior contradicts what you observe.
• A feature appears to be missing entirely.

../cargo-workspace-management/SKILL.md

../cargo-workspace-management/references/examples/reports.md

cargo-orchestration

cargo-analytics

cargo-billing

cargo-storage

cargo-connection

cargo-ai

cargo-content

content

cargo-context

cargo-hosting

*.cargo.app

cargo-workspace-management

Agent knowledge for RAG: files + libraries live in the

content

domain →

cargo-content

; how they attach to an agent →

cargo-ai

. (Files/libraries moved out of the old

ai file …

path in CLI ≥ 1.0.19.)

            ┌─────────────────────────────────────┐
            │              cargo-gtm              │
            │   Outcome / front door for GTM      │
            │   Recipes, guides, provider-playbks │
            └─────────────────┬───────────────────┘
                              │ delegates to ↓ (one-way)
       ┌──────────────────────┴──────────────────────┐
       │                                             │
┌──────────────────────────────────────────────────────────────┐
│              cargo-workspace-management                      │
│         Authentication, users, tokens, folders               │
└──────────────────────────────────────────────────────────────┘

  ┌─────────────────┐   ┌────────────────────┐   ┌─────────────────┐
  │  cargo-storage  │   │  cargo-connection  │   │    cargo-ai     │
  │ Models, columns,│   │ Connectors,        │   │ Agents, docs,   │
  │ datasets        │   │ integration actions│   │ MCP, memory     │
  └────────┬────────┘   └─────────┬──────────┘   └────────┬────────┘
                                              (cargo-content feeds
                                               files/libraries to agents)
           │                      │  (UUIDs flow down)    │
           └──────────────────────┼───────────────────────┘
                                  ▼
             ┌───────────────────────────────────────┐
             │          cargo-orchestration          │
             │   Runs, batches, plays, tools, SoR    │
             └───────────────┬───────────────────────┘
                             │
              ┌──────────────┴──────────────┐
              ▼                             ▼
 ┌────────────────────────┐  ┌───────────────────────────┐
 │    cargo-analytics     │  │       cargo-billing       │
 │  Results, metrics,     │  │    Credit usage, costs    │
 │  exports               │  │                           │
 └────────────────────────┘  └───────────────────────────┘

             ┌───────────────────────────────────────┐
             │             cargo-context             │
             │  Git-backed GTM markdown knowledge:   │
             │  personas, plays, proof, signals…     │
             └───────────────────────────────────────┘
           (orthogonal: not part of the workflow flow)

• cargo-gtm

  delegates to capability skills via relative paths (

  ../cargo-orchestration/...

  ). Capability skills never reference

  cargo-gtm

  .

• cargo-workspace-management

  provides auth context for every skill — set it up first.

• cargo-storage

  ,

  cargo-connection

  , and

  cargo-ai

  are peer skills that supply UUIDs to

  cargo-orchestration

  . They don't depend on each other.

• cargo-content

  owns workspace files and libraries (the

  content

  domain). It produces file/library UUIDs that

  cargo-ai

  consumes as agent release

  resources

  (RAG). Uploaded content files also surface read-only under

  .files/

  in the

  cargo-context

  runtime sandbox.

• cargo-context

  is orthogonal to the workflow-execution flow. It touches the git-backed GTM knowledge base (markdown/MDX), not storage or workflow runs. Use it for capturing/editing the workspace's prose context — personas, plays, proof, objections, signals — and for inspecting the typed knowledge graph.
• For SQL queries against storage, use

  cargo-ai storage query execute "<sql>"

  (tables as

  <datasetSlug>.<modelSlug>

  ). Load

  cargo-storage

  to discover dataset and model slugs, and to fetch the DDL when you need column types or the SQL dialect.
• For SQL queries against orchestration runtime tables (

  runs

  ,

  batches

  ,

  spans

  ,

  records

  ) — error rates, per-node failures, time-series — use

  cargo-ai orchestration query execute "<sql>"

  . Workspace scoping is automatic; tables are referenced without a schema prefix.
• Before building a workflow node graph, load

  cargo-connection

  to get

  connectorUuid

  and

  actionSlug

  .
• Before executing a workflow that uses an agent node, load

  cargo-ai

  to get

  agentUuid

  .
• After runs complete, load

  cargo-analytics

  to download results or measure performance. For action output retrieval, prefer

  cargo-ai orchestration run download-outputs

  over

  run download

  — the former returns a signed-URL CSV/JSON of just the output node's data.
• Load

  cargo-billing

  to understand credit consumption for any of the above.

SKILL.md

guides/

recipes/

provider-playbooks/

references/

agents/

recipes/prospecting.md

recipes/build-tam.md

recipes/linkedin-url-lookup.md

recipes/portfolio-prospecting.md

recipes/job-change-monitoring.md

waterfall.detectJobChange

recipes/funding-watch.md

recipes/tech-intent.md

recipes/icp-discovery.md

recipes/outreach-activation.md

recipes/re-engagement.md

recipes/lost-deal-revival.md

lost_reason

recipes/account-expansion.md

• All recipes use credits-based actions (

  cargo-ai connection integration list

  → 141 credits-based actions across 120 integrations).
• Action shape:

  {"kind":"connector","integrationSlug":"<slug>","actionSlug":"<slug>","config":{}}

  — no

  connectorUuid

  in

  config

  .
• Output retrieval:

  cargo-ai orchestration run download-outputs --output-node-slug <slug>

  (NOT

  run download

  ).
• peopleDataLabs filter shape:

  searchX

  uses cargo's

  {conjonction, groups, conditions}

  shape;

  queryX

  takes a PDL SQL string — never Elasticsearch.

../cargo-gtm/SKILL.md

runs

batches

spans

records

• See the decision flowchart at the top of

  ../cargo-orchestration/SKILL.md

  for when to use

  action execute

  vs

  run create

  vs

  batch create

  .
• Prefer built-in actions + expressions when building a node graph. Avoid

  python

  ,

  script

  (JS), and raw HTTP nodes unless necessary: use

  variables

  for transforms, the native

  agent

  node for LLM calls, the integration's dedicated connector action for APIs, and

  branch

  /

  filter

  /

  switch

  for routing. See

  ../cargo-orchestration/references/node-selection.md

  .
• Filter JSON uses

  conjonction

  (not

  conjunction

  ) — breaks silently if misspelled.
• Query orchestration runtime tables (ClickHouse) with

  cargo-ai orchestration query execute "<sql>"

  against

  runs

  ,

  batches

  ,

  spans

  ,

  records

  (no schema prefix; workspace scoping is automatic).
• For SQL against workspace storage (Companies, Contacts, …), use

  cargo-ai storage query execute "<sql>"

  — documented in

  cargo-storage

  .
• All operations are async — poll or pass

  --wait-until-finished

  . See Async polling.

../cargo-orchestration/SKILL.md

• segment download

  requires

  --model-uuid

  , not

  --segment-uuid

  .
• For batch result download, get the

  output-node-slug

  from

  release get <release-uuid>

  →

  nodes[].slug

  .
• For billing and credit usage, use

  cargo-billing

  instead.

../cargo-analytics/SKILL.md

• Requires a token with admin access.
• Invoice amounts are in cents — divide by 100 for dollars.

• subscriptionAvailableCreditsCount - subscriptionCreditsUsedCount

  from

  subscription get

  = remaining credits.

../cargo-billing/SKILL.md

• Query via

  cargo-ai storage query execute "<sql>"

  (or

  storage query download --query "<sql>"

  for full exports) using

  <datasetSlug>.<modelSlug>

  table names (e.g.

  default.companies

  ).

  model get-ddl

  is optional — useful for column types and SQL dialect.
• For SQL against orchestration runtime tables (

  runs

  /

  batches

  /

  spans

  /

  records

  ), use

  cargo-ai orchestration query execute "<sql>"

  — documented in

  cargo-orchestration

  .
• For advanced record queries (filtering, sorting, pagination), use

  segmentation segment fetch

  from

  cargo-orchestration

  .

../cargo-storage/SKILL.md

connectorUuid

actionSlug

• Integration = external service type (HubSpot, Clearbit, Salesforce, …)
• Connector = authenticated instance of an integration (referenced by

  connectorUuid

  in nodes)

../cargo-connection/SKILL.md

• Knowledge for RAG attaches to an agent via the release's

  resources

  : files + libraries come from

  cargo-content

  . Wire them in with

  release update-draft --resources …

  then

  release deploy-draft

  .
• CLI ≥ 1.0.19: files and libraries moved out of the

  ai

  domain into the top-level

  content

  domain (now the

  cargo-content

  skill). The old

  cargo-ai ai file …

  commands no longer exist.

For using agents (sending messages, multi-turn chat, polling), use

cargo-orchestration

.

../cargo-ai/SKILL.md

../cargo-ai/SKILL.md

native

connector

• New top-level

  content

  domain in CLI ≥ 1.0.19 —

  cargo-ai content file …

  /

  cargo-ai content library …

  . The old

  cargo-ai ai file …

  path is gone (

  unknown command

  → you're on the old path; bump the CLI).
• A file or library is inert until attached to an agent's deployed release

  resources

  — that wiring lives in

  cargo-ai

  .
• Uploaded content files are also readable (read-only) under

  .files/

  in the

  cargo-context

  runtime sandbox.
• For batch-run input files (CSVs that drive a batch), use

  cargo-ai workspaceManagement file upload

  (a different surface) — see

  cargo-workspace-management

  .

../cargo-content/SKILL.md

• Context repository = the GitHub repo backing the workspace's context. Canonical example:

  getcargohq/cargo-workspaces

  . Files use

  kebab-case.md

  names, YAML frontmatter with required

  title

  +

  description

  , and

  domain/slug

  cross-refs (no

  .md

  ).
• Runtime sandbox = a checked-out, executable copy of the context repo.

  runtime write

  and

  runtime edit

  push to the default branch;

  runtime execute

  does not push.
• Knowledge graph = the typed graph over every md/mdx file, with frontmatter and outbound cross-refs per node. Built via

  cargo-ai context graph get

  .

• runtime write

  /

  runtime edit

  commit and push.

  runtime execute

  is ephemeral — use it for

  grep

  /

  ls

  /inspection, never for persistent changes.

• runtime edit --old-string

  must match the file content exactly once. Read first, copy whitespace verbatim.
• Set

  title

  +

  description

  frontmatter on every

  .md

  /

  .mdx

  file — a strong convention, not enforced: missing/malformed frontmatter is still committed, it just indexes poorly (graph falls back to filename + first paragraph, and reads

  summary

  , not

  description

  ).
• Graph edges form only from frontmatter

  references:

  , markdown links, or wikilinks — a bare path in prose creates no edge. Cite source files in

  references:

  .
• For domains, conventions, and per-domain templates, see

  ../cargo-context/references/conventions.md

  .

• For bootstrapping a fresh workspace's context from a domain (ICP, personas, proof, signals — idempotent, skips already-seeded domains), see

  ../cargo-context/references/examples/bootstrap-from-domain.md

  .
• For the full bootstrap + ongoing call-driven refresh playbook (Phase 1 + Phase 2 + cadence), see

  ../cargo-context/references/examples/lifecycle.md

  .

../cargo-context/SKILL.md

https://<slug>.cargo.app

@cargo-ai/app-sdk

fetch(request, env)

@cargo-ai/worker-sdk

init

create

deployment create

deployment promote

• --slug

  is the live subdomain — globally unique within the hosting domain.
• Deploying ≠ going live.

  deployment create

  builds; the URL only moves on

  deployment promote

  .

  deployment get-promoted

  shows what's live.

• --source

  is the package root, not

  dist/

  — the build (

  npm ci && vite build

  for apps, bundling for workers) runs server-side.
• Builds are async — poll

  deployment get

  until terminal before promoting.

• --app-uuid

  /

  --worker-uuid

  are mutually exclusive on deployment commands;

  remove

  cascades to deployments.
• Folders come from

  cargo-workspace-management

  ;

  --folder-uuid null

  moves to root.

../cargo-hosting/SKILL.md

• Most commands require a token with admin access.

• workspaceManagement token create

  requires

  --name

  (the legacy

  --from-user

  flag was removed). Pick a name that makes the token's purpose obvious in

  token list

  later.
• Token values are only shown once at creation — store immediately in a secrets manager (GitHub Secrets, AWS Secrets Manager, etc.).
• Always send a

  workspaceManagement report create

  when the CLI errors, is being used incorrectly, or you (user or agent) are struggling to make progress on a CLI task — see the section at the top of this file and

  ../cargo-workspace-management/references/examples/reports.md

  .

../cargo-workspace-management/SKILL.md