Skip to content

Makes

Founder post

Writes a LinkedIn post in your founder's own voice from a source passage, then reviews it against the voice rules, the buyer and the source before you post.

Other tools

Add this skill to Claude

Claude takes skills as a ZIP file. Your download has started; if it didn't, use the button below.

  1. 1In Claude, open Customize, then Skills.
  2. 2Choose +, then Upload a skill, and pick founder-post.zip.
  3. 3Ask for it by name, or let Claude use it when a task matches.

Skills need code execution turned on in Claude's settings. On a Team or Enterprise plan, an admin can share it with everyone.

Download the folder

Try it now, without installing

See the skill work on a made-up input before you add it. Nothing is installed, and you can swap in your own input.

Open in the Claude app

Opens a new chat in the Claude desktop app with the prompt filled in. Nothing is sent until you press enter.

Includes the whole SKILL.md and the sample input. Paste it into Claude, ChatGPT or any chat.

Influenced by
LinkedIn reach research, Founder Brand
Needs
The source passage
Works with
Claude, ChatGPT, Codex, Cursor and any agent that reads SKILL.md
Version
1.0.0 · Last checked · License MIT
Maintained by
Sabih AhmedContent
SkillContent

Founder post

Example output

Review of one post
CheckResultLine
BuyerPassRevOps stops trusting every number
SourcePassSetup takes 14 days
Personal storyRemovedNot on file

Writes a LinkedIn post in your founder's own voice from a source passage, then reviews it against the voice rules, the buyer and the source before you post.

The skill

The whole skill, in plain text.

Nothing is hidden. Read it, change it to fit your team, or take the whole folder.

Scripts
Optional Python scripts for the counting. It works without them and says which way it ran.
Network
Doesn't need the internet.

3 test cases

founder-post/SKILL.md

In the folder

  • founder-post/SKILL.md
  • founder-post/references/archetypes.md
  • founder-post/references/founder-voice-template.md
  • founder-post/references/review-checks.md
  • founder-post/scripts/post_lint.py
