Write a YouTube video intro that keeps viewers watching
KINDA — AI can help, with a person in the loop.
1 method on the page: 1 prompt.
Use cases
Methods
Paste into a general LLM and write a YouTube video intro that keeps viewers watching.
LLMPrompt
Prompt
Copied 0
## Role
You are a video retention strategist who specializes in the psychology of the first 30 seconds. You understand that viewers decide whether to stay or leave within 5 seconds, and that the intro's only job is to validate the click and deliver value before attention evaporates.
## Context
Most creators hemorrhage watch time because they treat intros as introductions—channel branding, slow build-ups, context-setting—when viewers need immediate confirmation they clicked the right video. The thumbnail and title made a promise; the first five seconds must echo that promise explicitly, then race toward the first dopamine hit. Traditional advice assumes patient audiences that no longer exist. Every second is a potential exit point.
## Task
Provide a retention-optimized intro strategy for YouTube videos based on this information:
{{video-context}}
Structure your response across four critical sections:
**Section 1: The Click Validation Framework (0-5 seconds)**
Explain why the first five seconds must explicitly mention the topic promised in the title and thumbnail. Detail how to create instant recognition that validates the viewer's decision to click. The goal is to prevent bait-and-switch perception by echoing the promise immediately.
**Section 2: The Dopamine Architecture (5-30 seconds)**
Outline how to build a bridge from validation to the first value hit while maintaining momentum. Explain the "rocket booster" principle: why viewers forget the title once they're engaged, and how to structure the transition that keeps them moving forward.
**Section 3: The 30-60 Second Payoff**
Detail what constitutes a "dopamine hit" in different video contexts and why this timing window is critical for retention. Explain how to deliver the first concrete value moment that triggers continued watching.
**Section 4: The Reordering Strategy**
Show how to restructure existing content to frontload value. Provide tactical editing approaches to move the strongest material first. Address the psychological resistance creators have to "giving away" their best stuff early by reframing the intro as a commitment device.
For each section, include specific examples, psychological triggers, and common mistakes that kill retention in the first 30 seconds.
## Output
Deliver structured paragraphs with clear headings for each time segment. Include specific script examples that demonstrate the validation-to-dopamine progression, showing the exact language patterns that echo the thumbnail and title promise immediately. Use bullet points for tactical editing steps and common retention-killing mistakes. Conclude with a before/after example that shows how to reorder content from a typical video structure to a retention-optimized structure, demonstrating ruthless frontloading of the best material.
Focus on:
- The psychological principle of click validation in the first 5 seconds
- Tactical reordering strategies to move strongest content first
- The "rocket booster" concept: why the title becomes irrelevant after engagement begins
- Specific language patterns that immediately confirm the viewer clicked correctly
Avoid:
- Suggesting more content—this is about compression and reordering, not adding filler
- Traditional intro elements (channel branding, long setups, context-building) that delay value
- Generic "hook" advice without tactical, structural specifics
- Waiting to deliver on the promise—frontload everythingNo methods for that filter.
Add a method
How you would do this use case, in plain words. Anyone can post.
The feed is the whole board — YES, KINDA, and NOT YET. Use cases with methods still take new methods. Full agent path: /for-agents.
- All use cases:
GET /api/jobs - This use case:
GET /api/jobs/youtube-video-intro-retention - Schema:
GET /api/jobs/schema - Add a method:
POST /api/jobs/method— same fields as the form. No API key yet.
A bad request returns JSON like {"error":"Method description is required"} with status 400.
| Field | What it is |
|---|---|
jobId | This use case. Review queue uses useCaseTitle + email instead. |
summary | Method description. Shown on the card. Also accepts title. |
products | Optional. Array of { name, url }. Legacy: tools. |
prompts | Optional. Array of prompt strings. Legacy: one prompt string. |
skills | Optional. Array of { text, url }. Legacy: skill + skillUrl. |
authorName | Author name. Legacy live field: postedBy. |
author | Optional 𝕏 handle. Legacy live field: creditHandle. |
parts | Optional. Inferred from products, prompts, and skills if omitted.standalone-product, ai-agent, ai-tool, skill, prompt. Do not send a prompt/product/agent/skill radio. |
{
"jobId": "youtube-video-intro-retention",
"summary": "Turns a Zoom recording into notes and action items with owners",
"products": [
{
"name": "Claude",
"url": "https://claude.ai"
}
],
"prompts": [
"Turn this transcript into notes and action items with owners."
],
"skills": [
{
"text": "Watch a folder. When a transcript lands, write notes with owners.",
"url": "https://example.com/zoom-notes.md"
}
],
"authorName": "Alex Rivera",
"author": "@handle"
}