kenneth-liao/ai-launchpad-marketplace/title
Claude Code and agent skill by kenneth-liao/ai-launchpad-marketplace
- community
Checking that the SKILL.md file is still in the repository.
Generate optimized titles, headlines, and subject lines for any content type. Use when asked to create a title, headline, subject line, or when the user says "title ideas", "what should I call this", "subject line options", or needs engagement-optimized naming for videos, newsletters, or social posts.
Install
npx vskill@latest install kenneth-liao/ai-launchpad-marketplace/titleSKILL.md
Title Generation
Overview
This skill generates high-performing titles and headlines optimized for engagement across any content type. Titles are designed to spark curiosity, complement visual assets where applicable, and compel the audience to click, open, or engage.
Core Principle: Every title must prompt a specific question in the audience's mind. Description alone is insufficient — curiosity is non-negotiable.
When to Use
Use this skill when:
- The user asks to create a title, headline, or subject line
- The user requests title ideas or brainstorming for content
- The user wants to improve or optimize an existing title
- Working on content creation and a title is needed
- The user asks for multiple title variations to test
Content Type Resolution
Before generating titles, determine the content type and load the appropriate platform-specific reference file:
| Content Type | Reference File | Key Focus | |
|---|---|---|---|
| YouTube video | references/youtube-title-formulas.md | CTR, curiosity, thumbnail complementarity | |
| Newsletter / email | references/newsletter-subject-lines.md | Open rate, preview text, inbox competition | |
| Social media post | references/social-headlines.md | Scroll-stopping, platform-specific hooks |
Essential: Read the relevant reference file before generating titles — each platform has unique patterns and constraints that directly affect performance, and skipping this step leads to generic titles that underperform.
If the content type does not match any reference file, apply the universal principles below and adapt to the format.
Prerequisites
Gather Context
Before generating titles, gather the following information from conversation context, the user's filesystem, or by asking the user directly.
Required Information:
- Content topic: What is the content about?
- Target audience: Who is this for?
- Key message: What is the main takeaway or hook?
Highly Recommended Information:
- Visual asset description: What does the thumbnail, header image, or preview show?
- Target emotion: What emotion should the title evoke? (curiosity, shock, excitement, urgency)
- Content type: Video, newsletter, social post, blog article, etc.
Title Generation Workflow
Step 1: Gather Context
Collect required information if not already provided. Ask the user for anything missing:
Step 2: Load Platform Reference
Read the appropriate platform-specific reference file based on the content type identified in Step 1.
Step 3: Identify the Question
Before writing any title, identify the specific question you want in the audience's mind:
- What question will make them curious enough to engage?
- Does this question align with the content?
- Is the curiosity gap strong enough to drive action?
Examples of effective questions to prompt:
- "What mistakes am I making?" (mistake framing)
- "What happened?" (outcome uncertainty)
- "Why would someone do that?" (extreme behavior)
- "How is that possible?" (surprising claim)
Step 4: Generate Title Options
Generate 3-5 title variations that:
- Prompt the identified question
- Complement (not duplicate) any visual assets
- Align with the target emotion
- Follow platform-specific best practices from the reference file
Step 5: Verify Against Checklist
For each title, verify against the universal checklist:
- [ ] Curiosity Test: Does this prompt a specific question?
- [ ] Complementarity Test: Does this work WITH visual assets (not duplicate them)?
- [ ] Click/Open Compulsion Test: Is the curiosity gap strong enough?
- [ ] Non-Descriptive Test: Does this go beyond merely describing content?
- [ ] Target Audience Test: Will this resonate with the intended audience?
Step 6: Present and Refine
Present title options to the user with:
- The title itself
- The question it prompts in the audience's mind
- How it complements the visual asset (if applicable)
- Why it should drive engagement
Example presentation:
Step 7: Iterate Based on Feedback
If the user requests changes:
- Understand what aspect needs adjustment (curiosity, tone, length, etc.)
- Regenerate while maintaining checklist compliance
- Re-verify against the checklist
Voice Application
Before finalizing any written output, invoke the creator-stack:voice skill to apply voice rules. Titles should sound authentic to the user's voice, not generic.
Brand Compliance
When creating assets for The AI Launchpad, invoke creator-stack:brand-guidelines to resolve the correct design system and check anti-patterns.
Quality Assurance
Priority Order
- Spark curiosity (highest priority)
- Complement visual asset
- Raise audience question
- Create click/open compulsion
Rejection Criteria
Regenerate if the title:
- Merely describes the content without sparking curiosity
- Duplicates text that appears on the visual asset
- Answers the question instead of raising it
- Uses generic patterns without intrigue
- Fails the "What question does this raise?" test
Success Criteria
A successful title:
- Prompts a specific, compelling question in the audience's mind
- Works synergistically with any visual asset
- Creates a curiosity gap strong enough to drive engagement
- Aligns with the target audience and content type
- Passes all 5 universal checklist items
Common Pitfalls
- Generic Description: "AI Agents Tutorial" describes but does not intrigue. Add curiosity.
- Answering the Question: "How to Fix AI Agent Memory in 3 Steps" gives away too much. Tease, do not tell.
- Ignoring Platform: A YouTube title and a newsletter subject line have different constraints. Load the right reference.
- Thumbnail/Asset Duplication: If the thumbnail says "BROKEN", the title should not also say "broken." Complement, do not repeat.
- Single Option: Always provide 3-5 variations for the user to choose from.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingcreator-stack/skills/title/SKILL.md
Popularity
- 7-day trend score
- 0
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/kenneth-liao/ai-launchpad-marketplace/title)