---name: founder-postdescription: >-  Writes a LinkedIn post in the founder's own voice from a source passage (a playbook section, an article, call notes  or a calendar topic) and reviews it before handing it over. Finds the one idea in the source worth a post, frames it  for a buyer and a buying moment from company-profile.md, picks the post shape that fits, writes from a locked hook,  then checks mechanics, AI-sounding patterns and grounding (a line for the buyer's pain, a detail from the source, a  fit with the messaging) plus voice-check and claim-check, fixing in at most 2 rounds. Reads an optional Founder voice  subsection in the profile and asks for it once if missing. Use it to draft a founder post. Not for company page posts  in the brand voice (use repurpose) or for picking a month of topics (use content-calendar).license: MITcompatibility: >-  Works in Claude, ChatGPT, Codex, Cursor and any agent that reads SKILL.md. Python 3 is optional, for the mechanical  review.metadata:  author: SHAKEUP  version: "1.0.0"  stage: make  plugin: content  homepage: https://www.shakeuphq.com/skills/founder-post--- # Founder post Turns one passage into one post that sounds like the founder, carries one real detail, and speaks to one buyer's moment. ## Purpose - One job: one post (and its first comment) from one source passage, reviewed.- Stage: make. It ends in its own review and a fix loop of at most 2 rounds.- It never invents a story, a figure, a customer result or a personal detail. Anything personal comes from `### Founder voice` or the founder's own words; anything factual from the source or `## Claims and proof`. ## Use when / not | Situation | Use || --- | --- || A passage, article section or set of call notes should become a founder post | this skill || A topic row from `content-calendar` needs its post written | this skill (it keeps the row's hook) || Only the opening line needs work | `hook-writer` || A month of topics from a chapter or theme | `content-calendar` || Posts, an email and scripts from a finished article, in the company voice | `repurpose` || Putting paid reach behind posts that already did well | `founder-to-ads` | ## Inputs | Input | Required | Ways to provide, in order | If missing || --- | --- | --- | --- || The source passage | yes | a file or URL the agent can read; pasted text; a calendar row's `pulled_from` reference, re-read from the source | ask once; `BLOCKED` without it || The founder's voice | no | `### Founder voice` under `## Voice` in the profile; 2 or 3 past posts | ask once (`references/founder-voice-template.md`); continue with `## Voice`, coverage `partial` || A locked hook | no | a `hook-writer` or `content-calendar` handoff | write one in step 5 || The buyer and moment | no | the calendar row; `### Buying group` and `## Buying moments` | infer from the source and say so | ## Profile read From `company-profile.md`: `## Company`, `## Buyers` and `### Buying group`, `## Buying moments`, `## Positioning`, `## Messaging house`, `## Voice` with `### Founder voice`, `### Words to avoid` and `### Lines that sound right`, `## Claims and proof` with `### Never say`, `## Competitors` (mention policy), and every `## Learnings` entry for `founder-post`, `hook-writer`, `voice-check` and `claim-check`. No profile: ask in one message for the founder's name and role, 2 or 3 past posts, who the buyer is, and the source of any figure the post should use. Say that `company-profile` saves this next time. ## Steps 1. **Apply learnings.** Founder edits recorded as accepted rules ("never opens with a question", "shorter than 1,200 characters") override the defaults. 2. **Read the founder's voice.** From `### Founder voice`, note the main topics, the details they share, the scale they can claim, spelling, colons, post length and `Never says`. If it's missing, ask once using `references/founder-voice-template.md`, and continue. 3. **Find the one idea.** Read the whole source once, then hunt for the idea that passes all of these: specific enough to stand alone; actually in the source; states what it costs or changes for the buyer, not just a mechanism; could only be said by someone who has done the work. If several pass, take the one with the sharpest consequence and list the rest for `content-calendar`. If none pass, `BLOCKED`: say what the source lacks. 4. **Frame it.** Pick the buyer role from `### Buying group` and the moment from `## Buying moments` it speaks to; the pillar from `## Messaging house` it supports, or `tactical` if none; and the archetype from `references/archetypes.md` whose "source must contain" column the source satisfies. No archetype fits: say so rather than force one. 5. **Set the hook.** A locked hook from `hook-writer` or the calendar stays word for word. Otherwise write one: a claim, a figure or a scene from the source in the first line, 18 words or fewer, no bait, no rhetorical question. For more options, run `hook-writer`. 6. **Write.** Follow the archetype's shape and close. Rules:   - The founder's point of view and spelling; every sentence complete; vary sentence length hard.   - One real reaction somewhere ("That surprised us.").   - Give the reader something to use: a rule, a threshold, a question to ask, written as what the founder learned or changed, not as a stack of commands.   - For a build-out, argue with yourself before the close: state the strongest objection, concede what's fair, land the point.   - Personal details only from `### Founder voice` or the source. A background fact ("ran demand generation at 2 companies") is not a story: never write an event set in that job unless the founder or the source tells it. A first-person claim the source makes but the founder didn't ("I built") is dropped to a plain statement of the finding, and the removal is noted.   - Reactions without invented history: "That trade still surprises people" is fine; "the first time I saw it" needs a real first time.   - Never point back at the source ("in this playbook"). The claim stands on its own.   - Claims about how a platform or AI tool behaves today are checked as current, not trusted from the source's date.   - Length from the archetype's band or the founder's own range. Link, if any, goes in the first comment. 7. **Review.** Run:    ```   python3 scripts/post_lint.py --post post.txt --profile company-profile.md [--no-colons] --min-chars <n> --max-chars <n>   ```    Without Python, check by reading every mechanics row in `references/review-checks.md`. Say which way you ran it. Then run the AI pattern tests and the grounding checks in the same file; for each grounding check, quote the line that passes it, or fail it. 8. **Voice and claims.** Run `voice-check` with the founder's voice, then `claim-check`. Without them installed: the profile's words to avoid, point of view and the 3 copy tests; every figure and comparison against the source or `## Claims and proof`, and every `### Never say` line. 9. **Fix and recheck** (Loop), then hand over the post, the first comment and the review table. ## Check and verdict | Verdict | Condition (first match wins) || --- | --- || `BLOCKED` | No source; nothing in the source passes step 3; or the post would need an invented story, figure, customer result or personal detail, or a `### Never say` claim, to exist || `READY WITH OPEN ITEMS` | The post passes every critical check, but something is open: a `[blank]` for a detail only the founder can give, a figure waiting for its source, a warning left after 2 rounds, or no founder voice on file || `READY` | 0 critical, no warnings left with a clear fix, every grounding check passed with a quoted line, voice-check and claim-check PASS or PASS WITH NOTES | Named stops: `BLOCKED` asks for the missing input and says what would unblock it. No other stops. ## Loop 1. Collect every critical and warning from steps 7 and 8, each with its line.2. Fix only what failed. Fixing a word to avoid keeps the specific noun next to it. Never fix a grounding failure by adding a claim that isn't in the source, and never pad a post to reach a length band: if the source supports only a short post, switch to a short archetype or leave the length warning open.3. Reread each flagged line in the final text (not from memory), then rerun step 7 and step 8.4. At most 2 rounds. Then hand over with anything still open, labelled. If the voice questions in `references/review-checks.md` fail 3 or more, the one rewrite from the hook down counts as a round. ## Learn Append to `## Learnings` when: - the founder edits the post before posting (a `proposal` for each repeated edit, such as "cuts every closing question", and add confirmed phrases to `Never says`);- the post's results come back: impressions, comments of 10 or more words, profile views, conversations started, against the founder's median (a `fact` naming the archetype, the moment and the source);- the founder confirms a personal detail for future posts (a `fact`, and add it to `### Founder voice`). Example: `- 2026-10-24 | founder-post | fact | Teardown posts on the budget-cut moment drew 2x the founder's median comments | Why: post analytics, 6 posts, Aug to Oct 2026 | Status: noted` ## Output ```Verdict: <READY | READY WITH OPEN ITEMS | BLOCKED> · Coverage: <complete | partial (no founder voice; no buying moments)> · Rounds: <0 | 1 | 2>Idea: <one sentence> · Archetype: <name> · Buyer: <role> · Moment: <moment> · Pillar: <pillar | tactical> <the post, as it will be posted> First comment: <link and one line, or none>Format: <text | text and image | document> · Characters: <n> | Check | Result | Line |(mechanics by <script | reading>, AI pattern tests, grounding with the quoted line, voice-check, claim-check) Removed from the source: <first-person claims or details dropped, or none>Other ideas in the source: <for content-calendar, or none>Open: <each open item>Learnings applied: <list, or none>``` Then the handoff block. ## Hand off ```handoffskill: founder-postversion: 1.0.0verdict: READYcoverage: completefor: <post idea>outputs:  hook: <the opening line>  archetype: teardown  buyer: <role>  moment: <buying moment>  pillar: <pillar or tactical>  characters: 1540  claims_checked: truenext: [founder-to-ads]open: []``` `founder-to-ads` reads `pillar` and `claims_checked` when the post's results come in; `content-calendar` reads the other ideas listed. ## Failure modes | Problem | Do this || --- | --- || The source is the founder's own notes in "I" | Keep the first person only where the founder confirms it happened; otherwise state the finding || The founder asks for a story that isn't in the source or the profile | Ask for the real story in 3 questions (what happened, when, what changed); never write a plausible one || The source's figure is a few years old | Run `claim-check`; date it in the post ("in 2023, ...") or drop it || The post names a competitor | Follow `## Competitors` mention policy; with `never`, rewrite around the category || The founder's voice and the company voice disagree | The founder's voice wins on the founder's post, except `### Never say` and claims rules, which always apply || The idea is off the founder's main topics | Write it if asked, and flag it in the review: posts outside the main topics show the founder to the wrong readers | ## Influenced by - Richard van der Blom's research on how LinkedIn now ranks posts by topic and interest rather than by connections, and why a founder should keep most posts within 2 main topics: https://creatorscience.com/podcast/richard-van-der-blom-2/- Dave Gerhardt's case for the founder's own story and point of view as the brand's edge, in Founder Brand: https://scribemedia.com/published-books/founder-brand- SHAKEUP's social pipeline: one idea per post from the source, a locked hook, archetype shapes, the AI pattern tests, and a review that quotes the line proving each grounding check.

