Office hours: Build your self-driving GTM engine·Oct 29, 9:00am PT, onlineRegister→
Cargo
  • PrimitivesData ModelsYour companies, contacts and deals, merged from every sourceContextWhat your team knows, as files every agent readsTerritoriesWho sells where, defined onceMailboxesMailboxes in your reps' names, warmed up and kept under limitsToolsThe actions your agents, plays and reps callAgentsAI that researches, decides and writes, reading your contextPlaysWorkflows that run on a trigger or a schedule, with retriesAppsInternal apps for your reps, hosted on Cargo
    Add-onsChrome ExtensionSell faster, right in your browserButtonTrigger AI agents inside your CRMFormTurn any tool into an embeddable formSlackTag Cargo in Slack. It does the GTM workGitHubPlan on every pull request, deploy on merge
    MoreProjectsDefine your entire GTM in codeCLIUse Cargo from your terminalMCPUse Cargo from Claude and ChatGPTDeveloper resourcesCargo API docs, OpenAPI spec, auth docs, webhooks, MCP serverAPI ReferenceExplore the Cargo APIDocumentationLearn how to use CargoIntegrationsConnected to your entire GTM stack
  • VeriffHow Veriff replaced MuleSoft with Cargo under NetSuite, Stripe and SalesforceAugmentHow Augment Code routes developer sign-ups to reps in under an hourWeights & BiasesHow Weights & Biases ships a new purchase signal in 2 days on CargoSee all
  • Pricing
  • Cookbooks
  • Blog
Sign in
Blog

OpenClaw for GTM: Give Your Agent Prospecting, Enrichment and Outbound Skills

7 Oct8min read
AurelienAurelien

OpenClaw can already do go-to-market work. It just has nothing to do it with. It runs on your own machine, answers you in Slack, Telegram, WhatsApp or iMessage, schedules its own jobs and loads skills that follow the AgentSkills standard. Ask it to find fifty heads of RevOps at Series B fintechs and it will open a browser, search, and hand you a list that is half guesses, because it has no B2B data, no email verification and no account at any provider that has either.

That is the gap Cargo’s skills fill. Install them and the same request runs against licensed data providers through one CLI, with verified emails, a cost receipt and a record of the run. The skills are on ClawHub under @cargo-ai, they work the same way in Hermes Agent, and a new Cargo account starts with 100 free credits and no card.

What the skills give your agent #

Two packs, both public and both published to ClawHub on every change.

The platform pack (19 skills). One skill per Cargo domain: cargo-gtm for sourcing, enrichment, scoring and outreach drafts, cargo-storage for querying your data, cargo-orchestration for running workflows and batches, cargo-mailbox-management for sending, cargo-diagnostics for explaining a run that went wrong, and a router skill, cargo, that tells the agent which of the others to load.

The job pack. One skill per job, each named for the job rather than for Cargo, so the agent finds it by what you asked: find-work-email, build-tam-list, find-stakeholders, track-job-changes, track-funding-rounds, find-companies-using-tech, verify-email-list, score-leads, research-account. The skills carry the procedure, not the data. The data comes from the providers Cargo connects to, which is why every skill needs the cargo-ai CLI and a signed-in workspace.

Install in OpenClaw #

Install the CLI first. OpenClaw checks each skill’s requirements, and a Cargo skill without cargo-ai on the path stays installed but hidden: openclaw skills info cargo-gtm reports Needs setup and Visible to model: no until the binary exists.

shellscript
npm install -g @cargo-ai/cli

openclaw skills install @cargo-ai/cargo
openclaw skills install @cargo-ai/cargo-gtm
openclaw skills install @cargo-ai/find-work-email

That installs into the current agent’s workspace. Add --global to share the skills across agents. To take the whole platform pack in one command instead of one skill at a time:

shellscript
npx skills add getcargohq/cargo-skills --agent openclaw -g

Check that the agent can see them:

shellscript
openclaw skills info cargo-gtm   # ✓ Ready, Visible to model: yes

OpenClaw’s own guidance applies to these as to any third-party skill: read it before you enable it. Every skill is plain markdown, and the source is in getcargohq/cargo-skills and getcargohq/gtm-skills.

Sign the agent in #

Sign-up runs entirely in the terminal and creates the account on first use, so there is no separate sign-up step:

shellscript
cargo-ai login --email you@company.com                 # sends a code, then exits
cargo-ai login --email you@company.com --code 123456
cargo-ai whoami

Do this on the machine that runs the OpenClaw gateway, because that is where the skills execute. On a box that runs unattended, use an API token instead of your personal session: create one under Settings → API, scoped to one workspace, and give the gateway CARGO_API_TOKEN. A saved login acts as you across every workspace you belong to. A token can be scoped down and revoked from the dashboard.

The 100 free credits are valid for the account’s first 30 days and come to about 500 leads sourced (salesNavigator.searchLeads, 0.2 credits a lead), 1,000 verified-email enrichments (aiArk.enrichPerson, 0.1 credits each), or 50 fully enriched contacts (waterfall.enrichContact, 2 credits each).

What to ask it #

Ask the way you would ask a colleague, from whichever channel the agent lives in. The skills’ triggers are written in that voice:

  • “Find 50 heads of RevOps at Series B fintechs in France.”
  • “Find work emails for the people in this CSV.”
  • “Who on our customer list changed jobs this month?”
  • “Which companies in this list use Snowflake?”
  • “Research Acme before my call and give me a brief with sources.”

The agent loads the router, picks the skill, and runs the job through the CLI, and each run reports what it spent.

The skills also carry the rules for anything that touches a person. Every step that contacts someone is gated on a consent basis, a suppression list and a volume limit, and purchased or scraped lists and consumer targeting are refused. An agent with Cargo’s skills drafts outreach for your sequencer or for a Cargo mailbox. It does not bulk-mail strangers because someone asked it to in a group chat.

Put it on a schedule #

OpenClaw’s built-in scheduler turns a request into a standing one. A list every Monday morning, delivered to a Slack channel:

shellscript
openclaw automations create "0 8 * * 1" \
  "Using the Cargo skills, find companies in our ICP that raised a round in the last 7 days, find the head of sales at each, and post the list with verified emails." \
  --name "Monday funded accounts" \
  --tz "Europe/Paris" \
  --session isolated \
  --announce --channel slack --to "channel:C1234567890"

This is the right shape for a job one person wants, delivered to them, where a missed week costs nothing.

When the job should leave the agent #

A personal agent runs on one person’s machine, with that person’s session, until the laptop closes. That is fine for the Monday list. It stops being fine when the job has to run whether or not that machine is on, when the team depends on its output, or when someone has to answer for what it did six weeks ago.

At that point the agent should stop running the job and start building it. The same CLI declares the work as a Cargo play, in TypeScript, in a repository: it runs on Cargo on its schedule or when data changes, retries on failure, and leaves a trace of every run.

shellscript
cargo-ai project init my-gtm --cookbook new-hire-detection
cd my-gtm
npm install               # the cookbook's dependencies
cargo-ai project plan     # the diff against the workspace
cargo-ai project deploy   # needs a login

Ask OpenClaw to do it, with the cargo-project skill loaded, and it will. That is the division of labour that holds up: the agent drafts and changes the system, Cargo holds the credentials, the data, the schedule and the audit log, and a person approves the diff. We wrote up the operating model in run GTM with coding agents.

Hermes Agent #

Hermes Agent, from Nous Research, follows the same AgentSkills standard, so the same packs work. The skills CLI installs them into Hermes’s skill directory:

shellscript
npm install -g @cargo-ai/cli
npx skills add getcargohq/cargo-skills --agent hermes-agent -g   # → ~/.hermes/skills

Sign in the same way, on the machine Hermes runs on. If you are moving from OpenClaw, hermes claw migrate imports the skills you already installed there.

Frequently asked questions #

Yes, with the right skills. On its own OpenClaw can browse and search, but it has no B2B contact data or email verification. Cargo’s skills give it sourcing, enrichment, verification and scoring against licensed data providers through the cargo-ai CLI, with a cost receipt for every run.

Install the CLI with npm install -g @cargo-ai/cli, then run openclaw skills install @cargo-ai/cargo-gtm for each skill you want, or npx skills add getcargohq/cargo-skills --agent openclaw -g for the whole platform pack. Install the CLI first: without it OpenClaw marks the skills as needing setup and hides them from the model.

The skill declares cargo-ai as a required binary and OpenClaw cannot find it on the path. Run npm install -g @cargo-ai/cli on the machine that runs the gateway, then openclaw skills info cargo-gtm should report Ready.

Yes. Hermes follows the same AgentSkills standard. npx skills add getcargohq/cargo-skills --agent hermes-agent -g installs the pack into ~/.hermes/skills, and the CLI and sign-in are the same as for OpenClaw.

The skills are free and open source. A new Cargo account starts with 100 free credits, valid for its first 30 days, and needs no card, which covers about 500 leads sourced, 1,000 verified-email enrichments or 50 fully enriched contacts. Paid plans are usage-based with no seats.

It can draft outreach and hand it to your sequencer or a Cargo mailbox, and every step that touches a person is gated on a consent basis, a suppression list and a volume limit. Bulk unsolicited messaging, purchased or scraped lists and consumer targeting are refused by the skills themselves.

Sources #

  • OpenClaw: repository, skills, ClawHub, and skills CLI.
  • Hermes Agent: repository and skills.
  • Cargo: cargo-gtm on ClawHub, cargo-skills, gtm-skills, agent install instructions, and cookbooks.
~/run-it-on-cargo/

Build this workflow instead of reading about it.

Cargo is the GTM infrastructure your coding agent builds on: enrichment, scoring, routing and outreach, defined in code and run in production.

Start building
AurelienAurelienOct 7, 2026
On this page
  • What the skills give your agent
  • Install in OpenClaw
  • Sign the agent in
  • What to ask it
  • Put it on a schedule
  • When the job should leave the agent
  • Hermes Agent
  • Frequently asked questions
  • Sources

Stay Informed with our
weekly Newsletter

Related articlesSee all articles
AI & Automation
Automating Sales Research with AI Agents

Build AI research agents that automatically gather company insights, competitive intelligence, and personalization hooks. Includes agent architectures, output templates, and implementation workflows for sales teams.

MaxMax·Nov 17, 2026
AI & Automation
How to Build Multi-Step Sales Automation Workflows with AI Agents

How to assess platforms for multi-step, multi-agent sales workflows: workflow flexibility, end-to-end orchestration, manual setup, agent design for qualification and research, and the difference between connecting to CRM data and promising outcomes.

AurelienAurelien·Nov 17, 2026
AI & Automation
Best Platforms to Build AI Agents for Sales in 2026

Compare eight platforms for building AI agents for lead qualification, account research, outreach and CRM updates in 2026: how you build an agent, what it can write to your CRM, how you review its work, and what it costs.

AurelienAurelien·Nov 16, 2026

Build the self-driving GTM engine

Your coding agents build it on Cargo.Or our team builds, operates and improves it with you.

Start building
Cargo
Backed byY CombinatorSOC 2 Type IICertified
LinkedinX

Product

Data ModelsContextTerritoriesMailboxesToolsAI AgentsPlaysAppsIntegrationsPricing

Add-ons

Chrome extensionButtonFormSlackGitHub

Build

DocsDeveloper resourcesCargo API docsCargo OpenAPI specCargo auth docsCargo webhooksCargo MCP serverProjectsClaude CodeCodexCursorAll coding agents

Resources

ReportsBlogCustomer storiesCookbooksEnrichmentRoutingSignalsScoringCRM hygieneAd audiencesGTM skillsGTM EngineeringGlossaryCompareCargo x ClayCargo x WorkatoCargo x n8nCargo x DeeplineCargo x DefaultCargo x LeanDataCargo x UnifyCargo x ValleyCargo x GojiberryCargo x PhantomBusterCargo x ZapierCargo x ApolloCargo x Chili PiperCargo x Common RoomCargo x MakeCargo x Tray.io

Company

ManifestoCommunityEventsJobsPartners DirectoryPartner Program

Legal

SecurityTerms of servicePrivacy PolicyRefundsDPASupport
© 2026 Cargo
 ////////    ///////    ////////     ////////    ///////
///         ///   ///   ///   ///   ///         ///   ///
///         ///   ///   ///   ///   ///         ///   ///
///         /////////   ////////    ///  ////   ///   ///
///         ///   ///   /// ///     ///   ///   ///   ///
///         ///   ///   ///  ///    ///   ///   ///   ///
 ////////   ///   ///   ///   ///    ///////     ///////

$ npm install -g @cargo-ai/cli