cargo-gtm（货物总吨位）

Cargo GTM — Meta Skill

Use this skill for prospecting, account research, contact enrichment, verification, lead scoring, personalization, signal monitoring, and campaign activation.

1) What this skill governs

• Route GTM decisions, safety gates, and provider/quality defaults before execution.
• Keep long command chains and tooling nuance in sub-docs; provider-specific implementation detail in provider-playbooks/*.md.
• Anchor recipes in credits-based actions (the high-value action calls). Free CRUD (createLead, getLead, deleteRecords) doesn't need this skill — agents can compose those ad hoc.

Process / goal

The user is generally trying to go from "I have an ICP" to "Here's a list of prospects with verified emails and personalized signals." They may be anywhere in this process — guide them along.

Discovery order: companies first, then people. When the task requires finding contacts at companies matching criteria (portfolio, ICP, hiring signal), discover the company set first, then find people at each company. Don't start with broad people-search queries.

Documentation hierarchy

• Level 1 — SKILL.md (this file): decision model, guardrails, routing table, links to sub-docs.
• Level 2 — Phase docs: guides/finding-companies-and-contacts.md, guides/enriching-and-researching.md, guides/writing-outreach.md.
• Level 2.5 — Recipes: recipes/*.md — step-by-step playbooks for specific scenarios.
• Level 3 — Provider playbooks: provider-playbooks/<slug>.md — provider-specific quirks, costs, and fallback behavior.

2) Read behavior — MANDATORY before any execution

STOP. Do not call any provider, run any cargo-ai orchestration action execute command, or write any search query until you have opened the correct sub-doc for your task.

These docs encode what works, what fails, and why. They contain validated parameter schemas, cheapest-provider mappings, parallel execution patterns, sample payloads, and known pitfalls. Reading the right doc for 10 seconds saves 10 failed action calls, wasted credits, and garbage output.

Routing rules — match your task to a doc and READ IT

Recipes: step-by-step playbooks (check before executing)

Scan this list and read the recipe matching your task. When a recipe matches: follow it step-by-step as your execution plan.

If none match, scan the phase docs above for the closest pattern and adapt — or invoke agents/execution-plan-creator.md to compose a custom chain with provider/action slugs and cost estimates.

3) Priority provider stack (recipes lead with these 6)

These six credits-based providers cover the full prospecting → enrichment → verification → signal pipeline at the lowest credit cost in the catalog. Every recipe in this skill's recipes/ leads with this stack:

See provider-playbooks/ for per-provider deep dives. See references/stage-action-map.md for the complete cheapest-action-per-stage table across the full 120-integration catalog.

4) Recipe spine (default chain)

1. SOURCE   → salesNavigator.searchLeads / searchAccounts            (0.02–0.05/record)
2. DEDUPE   → cargo.matchProspect / cargo.matchBusiness              (0.5/record)
3. ENRICH   → cargo.enrichBusinessFirmographics / Technographics
              + waterfall.enrichContact / enrichCompany              (0.5–2/record)
4. SIGNAL   → cargo.enrichBusinessFundingAndAcquisitions
              + theirStack.searchJobs
              + waterfall.detectJobChange                            (0.5–3/record)
5. CONTACT  → FullEnrich.findEmail (fallback peopleDataLabs)         (1–3/record)
6. VERIFY   → waterfall.verifyEmail                                  (0.1/record)
7. BACKFILL → peopleDataLabs.enrichPerson (only if step 5 missed)    (3/record)

Adapt by phase: drop steps that aren't relevant to the user's goal. For pure sourcing, run step 1 only. For "enrich a list I already have," run steps 2–7.

5) Output retrieval — use run download-outputs, not run download

When the agent needs the actual data produced by an action (enriched fields, found emails, search results), use:

cargo-ai orchestration run download-outputs \
  --workflow-uuid <uuid> \
  --output-node-slug <slug> \
  --format json \
  --is-finished

Returns {"url": "..."} — a signed URL to a CSV/JSON containing only the output node's data. Faster and cheaper than run download (which pulls full run records). See references/output-retrieval.md and ../cargo-analytics/SKILL.md.

6) Action shape rules (every recipe)

Every action JSON in this skill follows the rules in ../cargo-orchestration/references/actions.md:

• kind: "connector" action shape: {"kind":"connector","integrationSlug":"<slug>","actionSlug":"<slug>","config":{}}. connectorUuid is NOT in config — the platform resolves the workspace's authenticated connector from integrationSlug automatically.
• For multi-step node graphs: connectorUuid lives at the top level of the node, not in config. Cross-node interpolation uses {{nodes.<slug>.<field>}}. Agent node outputs wrap under .answer (read as {{nodes.<slug>.answer.<field>}}).

7) When stuck — file a workspace report

If a recipe fails repeatedly and the cause isn't obvious, escalate via cargo-ai workspaceManagement report create. See ../cargo-workspace-management/SKILL.md (Reports section).

8) Provider playbooks

Per-provider deep dives for the priority stack. Long-tail providers don't have dedicated playbooks yet — fall back to references/alternatives.md and references/stage-action-map.md.

Priority stack:

• provider-playbooks/salesNavigator.md — cheapest sourcing in the catalog (0.02–0.05/record).
• provider-playbooks/cargo.md — 22 native enrichment + signal actions; the match* actions are key for dedup.
• provider-playbooks/waterfall.md — swiss-army-knife: enrichment, verification, and the cargo-unique detectJobChange signal.
• provider-playbooks/FullEnrich.md — premium contact lookup; reverseEmailLookup is unique.
• provider-playbooks/theirStack.md — tech-stack + hiring-intent signals.
• provider-playbooks/peopleDataLabs.md — heavyweight backfill at flat 3-credit tier.

9) References

• references/stage-action-map.md — cheapest credits-based action per stage across the full 120-integration catalog.
• references/credits-cost-table.md — auto-generated cost table for all 141 credits-based actions.
• references/waterfall-strategy.md — canonical waterfall chains by enrichment goal (every recipe's "fallback" follows these).
• references/alternatives.md — provider swap-ins from the long tail when the priority stack can't serve.
• references/output-retrieval.md — run download-outputs patterns for fetching action data.