营销与写作

cargo-gtm

getcargohq/cargo-skills

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 basis, suppression lists, and volume limits gate every step that touches a person (`references/acceptable-use.md`); bulk unsolicited messaging, purchased or scraped lists, and consumer targeting are refused. Triggers: "build me a list of", "find 50 <title> at <segment>", "who works at", "find work emails for these accounts", "enrich this CSV", "verify these emails", "build a TAM", "who fits our ICP", "who actually buys from us", "what data points should we collect on accounts", "our outbound is reaching the wrong people", "score these leads", "write a first-touch email", "push these to my CRM", "who changed jobs", "who just raised funding", "companies using <tech>", "who is hiring <role>", "find the buying committee", "portfolio companies of <investor>", "upload this audience to Google/Meta/LinkedIn ads". Providers: aiArk, anthropic, apolloio, bounceban, bouncer, brightData, builtwith, cargoSignals, cleon1, companyEnrich, contactOut, datagma, dropcontact, enrichCrm, enrichley, enrowio, exa, explorium, findyMail, firecrawl, forager, FullEnrich, g2, gemini, hunter, icypeas, kitt, leadMagic, linkedin, linkup, mixrank, neverBounce, oceanio, openAi, parallel, peopleDataLabs, perplexity, piloterr, pipecorn, prospeo, proxycurl, reverseContact, rocketreach, salesNavigator, serper, sillage, snitcher, societeInfo, storeleads, theirStack, theSwarm, typesafe, waterfall, x, zeroBounce. Reads phase guides, recipes, and per-provider playbooks before any paid call. Skip when: a run already happened and misbehaved — use cargo-diagnostics.

  • 1万 次安装
  • 21 星标
  • 收录于

安装命令

npx skills add https://github.com/getcargohq/cargo-skills --skill cargo-gtm

SKILL.md

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. The short version, binding on every recipe here:

  • B2B professional identities only, from the licensed providers in 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, batch or automated posting / replying / liking / DMing from the user's X account (xAccount). 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.