Kane Hook Point

---
name: kane-hook-point
description: "Create and review attention-winning hooks, matching stories, and credible conversion paths using Brendan Kane's public Hook Point method. Use for short videos, posts, ads, headlines, email openings, and pitches, with variants and a practical test plan."
---

# Hook Point: Stop, Story, Conversion

Based on Brendan Kane's public method. Not affiliated with or endorsed by Brendan Kane.

## When to use

Use this skill when a message contains useful substance but its opening fails to earn attention, when a team needs several original hook directions, or when attention is not producing the intended business action. Apply it to social videos, posts, ads, headlines, email subject lines and opening sentences, or spoken pitches. Start from the audience's experience and the actual value available, rather than polishing a slogan in isolation.

The working sequence is stop the scroll, sustain attention with a relevant story, and earn a credible next action. Kane's public interviews describe attention, story, and authenticity or credibility as interdependent pillars. Conversion is the business outcome supported by those pillars, not a replacement for credibility. Three seconds is an opening design target; it does not require every story to last three seconds or establish a universal attention-span fact.

Produce a reviewable creative brief and original variants using the supplied template. Drafting does not authorize publication, outreach, or paid campaigns. If the brief lacks facts, use clearly marked assumptions for creative development, flag proof gaps, and avoid presenting hypothetical outcomes as verified results. Load the detailed method for substantive work and consult examples only when they help resolve a creative choice.

## Procedure

1. **Frame the assignment.** Read [the deliverable fields](templates/output-template.md). Record the audience, channel, offer, useful value, intended action, evidence available, constraints, and current baseline. Choose the action before choosing a hook so attention serves the user's objective.

2. **Establish the method boundary.** Read [principles and attribution](references/method.md#principles-and-attribution). Distinguish sourced guidance from this package's implementation aids. Consult [the source register](references/sources.md) when explaining Kane's method or checking an attribution.

3. **Understand the audience's context.** Follow [audience and context](references/method.md#audience-and-context). Identify what the audience wants, notices, doubts, and already hears repeatedly. Translate specialist language into a recognizable situation without losing the meaning needed for the offer.

4. **Research competing attention.** Use [comparative research](references/method.md#comparative-research). Examine relevant strong and weak examples, including content outside the immediate industry. Record the suspected mechanism and execution differences rather than copying another creator's wording or assuming every popular post proves a format.

5. **Generate distinct hook directions.** Apply [hook construction](references/method.md#hook-construction). Explore concrete demonstrations, unexpected contexts, useful contrasts, and audience-relevant questions. Include several substantively different hypotheses before making small wording changes. See [the illustrations](examples/worked-examples.md) for complete transformations.

6. **Design the opening as experienced.** Follow [channel adaptation](references/method.md#channel-adaptation). For video, specify the first frame, visible action, spoken line, and readable text. For writing or a pitch, specify the first exposed words and their immediate continuation. Remove setup that postpones the reason to care.

7. **Reject empty interruption.** Apply [the promise test](references/method.md#promise-story-and-credibility). Keep only hooks whose implied promise the available story can fulfill. Replace exaggerated claims, irrelevant surprises, or unsupported numbers with a concrete, demonstrable reason to continue.

8. **Build the story and proof.** Use [story development](references/method.md#story-development). Connect the opening directly to the message, develop tension or useful discovery, and deliver the payoff. Show relevant evidence and limitations where the claim occurs. Select length according to useful sustained attention and channel constraints.

9. **Earn the next action.** Follow [conversion design](references/method.md#conversion-design). Tie a clear, proportionate action to the value just delivered. Specify what happens after the click, reply, or visit, and ensure the destination continues the same promise.

10. **Select and explain candidates.** Complete [the candidate table](templates/output-template.md). Explain why each finalist should stop this audience, how the story fulfills it, and what could fail. Treat editorial selection as a hypothesis until audience evidence exists.

11. **Plan a bounded test.** Use [testing and diagnosis](references/method.md#testing-and-diagnosis). State what changes, what remains comparable, the success measure, available exposure, and stopping conditions. Separate opening attention, story retention, and conversion so a failure suggests a specific revision.

12. **Review and deliver.** Run [the pass/fail checklist](checklists/review-checklist.md). Resolve failures or flag material evidence gaps, then return the filled template, finalists, chosen execution, and test plan. Include [source references](references/sources.md) for method claims, without implying endorsement or guaranteed performance.

## Files in this skill

- [SLUG.txt](SLUG.txt): Canonical package identifier.
- [SKILL.md](SKILL.md): Activation guidance and the compact working procedure.
- [references/method.md](references/method.md): Detailed principles, decisions, adaptations, and testing guidance.
- [references/sources.md](references/sources.md): Numbered register of public sources fetched for this package.
- [examples/worked-examples.md](examples/worked-examples.md): Invented video and email transformations with rule explanations.
- [templates/output-template.md](templates/output-template.md): Fill-in deliverable with field guidance.
- [checklists/review-checklist.md](checklists/review-checklist.md): Pass/fail gates and common repairs.