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
Cookbooks
LCOperations

LinkedIn content

Draft LinkedIn posts every week from your own proof points: each Monday three post drafts for one author land in your go-to-market repo as one pull request, built only from what context/ and the cadence log already say, each with its hook and the files it draws on; nothing is ever published.

Installation
Set up the linkedin-content cookbook in this project. 1. If the Cargo CLI is not installed yet, follow every step in https://api.getcargo.io/INSTALL.md 2. From the Cargo project, run: cargo-ai project add cookbook/linkedin-content 3. Then follow .claude/skills/linkedin-content/SKILL.md. Stop for my approval before any paid call, and stop at "cargo-ai project plan" before deploying anything.
Paste it into Claude Code, Cursor, Codex, Gemini CLI, Devin or Replicas.
$cargo-ai project add cookbook/linkedin-content
Run it in your Cargo project. Copies the example in, and deploys nothing.

Say this to your agent

Every Monday, draft three LinkedIn posts for our CEO, Dana Ruiz, from what's in context/.

Illustrative output #

Fictional records, to show the shape of what comes back.

text

## What you will be asked

| Input | | Why |
| --- | --- | --- |
| `CONTENT_AUTHOR` (`infra/agents/content-writer.ts`) | Asked | Every draft is in the first person. A team name produces posts nobody can publish as themselves. |

## Done when

- `node --import tsx evals/contract.mjs` passes
- `cargo-ai project plan` reports the agent, the two connectors and the folder
- the first run opened one pull request, `[linkedin-content] <week>`, containing only `cadence/content/<week>.md` in the `references/post.md` shape
- every draft lists its sources, and every number, customer and quote in it appears in one of them
- no customer whose `client/` file lacks reference permission is named
- a second run the same week linked the open pull request, opened no second one and changed nothing
- nothing was posted to LinkedIn or anywhere else

## What it costs

No connector action runs: the agent reads files in its checkout and opens a pull request through
the Cargo GitHub app. The recurring cost is the harness run itself, once a week, billed as LLM tokens through the
Anthropic connector, and it scales with how much of `context/` and `cadence/` there is to read.

The `performance-report` variation adds one paid LinkedIn action per run. Before adding it, read its
live price: `cargo-ai orchestration action list extractProfilePostActivity --kind connector
--integration-slug linkedin`, and say it out loud.

To keep a LinkedIn author posting from real material, draft from what your go-to-market repository already says and let a person publish. Every Monday this cookbook’s Claude Code harness agent writes three drafts for one author from context/ and the cadence log, cites the files behind each, and opens one pull request; it never publishes anything.

shellscript
cargo-ai project add cookbook/linkedin-content

What it does #

  • Reads positioning, proof points, clients, insights, objections and alternatives under context/, plus the last two weeks of cadence/log/ and the last eight weeks of drafts.
  • Drafts three posts, one per kind: a proof point, an answer to an objection, and this week’s lesson.
  • Cites the files behind every draft, cuts any claim it cannot cite, and never names a customer without reference permission.
  • Writes cadence/content/<week>.md and opens one pull request. A re-run that week finds that pull request by its title and stops; close it to ask for a redraft.

What’s inside #

Adds 4 resources.

FileResourceRole
infra/agents/content-writer.tsdefineAgent (claudeCode)the weekly cron, the author env var, the model
infra/agents/content-writer.prompt.ts(not a resource)what it reads, the three kinds, the citation rule, the PR
infra/connectors/anthropic.tsdefineConnector (anthropic)the model the harness runs on
infra/folders/index.tsdefineFolderwhere the agent is filed
references/post.md(not a resource)the drafts file shape and the rules for a draft

Why a pull request and not a post #

Publishing as a person is that person’s act. A draft that overstates a result costs a correction in the comments, under their name. The pull request is where someone reads it first, and the agent has no LinkedIn action that could skip that step.

Why no context capability #

The checkout already holds context/, so the agent reads it as files. A capability would add a second path that can write the knowledge layer without the review every other pipeline goes through.

Placeholders (edit before deploy) #

  1. CONTENT_AUTHOR in infra/agents/content-writer.ts: the person the posts are written as.
  2. languageModel: any Anthropic model the workspace’s connector can reach.
  3. The cron: Monday 14:00 UTC, after web-capture’s Monday run.

What it does not do #

It does not post, like, comment, connect or message on LinkedIn, write under context/, read the web or the CRM, or merge its own pull request.

Version0.2.0
LicenseMIT
Source
Deploys
  • agents
  • connectors
For
  • Marketing
  • Sales leadership
Integrations
  • Anthropic
Content
  • Say this to your agent
  • Illustrative output
  • What it does
  • What's inside
  • Why a pull request and not a post
  • Why no context capability
  • Placeholders (edit before deploy)
  • What it does not do
More in Operations
  • Standup
  • Meeting prep
  • Next step tracker
  • Stalled deal nudge
  • Weekly planning
  • Goal coverage
  • Workspace health
  • Ask Cargo
Next: CRM
  • CRM enrichment
  • CRM deduplication
  • Expansion signals

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