Skip to content

botkitsdev/botkits / skills/writing/botkits-storytelling-hooks

botkits-storytelling-hooks

Verified

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.

FileKindSize
README.mdmarkdown3.2 KB
SKILL.mdskill md5.4 KB
references/patterns.mdmarkdown7.8 KB
references/swipe-file-carousel-analysis.mdmarkdown8.6 KB

references/patterns.md

View on GitHub
# Hook family patterns

Our own fill-in templates, sorted by family. Use them to write a hook.

Do not paste another writer's hooks into a post or a slide. Every blank needs a real fact from the person who will publish. If a fact is missing, pick another family or leave the blank visible on a demo slide.

Thanks to [Chase Dimond, 80 Storytelling Hooks](https://x.com/ecomchasedimond/status/2122793870669062451) for the ten family names and the "use when" plus fill-in shape. The "why it works" lines and every template below are ours. The 11 other posts in [swipe-file-carousel-analysis.md](swipe-file-carousel-analysis.md) are cited as evidence for why hook lists get saved, not as lines to copy.

## Transformation

Use when you can name your own before and after.

Why it works: a gap between two states makes the reader want the path.

1. `[Old state] in [month]. [New state] now. The change was smaller than you think.`
2. `[Time period] ago I stood at [start]. The move to [end] was one habit, not a rebuild.`
3. `From [metric A] to [metric B] in [period]. I will show the dull step that moved the line.`
4. `I kept a log from [start date] to [end date]. The figure that moved was [metric].`
5. `[Old belief] used to run my week. [New practice] replaced it after [event].`
6. `I can name the day I left [old state]: [date]. What followed was [result].`
7. `[N] weeks of [practice] took me from [A] to [B]. Here is the weekly total.`
8. `The gap between [before] and [after] was [one change], done every [cadence].`

## Mistake

Use when you can name a failure and what it cost.

Why it works: a concrete cost makes the lesson specific, and the reader wants to avoid it.

1. `This cost me [real cost]. Here is the step I skipped.`
2. `I paid [amount or time] because I ignored [warning] on [date].`
3. `The error was [specific act]. It took [recovery time] to undo.`
4. `[Project] failed when I skipped [step]. The bill was [cost].`
5. `I still have the note from [date]: I chose [bad call] over [safer call].`
6. `After [failure], I wrote one rule: never [specific act] without [check].`
7. `[N] hours went into a fix that one review would have caught.`
8. `I lost [client or chance] when I [mistake]. I do [new check] now.`

## Turning point

Use when one event changed how you work.

Why it works: one cause is easy to remember.

1. `I was about to drop [goal]. Then [one event].`
2. `On [date], [event] ended the way I did [old approach].`
3. `One [meeting, email, or demo] on [date] reversed my plan for [work].`
4. `I had the quit note drafted for [goal]. [Event] stopped me sending it.`
5. `Until [event], I treated [topic] as [old view]. I do not anymore.`
6. `[Date] is the split: before it I [old action], after it I [new action].`
7. `A single [constraint or tool] showed up and [goal] started to move.`
8. `I can point to [event] as the reason I changed [process].`

## Behind the scenes

Use when you can show the work behind a public result.

Why it works: people already saw the result and want the hidden effort.

1. `[Result] took [real effort]. Here is the part nobody saw.`
2. `The public [result] hides [N] drafts and [hours] of cuts.`
3. `Before [result] shipped, I threw out [N] versions of [artifact].`
4. `The work that made [result] was [unglamorous task], done on [days].`
5. `People saw [result]. They did not see [failed attempt] from [date].`
6. `The calendar behind [result]: [N] work sessions, [N] dead ends.`
7. `I kept the raw log for [project]. The useful page is not the launch post.`
8. `[Result] looks short. The checklist I used has [N] items.`

## Contrarian

Use when you rejected common advice and have a record.

Why it works: the reader checks a belief they already hold.

1. `Most people say [advice]. I tried the opposite for [period]. Here is what happened.`
2. `I ran [popular practice] for [period] and measured [metric]. Then I stopped.`
3. `The usual tip is [advice]. My log for [period] shows [different result].`
4. `I dropped [common tactic] on [date]. [Metric] over the next [period] was [value].`
5. `[Popular belief] failed me on [project]. I switched to [other method].`
6. `For [period] I did the reverse of [advice]. The record is [result].`
7. `I do not follow [common rule] anymore. [Proof] is why.`
8. `Everyone around me still does [practice]. I stopped on [date] after [result].`

## Relatable

Use when you can name a struggle the reader has now.

Why it works: recognition comes before trust.

1. `If [specific struggle] is your week, read this.`
2. `When [task] takes [longer than planned] and [other duty] still waits, this is the note I keep.`
3. `[Specific struggle] showed up again on [day]. I handled it by [step].`
4. `You can be deep into [work] and still feel late. I was there in [month].`
5. `The part of [job] nobody briefed me on was [task]. I wrote down how I do it now.`
6. `If [morning or weekly pattern] keeps slipping, here is the check I added.`
7. `I have had [struggle] for [period]. The useful move was [small step].`
8. `This is for the person mid-[project] who cannot see [next step] yet.`

## Client or customer

Use when a real client case taught you something.

Why it works: proof comes from a third party, not from a claim.

1. `A client asked [question]. The answer changed how we [do X].`
2. `On [project], the buyer said [quote]. We changed [process] the same week.`
3. `[Client type] came in with [problem]. The fix that stuck was [change].`
4. `We almost shipped [bad option] for [client]. Their question about [topic] stopped us.`
5. `A [support or sales] note on [date] made us drop [old approach].`
6. `After [failed campaign] for [client], the post-mortem gave us [one lesson].`
7. `[Client] wanted [outcome]. What worked was [small change], not [big change].`
8. `One sentence from [customer] on [date] is now a line in our [checklist or brief].`

## Curiosity

Use when something odd happened and you checked it.

Why it works: an unanswered question makes the reader stay.

1. `[Thing] kept happening. The reason was not where I looked first.`
2. `I could not explain [odd result] until I opened [log, file, or source].`
3. `[Metric] jumped on [date] for no obvious reason. The cause was [finding].`
4. `A stray [detail] in [place] did not match [expectation]. I followed it.`
5. `I ran [test] to settle [question]. The output was not the one I predicted.`
6. `[Pattern] showed up [N] times. I only trusted it after [check].`
7. `The first place I searched for [answer] was wrong. The right one was [place].`
8. `I wrote down [odd fact] and came back a week later with [finding].`

## Lesson

Use when you can pack experience into one rule.

Why it works: one line is easy to save.

1. `[N] years of [work] left me with one rule: [rule].`
2. `If I could brief [past self] in one line, I would say [rule].`
3. `I got more from [rough experience] than from [course or book]. The takeaway: [rule].`
4. `Three notes I kept after [experience]: [1], [2], [3].`
5. `The only principle I still use from [period] is [principle].`
6. `I used to need [complex system]. I now use [one rule] and a log.`
7. `My clearest lesson on [topic] came from [unexpected source], not from [expected source].`
8. `[N] failed tries at [task] taught me to [specific practice] first.`

## Decision

Use when you chose between two named options.

Why it works: two options create a real stake.

1. `[Option A] or [Option B]. I picked [one]. Here is why.`
2. `I turned down [opportunity] on [date]. The reason was [constraint].`
3. `The choice I delayed until [date] was [decision]. Waiting cost me [cost].`
4. `Saying no to [opportunity] protected [thing I valued].`
5. `I accepted a risk of [concrete downside] when I chose [option].`
6. `The harder path was [option]. I took it because [reason], and [result] followed.`
7. `I had the yes ready for [offer]. One question, [question], made me stop.`
8. `From this year, the choice that still shapes my week is [decision].`
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall