skills/content-proof/SKILL.mdView on GitHub
This applies to everything the company publishes and every piece of proof it collects. It produces a calendar people can see, a cadence that holds, and a proof bank that is current.
Before you start
This skill works on its own. If the person has their own marketing brain (or any folder of context files about their company), read the files listed under reads in the header first and cite them for every fact. If they do not have one, do not look for one: ask for the two or three facts this play needs and go on. Never invent a fact; a blank is a question for the person.
Tools: this play speaks in verbs (check the CRM, pull the call, schedule the post). TOOLS.md at the root of this repo lists the tools recommended for each verb. The company’s own 1-context/stack.md wins when it exists. No tool is required; a spreadsheet and a mail client cover most of it.
The play
- Read the context (see Before you start). Open the calendar (
content-calendar); every piece lives there with a date, a channel, a pillar and an owner. - Fill the calendar from the three pillars: product (releases, tips, how-tos), point of view (the founder’s industry view), trust (customer stories and proof). Each week should carry all three.
- Run
founder-content-rhythmweekly: ideas from the founder’s own calls and inbox, the content meeting, review, schedule. - Run
social-postfor company page posts from the calendar;schedule-postpublishes them. Company page daily, founder on their cadence. - Run
blog-editon long-form before it ships;graphics-checkon every image. - Proof:
case-studywhen success tees up a candidate;customer-interviewfor the call;customer-video-cutfor the footage;proof-capturethe moment any quote, number or testimonial appears, so it enters the tracker with its permission status. - Run
product-tip-serieson the release cadence for existing customers. - Weekly: cadence held, pieces shipped by pillar, proof added, into
weekly-marketing-update.
KPIs
- Posting cadence held (company page and founder).
- Proof pieces completed per quarter (case studies, video testimonials).
- Recognition in outbound replies and at events (“I saw your post”).
What good looks like
- The best operator treats content as the gasoline for every other channel: outbound lands better when the name is known, events convert better when the booth story was seen before. The calendar is planned against the demand plays, not in a vacuum.
- The mediocre version produces content when someone has time, and the quote bank goes stale so every new piece reuses the same two customers.
- Good output is a calendar the executive team can open, a founder who posts from their own material, and a proof bank where every quote has a permission row.
Rules
- MUST route every customer mention through
permission-check. - MUST keep the three pillars in every week’s plan.
- NEVER mine call recordings for case studies in place of asking the customer; the human ask comes first, the recording helps draft.
- NEVER ship a graphic with a clipped screenshot or generated-looking art for print.