1---2name: hook-writer3description: >-4 Writes opening lines for a LinkedIn post from one idea or a draft. States what the post promises, ties every hook to5 one of the company's buying moments from company-profile.md, drafts 2 hooks per fitting family across 8 families6 (contrarian, curiosity gap, story, labeling, signaling, framework, authority, stakes), checks each for length, bait,7 double promises and a missing specific, cuts the generic ones with 3 copy tests, and ranks the best 3 with a fix to8 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't9 landing. Not for writing the whole post (use founder-post) or ad headlines (use ad-variants).10license: MIT11compatibility: >-12 Works in Claude, ChatGPT, Codex, Cursor and any agent that reads SKILL.md. Python 3 is optional, for the mechanical13 checks.14metadata:15 author: SHAKEUP16 version: "2.0.0"17 stage: make18 plugin: content19 homepage: https://www.shakeuphq.com/skills/hook-writer20---21 22# Hook writer23 24Writes 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.25 26## Purpose27 28- One job: hooks for one post, checked, with the best 3 ranked.29- Stage: make. It ends in its own check and a fix loop of at most 2 rounds.30- 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.31 32## Use when / not33 34| Situation | Use |35| --- | --- |36| A post is written and needs its opening line | this skill |37| An idea needs hook options before the post is written | this skill |38| A post's hook isn't getting read | this skill, on the post |39| The whole post needs writing | `founder-post` (it can call this skill for the hook) |40| A month of post ideas | `content-calendar` |41| Ad headlines within a platform's limits | `ad-variants` |42 43## Inputs44 45| Input | Required | Ways to provide, in order | If missing |46| --- | --- | --- | --- |47| 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 |48| 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` |49| 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 |50| The writer's voice | no | `### Founder voice` or `## Voice` in the profile; 2 or 3 past posts | plain and direct; coverage `partial` |51 52## Profile read53 54From `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`.55 56No 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.57 58## Steps59 601. **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.61 622. **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.63 643. **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.65 664. **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.67 685. **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.69 706. **Mechanical checks.** Run:71 72 ```73 python3 scripts/hook_check.py --hooks hooks.txt --specific "<the specific>" --profile company-profile.md74 ```75 76 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.77 787. **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).79 808. **Rank** the survivors: anchored to a high-priority moment, then most specific promise, then fewest words; the top 3 from 3 different families.81 829. **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.83 8410. **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.85 86## Check and verdict87 88| Verdict | Condition (first match wins) |89| --- | --- |90| `BLOCKED` | No idea or post, or the post's promise can't be stated in one sentence |91| `THIN` | Fewer than 3 hooks pass every check after the loop: say which input would fix it (a specific, a sharper promise, a moment) |92| `READY WITH BLANKS` | 3 or more pass, but at least 1 of the top 3 carries `[blank]` for a fact the writer must supply |93| `READY` | 3 or more pass with no blanks, at least 2 of the top 3 anchored to a buying moment |94 95Named stops: `BLOCKED` asks for what the post delivers. No other stops; `THIN` and `READY WITH BLANKS` hand over with what's missing.96 97## Loop98 991. Check: steps 6, 7 and 10.1002. 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.1013. Recheck the rewrites. At most 2 rounds; then hand over with the failed hooks shown and their rule.102 103## Learn104 105Append to `## Learnings` when:106 107- the reader picks a hook outside the top 3 (a `proposal` with their reason, such as "story hooks fit our founder better than frameworks");108- 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);109- the reader bans a phrase or a family (a `fact`; add phrases to `### Words to avoid`).110 111Example: `- 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`112 113## Output114 115```116Verdict: <READY | READY WITH BLANKS | THIN | BLOCKED> · Coverage: <complete | partial (no buying moments; no voice)> · Checks: <script | by reading>117The promise: <one sentence>118Moments: <moment, role, the buyer's words> (one line each)119 120| Family | Hook | Moment | Words | Check |121(every hook; Check is Pass or the rule it broke, including "generic: fails picture, proof")122 123Top 3:1241. "<hook>": <why it works, in one line> · Moment: <moment>1252. ...1263. ...127First sentence fix: <the rewritten first sentence, or "pays off as written">128Blanks to fill: <each [blank] and what goes there, or none>129Learnings applied: <list, or none>130```131 132Then the handoff block.133 134## Hand off135 136```handoff137skill: hook-writer138version: 2.0.0139verdict: READY140coverage: complete141for: <post or idea>142outputs:143 top_hook: <hook 1>144 alternatives: [<hook 2>, <hook 3>]145 moment: <the buying moment hook 1 is tied to>146 family: <family of hook 1>147 first_sentence: <the fixed first sentence, or unchanged>148next: [founder-post]149open: []150```151 152`founder-post` keeps `top_hook` unchanged as the post's opening line.153 154## Failure modes155 156| Problem | Do this |157| --- | --- |158| The post makes 2 points | Say so; write hooks for the stronger one and suggest the other as its own post |159| The only specific is a figure with no source | Keep it out of the hooks until `claim-check` passes it; use `[blank]` |160| 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 |161| The profile has no buying moments | Ask once for the reader's role and situation; mark every hook `unanchored`; suggest `buying-moments` |162| 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 |163 164## Influenced by165 166- 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-202167- 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.