yt-packaging
Create optimized YouTube titles and thumbnail concepts for maximum CTR. Use this skill whenever the user says "title ideas", "thumbnail concepts", "package this video", "CTR optimization", "title options", "packaging", or has an approved brief and needs to finalize the title and thumbnail direction before outlining. Packaging determines whether viewers click. Use when working with yt packaging. Trigger with 'yt', 'packaging'.
Best use case
yt-packaging is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create optimized YouTube titles and thumbnail concepts for maximum CTR. Use this skill whenever the user says "title ideas", "thumbnail concepts", "package this video", "CTR optimization", "title options", "packaging", or has an approved brief and needs to finalize the title and thumbnail direction before outlining. Packaging determines whether viewers click. Use when working with yt packaging. Trigger with 'yt', 'packaging'.
Teams using yt-packaging should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/yt-packaging/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How yt-packaging Compares
| Feature / Agent | yt-packaging | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create optimized YouTube titles and thumbnail concepts for maximum CTR. Use this skill whenever the user says "title ideas", "thumbnail concepts", "package this video", "CTR optimization", "title options", "packaging", or has an approved brief and needs to finalize the title and thumbnail direction before outlining. Packaging determines whether viewers click. Use when working with yt packaging. Trigger with 'yt', 'packaging'.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agent for YouTube Script Writing
Find AI agent skills for YouTube script writing, video research, content outlining, and repeatable channel production workflows.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# YouTube Packaging You are creating the title and thumbnail concept for a YouTube video. Packaging is where CTR is determined - the title and thumbnail are the single biggest factor in whether a video succeeds. ## Before You Start You need from the user: 1. **The approved brief** - Either load `video-brief-yt-packaging.md` from the working directory or get the brief details from the user 2. **Timing context** - Is this a trending/update video (speed matters) or evergreen (optimize for long-term search)? 3. **Competitive context** - What titles are competitors using for similar content? (Use WebSearch if not already known) ## The Packaging Process ### Step 1: Competitive Title Analysis Before writing titles, research what's already out there: - Search YouTube for the topic - Note the top 5-10 existing titles - Identify patterns: what words/structures appear in high-view videos? - Identify gaps: what angle is NO ONE using? ### Step 2: Generate Title Options Create 5-10 title options across different strategies: **Strategy A: Direct Benefit** Focus on what the viewer will be able to DO. - "How to [Verb] [Tool] to [Outcome]" - "Build [Thing] with [Tool] in [Time]" **Strategy B: Curiosity Gap** Create intrigue without being misleading. - "The [Tool] Feature Nobody Is Talking About" - "I Automated My Entire [Process] - Here's How" **Strategy C: Authority/Definitive** Position as THE resource. - "The Complete [Tool] Guide for [Year]" - "Everything You Need to Know About [Feature]" **Strategy D: Trending/Urgency** For update videos and time-sensitive content. - "[Tool] Just Changed Everything - Here's What You Need to Know" - "New [Feature] Walkthrough: [Specific Capability]" **For each title:** - Note which strategy it uses - Estimate search-friendliness (contains searchable keywords?) - Estimate curiosity factor (would you click?) - Note the character count (aim for under 60 characters for full display) ### Step 3: Generate Thumbnail Concepts Create 3-5 thumbnail concepts. Each concept should include: **Visual description:** - Main visual element (screen-share preview, tool logo, face expression, graphic) - Text overlay (1-4 words MAX - the thumbnail is not the title) - Color scheme and contrast - Layout (rule of thirds, focal point) **For each concept:** - How does it complement the title? (Title + thumbnail = one message, not two separate messages) - Does it stand out in a feed of similar videos? - Is it readable at mobile size (small thumbnail)? - Does it communicate the value proposition visually? ### Step 4: A/B Test Variants For the top 2-3 title + thumbnail combos, suggest A/B testing variants: - Same title, different thumbnail approach - Same thumbnail, different title strategy - Small tweaks (word swaps, number inclusion) ### Step 5: Present to User Present all options in a structured format: ```markdown ## Title Options | # | Title | Strategy | Keywords | Length | |---|-------|----------|----------|--------| | 1 | [title] | Direct Benefit | [keywords] | 48 chars | | 2 | [title] | Curiosity Gap | [keywords] | 52 chars | ... ## Thumbnail Concepts ### Concept A: [Name] - Visual: [description] - Text overlay: "[text]" - Complements titles: #1, #3 ### Concept B: [Name] - Visual: [description] - Text overlay: "[text]" - Complements titles: #2, #4 ## Recommended Combo Title #[X] + Thumbnail Concept [Y] because [reasoning] ``` "Pick your title and thumbnail direction." - Go with recommended combo - Mix and match (pick different title + thumbnail) - Request more options - Adjust the angle **This is a mandatory human checkpoint.** ### Step 6: Save Save the approved packaging as `packaging-yt-packaging.md`. ## Key Principles - **Title and thumbnail are ONE system.** They must work together. The thumbnail should NOT repeat the title - they should complement each other. Title says what, thumbnail shows the emotion/intrigue. - **No clickbait without substance.** Titles should be compelling but honest. Every promise in the title must be delivered in the video. - **Search + browse balance.** For evergreen content, include searchable keywords. For trending content, prioritize curiosity and urgency. - **Mobile-first thumbnails.** Most YouTube browsing happens on mobile. Thumbnails must be readable at small sizes. - **Under 60 characters.** Titles get truncated on mobile. The most important words should be in the first 40 characters. ## Overview Create optimized YouTube titles and thumbnail concepts for maximum CTR. ## Prerequisites - Access to the optimization environment or API - Required CLI tools installed and authenticated - Familiarity with optimization concepts and terminology ## Instructions 1. Assess the current state of the optimization configuration 2. Identify the specific requirements and constraints 3. Apply the recommended patterns from this skill 4. Validate the changes against expected behavior 5. Document the configuration for team reference ## Output - Configuration files or code changes applied to the project - Validation report confirming correct implementation - Summary of changes made and their rationale ## Error Handling | Error | Cause | Resolution | |-------|-------|------------| | Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with optimization | | Configuration conflict | Incompatible settings detected | Review and resolve conflicting parameters | | Resource not found | Referenced resource missing | Verify resource exists and permissions are correct | ## Examples **Basic usage**: Apply yt packaging to a standard project setup with default configuration options. **Advanced scenario**: Customize yt packaging for production environments with multiple constraints and team-specific requirements. ## Resources - Official optimization documentation - Community best practices and patterns - Related skills in this plugin pack
Related Skills
schema-optimization-orchestrator
Multi-phase schema optimization workflow orchestrator. Creates session directories, spawns phase agents sequentially, validates outputs, aggregates results. Trigger: "run schema optimization", "optimize schema workflow", "execute schema phases"
test-skill
Test skill for E2E validation. Trigger with "run test skill" or "execute test". Use this skill when testing skill activation and tool permissions.
example-skill
Brief description of what this skill does and when the model should activate it. Use when [describe the user's intent or situation]. Trigger with "example phrase", "another trigger", "/example-skill".
testing-visual-regression
Detect visual changes in UI components using screenshot comparison. Use when detecting unintended UI changes or pixel differences. Trigger with phrases like "test visual changes", "compare screenshots", or "detect UI regressions".
generating-unit-tests
Test automatically generate comprehensive unit tests from source code covering happy paths, edge cases, and error conditions. Use when creating test coverage for functions, classes, or modules. Trigger with phrases like "generate unit tests", "create tests for", or "add test coverage".
generating-test-reports
Generate comprehensive test reports with metrics, coverage, and visualizations. Use when performing specialized testing. Trigger with phrases like "generate test report", "create test documentation", or "show test metrics".
orchestrating-test-execution
Test coordinate parallel test execution across multiple environments and frameworks. Use when performing specialized testing. Trigger with phrases like "orchestrate tests", "run parallel tests", or "coordinate test execution".
managing-test-environments
Test provision and manage isolated test environments with configuration and data. Use when performing specialized testing. Trigger with phrases like "manage test environment", "provision test env", or "setup test infrastructure".
generating-test-doubles
Generate mocks, stubs, spies, and fakes for dependency isolation. Use when creating mocks, stubs, or test isolation fixtures. Trigger with phrases like "generate mocks", "create test doubles", or "setup stubs".
generating-test-data
Generate realistic test data including edge cases and boundary conditions. Use when creating realistic fixtures or edge case test data. Trigger with phrases like "generate test data", "create fixtures", or "setup test database".
analyzing-test-coverage
Analyze code coverage metrics and identify untested code paths. Use when analyzing untested code or coverage gaps. Trigger with phrases like "analyze coverage", "check test coverage", or "find untested code".
managing-snapshot-tests
Create and validate component snapshots for UI regression testing. Use when performing specialized testing. Trigger with phrases like "update snapshots", "test UI snapshots", or "validate component snapshots".