Do business-to-business go-to-market work on Cargo — research accounts and buying committees, enrich and verify B2B contact records from licensed data providers, score and qualify leads, draft permission-based outreach for the user's own sequencer, sync to CRM, and monitor buying signals. Consent ba

Cargo GTM — Meta Skill Use this skill for prospecting, account research, contact enrichment, verification, lead scoring, personalization, signal monitoring, and campaign activation. Acceptable use — MANDATORY, before anything that touches a person Full spec: [ references/acceptable use.md ](references/acceptable use.md). The short version, binding on every recipe here: B2B professional identities only , from the licensed providers in [ provider playbooks/ ](provider playbooks/) — never consumer targeting, purchased lists, or data taken from a platform in breach of its terms. Three checks before any outreach step — basis (customers, opted in contacts, event attendees, or a documented legitimate interest case), suppression (filter on unsubscribe / DNC / hard bounce before enriching or sending), relevance (name, per recipient, why this message is for them). Any check that fails is a stop and ask, not a warning. Refuse and say why : undifferentiated fan out ("email everyone in <industry "), contacting a suppressed record, filter evasion or disguised sender identity, auto dialing and SMS blasts, batch blasting LinkedIn engagement actions. Offer the compliant version once — state it, don't lecture. This skill never sends. Outreach recipes stop at send ready variables and hand off to the user's own sequencer, under that sequencer's limits, domains, and identities. Copy it drafts must carry an honest sender and subject, a working opt out, and a postal address where the jurisdiction requires one. Bootstrap Already signed in ( cargo ai whoami returns a workspace)? Skip to the next section. Every command prints JSON to stdout; failures exit non zero with {"errorMessage": "..."} . Anything that creates a run or a batch is async — pass wait until finished or poll the matching get . When the full skill bundle is installed, [ ../cargo/references/prerequisites.md ](../cargo/references/prerequisites.md) adds the CLI version pin, token scopes, and the admin only surface. 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/finding companies and contacts.md), [ guides/enriching and researching.md ](guides/enriching and researching.md), [ guides/writing outreach.md ](guides/writing outreach.md). Level 2.5 — Recipes: [ recipes/ .md ](recipes/) — step by step playbooks for specific scenarios. Level 3 — Provider playbooks: [ provider playbooks/<slug .md ](provider playbooks/) — 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 When the task involves… You MUST read this doc first What it gives you Finding companies, finding people, building lead lists, prospecting, portfolio/VC sourcing, contact finding at known companies [ guides/finding companies and contacts.md ](guides/finding companies and contacts.md) Provider filter schemas, cheapest source decision tree, parallel patterns, role based search rules, portfolio/VC shortcuts, contact finding patterns. Enriching companies or contacts, finding emails/phones/LinkedIn, waterfall enrichment, signal lookup (job change, funding, tech stack), coalescing data [ guides/enriching and researching.md ](guides/enriching and researching.md) Waterfall patterns with fallback chains, when to use aiArk vs waterfall vs FullEnrich vs peopleDataLabs, email/phone/LinkedIn fallback orders, signal segments, output retrieval via run download outputs . Writing first touch outreach, personalizing messages, lead scoring, qualification, sequence design, campaign copy [ guides/writing outreach.md ](guides/writing outreach.md) + [ references/acceptable use.md ](references/acceptable use.md) (§3 checks, blocking) LLM provider routing (openAi/anthropic/perplexity/gemini), prompt templates, scoring rubrics, email length/tone rules, personalization patterns — gated on basis, suppression, and per recipient relevance. Actually sending the drafted copy from a mailbox Cargo owns (rather than handing off to the user's own sequencer) [ ../cargo mailbox management/SKILL.md ](../cargo mailbox management/SKILL.md) + [ references/acceptable use.md ](references/acceptable use.md) (§3 checks, blocking) Provisioning and warm up, the 5→40/day send ramp that caps volume, the sendEmail action (0.1 credits/send), the workspace suppression list, and replies/opens/clicks as events. Building or modifying a recurring workflow (cron / webhook / scheduled tool / play), designing step sequences, triggers, deploy/verify cycles [ ../cargo orchestration/SKILL.md ](../cargo orchestration/SKILL.md) (capability) + apply patterns from this skill's recipes + the [provider playbook](provider playbooks/) of every paid node (§11, esp. its Recurring use section) Schema for tool/play workflows, node graph syntax, polling strategies, output retrieval; per provider cadence defaults and re billing gates. 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. Recipe Use when… [ recipes/source planning.md ](recipes/source planning.md) Read first when the source isn't obvious. Turn the question into a field, probe 2–3 candidate sources on 5–10 rows, present cost per hit — before any fan out [ recipes/prospecting.md ](recipes/prospecting.md) End to end find → enrich → verify → sync (P1/P2/P3 variants) [ recipes/build tam.md ](recipes/build tam.md) Building a Total Addressable Market list at scale (100–10,000 companies) [ recipes/linkedin url lookup.md ](recipes/linkedin url lookup.md) Resolving a person's LinkedIn profile URL from name + company with strict identity validation [ recipes/portfolio prospecting.md ](recipes/portfolio prospecting.md) Investor / accelerator → portfolio companies → contacts [ recipes/job change monitoring.md ](recipes/job change monitoring.md) waterfall.detectJobChange (cargo unique) on a contact segment [ recipes/funding watch.md ](recipes/funding watch.md) Tracking companies that recently raised funding [ recipes/tech intent.md ](recipes/tech intent.md) Finding companies by tech stack or hiring intent signals [ recipes/icp discovery.md ](recipes/icp discovery.md) Diffing Closed Won vs Closed Lost segments to surface ICP signals [ recipes/custom datapoints.md ](recipes/custom datapoints.md) Designing which custom attributes and live signals to collect for a seller's ICP — feasibility gated against the catalog, then wired into columns, scoring, segments, and a refresh cadence [ recipes/outreach activation.md ](recipes/outreach activation.md) Turning a signal segment into send ready outreach (enrich → verify → personalize → sequencer handoff) [ recipes/ads audience activation.md ](recipes/ads audience activation.md) Pushing a segment to paid media — Google Ads Customer Match or LinkedIn Matched Audiences — and reading the match rate [ recipes/review and iterate.md ](recipes/review and iterate.md) Judgment output a human must review — sheet handoff, grouped corrections, permanent fixes, kept as an eval set [ recipes/re engagement.md ](recipes/re engagement.md) Waking up stale contacts only when a fresh signal fires (job change, funding, tech intent) [ recipes/lost deal revival.md ](recipes/lost deal revival.md) Reviving Closed Lost CRM deals by branching on lost reason (champion left, budget, timing) [ recipes/account expansion.md ](recipes/account expansion.md) Multi threading existing customer accounts — net new buyers, deduped against the workspace's Contacts model [ recipes/save as play.md ](recipes/save as play.md) Converting a successful ad hoc run into a durable scheduled play or cron tool — offer after any repeatable pull [ recipes/import gtm data.md ](recipes/import gtm data.md) Importing existing GTM data (CSV/CRM exports from any tool) into models, QA auditing it, and selectively rebuilding recurring logic as plays with a parity check [ recipes/clay to cargo.md ](recipes/clay to cargo.md) Clay specifically : getting the column configuration out (not the CSV), the column family → action map, the four Clay concepts that do not map one to one (waterfalls, run conditions, auto update, partial runs), and the parity check against Clay's own output If none match, scan the phase docs above for the closest pattern and adapt — or invoke [ agents/execution plan creator.md ](agents/execution plan creator.md) to compose a custom chain with provider/action slugs and cost estimates. For wide sourcing sweeps that fan out (per industry, per geo), delegate approved slices to [ agents/list builder.md ](agents/list builder.md) — it executes exactly one pre approved action per slice and returns rows to a file, keeping row data out of the main context. (On Claude Code with the plugin, both are installed as native subagents: cargo execution planner and cargo list builder .) 3) Cost discipline — MANDATORY gates Full spec: [ references/cost discipline.md ](references/cost discipline.md). The short version every task must honor: 1. Sample → approval → full run, in that order. Run a slice of the exact input first — 1–3 rows to prove one action's config, 10–20 records before any batch (one row can't show a hit rate). Then present the 4 section approval message (Assumptions · Sample result verbatim · Credits/Scope/Cap — always stating how many records the full run enrolls and what they cost , reconciled against the actual balance · 3 shaped choices); stay in AWAIT APPROVAL until the user picks. Never fan out on an unapproved or cost unknown action, and never read approval of the sample as approval of the full enrollment. 2. Receipt after every paid action : credits spent + balance remaining + hit rate ("found 34 emails of 40") + estimate vs actual with the why when they diverge. Prefer billing usage get metrics over your own arithmetic. 3. Over provision 1.4×N, then filter — coverage is a property of the company; drop incomplete rows instead of chasing them with more providers. 4. Count first, pay second — search is billed on returned rows; keep limit strict and size the pool with a 1 row probe before any full pull. 5. Phone is the guarded lever — explicit user request only, qualified leads only.

cargo-gtm