Use this when writing a storytelling hook for a post. You get a hook in your own words, with every blank filled by a real fact. Do not copy another writer's hooks.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Storytelling Hooks?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/botkitsdev-storytelling-hooks)
---
name: storytelling-hooks
description: >-
Use this when writing a storytelling hook for a post. You get a hook in
your own words, with every blank filled by a real fact. Do not copy
another writer's hooks.
license: MIT
---
# Storytelling hooks
Write a hook from a fact you already have. Do not paste another writer's lines.
If you keep a private log of hooks that won or lost on an account, write three options here first, then check that log. This skill does not score past posts.
## Facts first
- Every blank is a fact you can name: a date, a cost, a quoted question, a rule you actually follow.
- If you do not have the fact, pick another family. Do not invent a number, a client, or a year.
- The rest of the post must pay off the hook. If the hook promises one rule, the post has one rule. If it names a cost, the post gives that cost.
## Families
Full templates live in [references/patterns.md](references/patterns.md). Use the short table here to pick a family.
| Family | Use when | Why it works | One template |
| --- | --- | --- | --- |
| Transformation | You can name your own before and after | A gap between two states makes the reader want the path | `[Old state] in [month]. [New state] now. The change was smaller than you think.` |
| Mistake | You can name a failure and what it cost | A concrete cost makes the lesson specific | `This cost me [real cost]. Here is the step I skipped.` |
| Turning point | One event changed how you work | One cause is easy to remember | `I was about to drop [goal]. Then [one event].` |
| Behind the scenes | You can show the work behind a public result | People already saw the result and want the hidden effort | `[Result] took [real effort]. Here is the part nobody saw.` |
| Contrarian | You rejected common advice and have a record | The reader checks a belief they already hold | `Most people say [advice]. I tried the opposite for [period]. Here is what happened.` |
| Relatable | You can name a struggle the reader has now | Recognition comes before trust | `If [specific struggle] is your week, read this.` |
| Client or customer | A real client case taught you something | Proof comes from a third party, not from a claim | `A client asked [question]. The answer changed how we [do X].` |
| Curiosity | Something odd happened and you checked it | An unanswered question makes the reader stay | `[Thing] kept happening. The reason was not where I looked first.` |
| Lesson | You can pack experience into one rule | One line is easy to save | `[N] years of [work] left me with one rule: [rule].` |
| Decision | You chose between two named options | Two options create a real stake | `[Option A] or [Option B]. I picked [one]. Here is why.` |
## Write one hook
1. Name the fact the post can stand on, and the payoff the body can deliver.
2. Draft 3 hooks from 2 or 3 different families. Write them from the fact, not from a swipe file.
3. Drop any hook whose promise the body cannot keep. Drop any hook with an empty or invented blank.
4. Keep 1. Run [no-ai-slop](../no-ai-slop/) and [top-edit](../top-edit/) on that line.
5. Fit the line to the platform: on X it is the whole first line; on LinkedIn it must fit before "see more"; on a video it is the first spoken line.
6. For the rest of an X or LinkedIn post, hand off to [social-copywriting](../social-copywriting/).
Deliver the chosen hook in a code block. Under it, name the family, the fact that fills each blank, and the two hooks you did not use.
[references/swipe-file-carousel-analysis.md](references/swipe-file-carousel-analysis.md) has the evidence for why hook lists get saved.
## Never
- Copy a source hook word for word, or with only a light rewording.
- Invent a number, a client, or a year to fill a blank.
- Promise in the hook what the body does not deliver.
## Inspired by
Thanks to [Chase Dimond, 80 Storytelling Hooks](https://x.com/ecomchasedimond/status/2122793870669062451) (@ecomchasedimond, posted 17 Nov 2026). The post groups fill-in hooks by story type and gives each group a "use when" line. That is the seed for this skill. None of his 80 lines are reproduced here.
Thanks also to these save-first list posts, read with the seed post on 18 Nov 2026:
- [Ruben Hassid, Claude Skills library](https://x.com/rubenhassid/status/2111774301779116541)
- [Ruben Hassid, The AI apps I keep using](https://x.com/rubenhassid/status/2113133252819013808)
- [Shubham Ghumare, AI engineering from scratch](https://x.com/ghumare64/status/2122747671245103475)
- [Jack, 60 AI marketing agents](https://x.com/jack_9947/status/2120920710474346702)
- [Ruben Hassid, One list instead of a course](https://x.com/rubenhassid/status/2118946554551877936)
- [Shubham Ghumare, Free AI engineering curriculum](https://x.com/ghumare64/status/2113599963670397206)
- [Chase Dimond, 6 ways to sell the benefit](https://x.com/ecomchasedimond/status/2122868475999986091)
- [Ruben Hassid, Claude guides I wish I had](https://x.com/rubenhassid/status/2113858021415608437)
- [Jack, Claude marketing skills](https://x.com/jack_9947/status/2122730025518518628)
- [Chase Dimond, 8 biases behind every good offer](https://x.com/ecomchasedimond/status/2116240429805191489)
- [Andrew Bolis, 9 prompts beyond summaries](https://x.com/AndrewBolis/status/2118316155773628622)
This skill adds why each family works, our own templates, a fact rule for every blank, a check that the body pays off the hook, and a draft-three-then-pick-one step.