Skip to content

Makes

Hook writer

Writes opening lines for a LinkedIn post from one idea, ties each to a moment your buyer lives through, cuts the generic ones and ranks the best 3.

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 hook-writer.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
The 3 copy tests
Needs
The post, or the idea and what it will deliver
Works with
Claude, ChatGPT, Codex, Cursor and any agent that reads SKILL.md
Version
2.0.0 · Last checked · License MIT
Maintained by
Sabih AhmedContent
SkillContent

Hook writer

Example output

Hooks for one post
FamilyMomentCheck
FrameworkBoard asks for pipelinePass
ContrarianBoard asks for pipelinePass
SignalingNoneGeneric, cut

Writes opening lines for a LinkedIn post from one idea, ties each to a moment your buyer lives through, cuts the generic ones and ranks the best 3.

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

hook-writer/SKILL.md

In the folder

  • hook-writer/SKILL.md
  • hook-writer/references/families.md
  • hook-writer/scripts/hook_check.py
---name: hook-writerdescription: >-  Writes opening lines for a LinkedIn post from one idea or a draft. States what the post promises, ties every hook to  one of the company's buying moments from company-profile.md, drafts 2 hooks per fitting family across 8 families  (contrarian, curiosity gap, story, labeling, signaling, framework, authority, stakes), checks each for length, bait,  double promises and a missing specific, cuts the generic ones with 3 copy tests, and ranks the best 3 with a fix to  the post's first sentence when it doesn't pay the hook off. Use it when a post needs its first line or a hook isn't  landing. Not for writing the whole post (use founder-post) or ad headlines (use ad-variants).license: MITcompatibility: >-  Works in Claude, ChatGPT, Codex, Cursor and any agent that reads SKILL.md. Python 3 is optional, for the mechanical  checks.metadata:  author: SHAKEUP  version: "2.0.0"  stage: make  plugin: content  homepage: https://www.shakeuphq.com/skills/hook-writer--- # Hook writer Writes the first line of a post so the right buyer, at the right moment, wants the rest, and cuts every line a competitor could have written. ## Purpose - One job: hooks for one post, checked, with the best 3 ranked.- Stage: make. It ends in its own check and a fix loop of at most 2 rounds.- It never invents a figure, a client, a result or an experience. A hook that needs a fact the writer didn't give carries `[blank]` and says what goes there. ## Use when / not | Situation | Use || --- | --- || A post is written and needs its opening line | this skill || An idea needs hook options before the post is written | this skill || A post's hook isn't getting read | this skill, on the post || The whole post needs writing | `founder-post` (it can call this skill for the hook) || A month of post ideas | `content-calendar` || Ad headlines within a platform's limits | `ad-variants` | ## Inputs | Input | Required | Ways to provide, in order | If missing || --- | --- | --- | --- || The post, or the idea and what the post will deliver | yes | the reader's request; a `founder-post` or `content-calendar` handoff | ask once; `BLOCKED` if it delivers nothing clear || Who it's for and their moment | no | `## Buying moments` and `### Buying group` in the profile; the reader's note | ask once for the role and the situation; without them, hooks are `unanchored` || One specific: a figure, a named tool, a result, something that happened | no | the post; `## Claims and proof`; the reader | hooks carry `[blank]` where the specific goes || The writer's voice | no | `### Founder voice` or `## Voice` in the profile; 2 or 3 past posts | plain and direct; coverage `partial` | ## Profile read From `company-profile.md`: `## Buyers` and `### Buying group`, `## Buying moments`, `## Voice` (with `### Founder voice` if present, and `### Words to avoid`), `## Claims and proof` (with `### Never say`), and every `## Learnings` entry for `hook-writer`. No profile: ask in one message for who the post is for, the situation they're in when it matters, and one specific fact the post rests on. Say that `company-profile` saves this next time. ## Steps 1. **Apply learnings.** A family the reader keeps choosing, or one whose hooks performed, moves up the ranking; a learning that bans a family removes it. 2. **Find the promise.** Write, in one sentence, what the post delivers to the reader. Every hook promises that and nothing more. If you can't write the sentence, stop with `BLOCKED` and say what the post needs to deliver; no hook fixes an unclear post. 3. **Pick the moments.** From `## Buying moments`, pick the 1 to 3 the promise speaks to, high priority first (`references/families.md`, tying a hook to a buying moment). Note the trigger, the buyer's own words and the role for each. 4. **Pick the families.** Choose the 3 to 5 of the 8 in `references/families.md` that fit the post. Skip any whose "skip when" applies: no framework hook without a full method, no authority hook without experience on file, no story hook without something that happened. 5. **Write 2 hooks per family.** Each one names something from one picked moment, carries the specific (or `[blank]`), and fits the writer's voice: no emojis, hashtags or line-break tricks unless the voice or past posts use them. 6. **Mechanical checks.** Run:    ```   python3 scripts/hook_check.py --hooks hooks.txt --specific "<the specific>" --profile company-profile.md   ```    Without Python, check each hook by reading: over 18 words (about 2 lines on a phone, which is what shows before the post is cut); bait phrases from `references/families.md`; a rhetorical question or "Imagine" opener; 2 promises in one line ("why X and how Y", "plus"); no figure, name or specific; a dash; a word to avoid; capitals or "!!"; emojis or hashtags. Say which way you ran it. 7. **Cut the generic ones.** Apply the 3 copy tests (`references/families.md`) to each hook that passed step 6. Failing 2 or more: cut. Then the payoff test: does the post deliver everything the hook promises? If not: cut, or fix the post (step 9). 8. **Rank** the survivors: anchored to a high-priority moment, then most specific promise, then fewest words; the top 3 from 3 different families. 9. **Pay it off.** Read the post's first sentence after each top hook. If it doesn't pay the hook off straight away, rewrite that sentence so it does. 10. **Check the top 3** with `voice-check` and `claim-check`, or inline: the profile's words to avoid and point of view, and every figure against `## Claims and proof` or the post's own source. A hook with a figure that fails is cut, not softened. ## Check and verdict | Verdict | Condition (first match wins) || --- | --- || `BLOCKED` | No idea or post, or the post's promise can't be stated in one sentence || `THIN` | Fewer than 3 hooks pass every check after the loop: say which input would fix it (a specific, a sharper promise, a moment) || `READY WITH BLANKS` | 3 or more pass, but at least 1 of the top 3 carries `[blank]` for a fact the writer must supply || `READY` | 3 or more pass with no blanks, at least 2 of the top 3 anchored to a buying moment | Named stops: `BLOCKED` asks for what the post delivers. No other stops; `THIN` and `READY WITH BLANKS` hand over with what's missing. ## Loop 1. Check: steps 6, 7 and 10.2. Fix: rewrite a failed hook once, changing only what failed (shorten it, swap the bait for the specific, split a double promise into 2 hooks). If fewer than 3 pass, write 2 more from a family not yet used.3. Recheck the rewrites. At most 2 rounds; then hand over with the failed hooks shown and their rule. ## Learn Append to `## Learnings` when: - the reader picks a hook outside the top 3 (a `proposal` with their reason, such as "story hooks fit our founder better than frameworks");- a post's results come back, such as impressions, comments or profile visits against the writer's usual (a `fact` naming the family and the moment, with the source);- the reader bans a phrase or a family (a `fact`; add phrases to `### Words to avoid`). Example: `- 2026-10-24 | hook-writer | fact | Labeling hooks naming the board-meeting moment beat the founder's median impressions 3 times out of 4 | Why: post analytics, Sept to Oct 2026 | Status: noted` ## Output ```Verdict: <READY | READY WITH BLANKS | THIN | BLOCKED> · Coverage: <complete | partial (no buying moments; no voice)> · Checks: <script | by reading>The promise: <one sentence>Moments: <moment, role, the buyer's words> (one line each) | Family | Hook | Moment | Words | Check |(every hook; Check is Pass or the rule it broke, including "generic: fails picture, proof") Top 3:1. "<hook>": <why it works, in one line> · Moment: <moment>2. ...3. ...First sentence fix: <the rewritten first sentence, or "pays off as written">Blanks to fill: <each [blank] and what goes there, or none>Learnings applied: <list, or none>``` Then the handoff block. ## Hand off ```handoffskill: hook-writerversion: 2.0.0verdict: READYcoverage: completefor: <post or idea>outputs:  top_hook: <hook 1>  alternatives: [<hook 2>, <hook 3>]  moment: <the buying moment hook 1 is tied to>  family: <family of hook 1>  first_sentence: <the fixed first sentence, or unchanged>next: [founder-post]open: []``` `founder-post` keeps `top_hook` unchanged as the post's opening line. ## Failure modes | Problem | Do this || --- | --- || The post makes 2 points | Say so; write hooks for the stronger one and suggest the other as its own post || The only specific is a figure with no source | Keep it out of the hooks until `claim-check` passes it; use `[blank]` || The writer asks for a "comment for the template" hook | Write it only if the template exists and the post says so; otherwise refuse that hook and say why || The profile has no buying moments | Ask once for the reader's role and situation; mark every hook `unanchored`; suggest `buying-moments` || Every family fails "could no one else say it" | The post itself is generic: say so and point to the specific that would change it | ## Influenced by - Harry Dry's 3 copy tests (can I picture it, can it be proved wrong, could no one else say it): https://www.demandcurve.com/newsletters/growth-newsletter-202- SHAKEUP's founder content practice: hooks tied to the buyer's moment rather than to curiosity alone, no bait, and a first sentence that pays the promise off.

