From creator-stack
Generates optimized titles, headlines, and subject lines for content like YouTube videos, newsletters, emails, and social posts using platform-specific formulas.
npx claudepluginhub kenneth-liao/ai-launchpad-marketplace --plugin creator-stackThis skill uses the workspace's default tool permissions.
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.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
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.
Use this skill when:
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.
Before generating titles, gather the following information from conversation context, the user's filesystem, or by asking the user directly.
Required Information:
Highly Recommended Information:
Collect required information if not already provided. Ask the user for anything missing:
To create an optimized title, I need to understand:
1. What is the content about? (topic)
2. Who is your target audience?
3. What is the main hook or takeaway?
4. Do you have a visual asset (thumbnail, header image)? If so, what does it show?
5. What emotion should the title evoke?
Read the appropriate platform-specific reference file based on the content type identified in Step 1.
Before writing any title, identify the specific question you want in the audience's mind:
Examples of effective questions to prompt:
Generate 3-5 title variations that:
For each title, verify against the universal checklist:
Present title options to the user with:
Example presentation:
Here are 3 optimized title options:
1. "The AI Agent Mistake That Cost Me 10 Hours"
- Prompts: "What mistake? How can I avoid it?"
- Complements thumbnail showing frustrated face + error message
- Creates urgency through time cost
2. "I Built This AI Agent Wrong (Here's What I Learned)"
- Prompts: "What did they do wrong? What's the lesson?"
- Personal experience framing creates relatability
3. "Why Your AI Agents Keep Breaking (And Mine Don't)"
- Prompts: "Why do mine break? What's their secret?"
- Creates contrast and curiosity
If the user requests changes:
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.
When creating assets for The AI Launchpad, invoke creator-stack:brand-guidelines to resolve the correct design system and check anti-patterns.
Regenerate if the title:
A successful title: