LinkedIn content

State: to-be-approved. Deploy-verified against a live workspace: not yet. Treat Done when below as the acceptance test and review cargo-ai cdk plan before deploying. Make no outcome claim for this skill until it is approved.

The outcome

The proof points, customer stories and lessons the team already wrote down stop sitting in a repo nobody outside GTM reads. Every Monday one agent reads context/ (positioning, proof, clients, insights, objections, alternatives) and the last two weeks of cadence/log/, and drafts three LinkedIn posts for one named author:

1. One on a proof point: a result a customer got, from a proof/ file.
2. One that answers an objection or a misconception buyers bring, without naming a competitor.
3. One from this week: something the team learned, from a dated insight or log entry.