How it thinks

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

What we built

We tie every hook to a moment your buyer is living through, not to curiosity alone. Bait never makes the list, and the first sentence of the post has to pay the promise off.

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

    Find the promise

    It writes, in one sentence, what the post delivers. Every hook promises that and nothing more. No hook can rescue a post with no clear promise.

  2. 02

    Pick the buyer's moment

    From your buying moments, it picks the 1 to 3 the post speaks to, with the trigger, the buyer's own words and the role who lives it.

  3. 03

    Write across 8 families

    Contrarian, curiosity gap, story, labeling, signaling, framework, authority and stakes. It picks the 3 to 5 that fit and writes 2 hooks each.

  4. 04

    Run the checks

    Its script flags hooks over 18 words, bait phrases, rhetorical questions, 2 promises in one line and hooks with no specific.

  5. 05

    Cut the generic ones

    The 3 copy tests ask whether you can picture it, whether it can be proved wrong and whether no one else could say it. A hook that fails 2 of the 3 is cut.

  6. 06

    Rank the best 3

    Tied to a high-priority moment first, then the most specific promise, then the fewest words, each from a different family. If the post's first sentence doesn't pay the hook off, it rewrites that sentence.

What you need

  • Required

    The post, or the idea and what it will deliver

    Your request → A founder post or content calendar handoff

  • Optional

    Who it's for and their moment

    The buying moments and buying group in your company profile → A note from you

  • Optional

    One specific fact

    The post itself → The Claims and proof section of your company profile → Your answer

  • Optional

    The writer's voice

    The Voice section of your company profile, with the founder's own subsection if you have one → 2 or 3 past posts

What it can return

  • READY

    At least 3 hooks pass every check with no blanks, and most of the top 3 are tied to a buying moment.

  • READY WITH BLANKS

    At least 3 pass, but one needs a fact only you can fill in.

  • THIN

    Fewer than 3 pass after 2 rounds. It names the fact, promise or moment that would fix it.

  • BLOCKED

    There's no post or idea, or the post's promise can't be stated in one sentence.

Where it stops for you

  • When the post doesn't deliver anything it can state in one sentence

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 post is about the 3 CRM fields a board's pipeline question depends on.

Verdict

READY

Coverage: complete

The promise

the post shows which 3 CRM fields decide whether a board believes the pipeline report.

FamilyHookMomentWordsCheck
Framework3 CRM fields to check before your board asks which channels created pipeline.Board asks for pipeline13Pass
ContrarianYour attribution model isn't the problem in the board meeting. 3 CRM fields are.Board asks for pipeline14Pass
StakesA blank source field won't show up in your dashboard. It shows up in the board meeting.Board asks for pipeline17Pass
LabelingIf your board asks for pipeline by channel next quarter, check 3 CRM fields first.Board asks for pipeline15Pass
SignalingAnyone who has defended pipeline figures to a board will recognize this.None12Generic: fails 2 copy tests

Top 3:

  1. "3 CRM fields to check before your board asks which channels created pipeline." It names the moment and the exact payoff.
  2. "Your attribution model isn't the problem in the board meeting. 3 CRM fields are." It pushes back on the usual fix.
  3. "A blank source field won't show up in your dashboard. It shows up in the board meeting." This one names a cost the reader hasn't seen yet.
First sentence fix

the post's opening pays off hook 1 as written.

The handoff block the next skill reads
skill: hook-writer
version: 2.0.0
verdict: READY
coverage: complete
for: the 3 CRM fields post
outputs:
  top_hook: 3 CRM fields to check before your board asks which channels created pipeline.
  moment: Board asks for pipeline by channel
  family: framework
next: [founder-post]
open: []

What good looks like

  • Every hook promises something the post delivers
  • Each of the top 3 names a moment, a role or a trigger your buyer would recognize
  • Facts you didn't give stay as blanks
  • Cut hooks are shown with the test they failed
  • A fix to the post's first sentence when it doesn't pay the hook off

Install

Use it in the tool you already have.

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

  1. 01
    Download hook-writer.zip.
  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.

Why tie a hook to a buying moment?

A hook that names the situation your buyer is in right now gets read by the right people. One with no moment, however clever, gets read by anyone, which doesn't help you sell.

Will it make up a number to sharpen a hook?

No. If a hook needs a fact you didn't give, it leaves a blank and tells you what goes there.

What counts as bait?

Phrases that promise a reaction instead of content, a resource behind a comment, a cliffhanger the post doesn't resolve, and questions the reader can't answer from their own work.