creator-stack/skills/hook/SKILL.md
Create retention-optimized opening hooks for any content type. Use when designing a video intro, newsletter opening paragraph, social post hook, or when the user mentions "hook", "opening", "intro", "first 15 seconds", "retention", or "how should I start this".
npx skillsauth add kenneth-liao/ai-launchpad-marketplace hookInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill provides concrete requirements and proven patterns for creating opening hooks that retain audience attention, extend title/headline curiosity, and maximize engagement. The opening content is critical for retention across all platforms — video, email, and social.
Core Principle: The opening works best when it extends the curiosity created by the title/headline rather than repeating or wasting it. Because the audience already engaged based on the title's promise, attention momentum is at its peak — the opening should add new intrigue and make them even more interested.
Use this skill when:
Before creating hooks, determine the content type and load the appropriate platform-specific reference file:
| Content Type | Reference File | Opening Format |
|---|---|---|
| YouTube video | references/youtube-hooks.md | First 5-15 seconds of video |
| Newsletter | references/newsletter-hooks.md | First paragraph / preview text |
| Social post | references/social-hooks.md | First line / hook tweet |
Essential: Read the relevant reference file before creating hooks — these references contain platform-specific patterns, timing requirements, and patterns to avoid that directly affect retention.
If the content type does not match any reference file, apply the universal principles below and adapt to the format.
The opening works best when it builds upon the intrigue from the title/headline rather than repeating it.
CORRECT Example:
INCORRECT Example:
The opening should make the audience more interested than when they engaged. Attention should increase, not drain.
Essential: Opening content should directly relate to the title/headline promise, because any disconnect breaks the trust that brought the audience in.
Guidelines:
These patterns consistently fail because each one drains the attention momentum the title created:
Avoid restating what the title already communicated. The audience already has this information — repetition signals that the content won't offer anything new, and attention drops.
Avoid starting with greetings, welcomes, or introductions before the hook. Greetings are fine after the initial hook is established, but leading with them delays the payoff.
Avoid opening with tangents, stories, or content disconnected from the title/headline promise. Audience confusion triggers abandonment — they came for a specific promise and need immediate confirmation they're in the right place.
Use one of these proven hook structures:
Show a brief glimpse of the payoff before diving into the full content.
Creates thought: "I need to know how to do that!" or "I need to read this."
Works best for: Educational content, tutorials, how-to guides.
Add surprising context that makes the promise MORE compelling than the title alone.
Example: Title about a technique -> Open with "What I'm about to show you took professionals years to discover, but you'll learn it in 60 seconds."
Creates thought: "This is even better than I expected!"
Works best for: Expert content, reveals, insider knowledge.
Immediately validate why the audience needs this content by amplifying the problem.
Example: Title about mistakes -> Open with "If you're doing [X], you're losing [specific bad outcome]."
Creates thought: "I need to fix this now!"
Works best for: Problem-solving content, mistake-avoidance content.
Jump straight into delivering on the promise. No preamble, just results.
Creates thought: "This is exactly what I came for!"
Works best for: Tactical content, quick tips, high-value insights.
When creating or reviewing opening hooks, follow this workflow:
Before finalizing any written output, invoke the creator-stack:voice skill to apply voice rules. Hooks should reflect the user's authentic voice, not generic copywriting language.
When creating assets for The AI Launchpad, invoke creator-stack:brand-guidelines to resolve the correct design system and check anti-patterns.
Before finalizing any opening hook, verify ALL of these:
Bad: "Hi everyone, welcome! Thanks so much for being here..."
Problem: Drains attention before value is delivered.
Bad: Title: "5 AI Agent Patterns"
Opening: "Today I'm showing you 5 AI agent patterns"
Problem: Audience already knows this. No new information.
Bad: Title: "Amazing Coding Hack"
Opening: "So I was browsing GitHub yesterday and I saw
this interesting repo and it reminded me of..."
Problem: Takes too long to get to the promised content.
Bad: "Before we get started, let me explain why this is
important and give you some background on..."
Problem: Delays the payoff. Audience loses patience.
Priority Order (highest to lowest):
The strongest hooks avoid these three patterns because each one drains the attention the title created: repeating the title, greeting before hooking, or starting with unrelated content. Regenerate if any of these are present, regardless of other qualities.
development
Manage scheduled Claude Code tasks — add (recurring or one-off), list, pause, resume, remove, view results, and test execution of skills, prompts, and scripts with safety controls and notifications. Use when the user mentions scheduling, cron, automated tasks, recurring tasks, background tasks, running something on a schedule, periodic execution, or wants a skill/prompt/script to run automatically at a set time. Cross-platform (macOS, Linux, Windows).
tools
Upgrade a plugin's skills, hooks, and patterns to align with latest Claude Code capabilities and best practices. Use when a plugin needs modernization, after Claude Code updates, or when the user says "upgrade plugin", "modernize plugin", or "update plugin to latest patterns".
tools
Use when reviewing how skills performed during a session, when the user wants to analyze skill invocations and identify improvements, or when the user says "skill retro", "review skills", "how did skills do", "improve this skill", or "skill retrospective".
tools
Run or generate test suites for any skill. Use when testing a skill before deployment, after making changes, before/after plugin upgrades, when validating skill behavior, or when the user says "test skill", "run skill tests", "generate tests for skill", or "check for regressions".