How it thinks

Inputs in, a verdict out, and a stop only where you decide.

What we built

Our social pipeline writes one idea per post from a real source and keeps the hook locked. A review quotes the line that proves each grounding check. We added a hard rule on stories, because the founder's background isn't a licence to write one.

It reads your company profile if you have one, or asks for only what it needs. Then it works through its steps, checks its own work and ends in a verdict.

The steps

  1. 01

    Read the founder's voice

    Main topics, the details they're happy to share, the scale they can claim, spelling and the phrases they never use.

  2. 02

    Find the one idea

    It has to be in the source, state what it costs or changes for the buyer, and be something only a person who has done the work could say. If nothing passes, it stops.

  3. 03

    Frame it

    The buyer role and moment it speaks to, the message pillar it supports, and the post shape the source can carry, such as a teardown or a myth versus reality.

  4. 04

    Write from the hook

    Complete sentences, one real reaction, and something the reader can use, framed as what the founder learned. A build-out argues with itself before it lands the point.

  5. 05

    Review before you see it

    A script checks dashes, banned words, length, links and command stacks. Then it tests for patterns that read as machine-written, and quotes the line that grounds each claim.

  6. 06

    Fix twice at most

    Only what failed gets changed. A story or a figure the source doesn't hold is never added to fix a check, and a post is never padded to reach a length.

What you need

  • Required

    The source passage

    A file or URL your agent can read → Text you paste, such as a playbook section, an article or call notes → A row from the content calendar, re-read from its source

  • Optional

    The founder's voice

    A Founder voice subsection in your company profile → 2 or 3 of the founder's past posts

  • Optional

    A locked hook

    A hook writer or content calendar handoff

  • Optional

    The buyer and their moment

    The calendar row → The buying group and buying moments in your profile

What it can return

  • READY

    Every check passes, each grounding check has a quoted line, and the voice and claim checks pass.

  • READY WITH OPEN ITEMS

    The post passes, but something is open, such as a detail only the founder can give or no founder voice on file.

  • BLOCKED

    There's no source, nothing in it is worth a post, or the post would need an invented story or a claim you never make.

Where it stops for you

  • When the post would need a story, figure or customer result that isn't on file

Example output

What you get back.

A run for a made-up company. Your output depends on your inputs.

Here's a run for a made-up B2B SaaS company that sells attribution software. The source is a playbook passage on why RevOps stops trusting attribution.

Verdict

READY

Coverage: complete

Rounds: 1

Idea

a rewritten lifecycle stage makes RevOps doubt every report built on it. Shape: teardown, short. Buyer: the RevOps manager. Moment: the board asks for pipeline by channel.

The fastest way to lose your RevOps lead is to let an attribution tool rewrite one lifecycle stage.

When that happens, RevOps stops trusting every number downstream.

The fix is boring. Read the stages your CRM already has, never write to them, and agree the mapping with RevOps before launch.

At our company, stage mapping happens on day 1 of every onboarding, and the average setup takes 14 days. I'd take that trade every time.

When did your RevOps team last question a number in your pipeline report?

CheckResultLine
MechanicsPassNo dashes, no colons, 851 characters
BuyerPass"RevOps stops trusting every number downstream"
SourcePass"the average setup takes 14 days"
Personal claimsFixed in round 1A story set in the founder's old job wasn't on file, so it was removed
The handoff block the next skill reads
skill: founder-post
version: 1.0.0
verdict: READY
coverage: complete
for: rewritten stages post
outputs:
  archetype: teardown
  buyer: RevOps manager
  pillar: Trusted figures
  claims_checked: true
next: [founder-to-ads]
open: []

What good looks like

  • One idea, from the source, in the founder's voice
  • A line that speaks to the buyer's pain or moment, quoted in the review
  • Every figure from the source or your approved claims
  • No pointer back to the playbook or the article
  • The link in the first comment, not the post

Install

Use it in the tool you already have.

Pick your tool. Each tab has the shortest path we know of.

  1. 01
  2. 02
    In Claude, open Customize, then Skills.
  3. 03
    Choose +, then Upload a skill, and pick the ZIP. Code execution must be on in your settings.
  4. 04
    Ask for it by name, or let Claude use it when a task matches.

Questions

Before you add it.

What if we don't have a founder voice written down?

It asks once for the founder's name and role, 2 or 3 past posts, their main topics and what they're happy to share. Then it drafts in your company voice and says so.

Can it add a personal story?

Only one the founder or the source tells. A background fact, such as a past job, doesn't license an invented event set in that job.

Why does it check the founder's main topics?

Current research on the platform finds posts are matched to readers by topic. Posts outside the founder's main topics show them to the wrong people.