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'.
What this skill does
# 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 in Image & Video
watch
IncludedWatch a video (URL or local path). Downloads with yt-dlp, extracts auto-scaled frames with ffmpeg, pulls the transcript from captions (or Whisper API fallback), and hands the result to Claude so it can answer questions about what's in the video.
physical-ai-defect-image-generation
IncludedUse when the user wants to orchestrate defect image generation, run associated setup, or handle outputs on OSMO. The Day 0 path handles cold-start with USD-to-ROI, image-edit augmentation, and AnomalyGen to create initial PCBA datasets. The Day 1 path performs inference and labeling on real images. This skill helps with first-time asset setup, creation of finetuning checkpoints, and configuring deployment. Trigger keywords: defect image generation, dig workflow, dig pipeline, defect image detection workflow, aoi pipeline, aoi anomalygen, usd2roi anomalygen, day 0 pcba, day 1 pcba, day 1 real-photo alignment, day 1 manual roi, metal surface anomaly, glass defect, anomalygen finetune, setup_pcb, setup_metal, setup_glass, setup_pretrained, dig setup, dig datasets, dig pretrained checkpoint, dig image-edit endpoint.
accelint-react-best-practices
IncludedReact performance optimization and best practices. ALWAYS use this skill when working with any React code - writing components, hooks, JSX; refactoring; optimizing re-renders, memoization, state management; reviewing for performance; fixing hydration mismatches; debugging infinite re-renders, stale closures, input focus loss, animations restarting; preventing remounting; implementing transitions, lazy initialization, effect dependencies. Even simple React tasks benefit from these patterns. Covers React 19+ (useEffectEvent, Activity, ref props). Triggers - useEffect, useState, useMemo, useCallback, memo, inline components, nested components, components inside components, re-render, performance, hydration, SSR, Next.js, useDeferredValue, combined hooks.
elevenlabs-agents
IncludedBuild conversational AI voice agents with ElevenLabs Platform using React, JavaScript, React Native, or Swift SDKs. Configure agents, tools (client/server/MCP), RAG knowledge bases, multi-voice, and Scribe real-time STT. Use when: building voice chat interfaces, implementing AI phone agents with Twilio, configuring agent workflows or tools, adding RAG knowledge bases, testing with CLI "agents as code", or troubleshooting deprecated @11labs packages, Android audio cutoff, CSP violations, dynamic variables, or WebRTC config. Keywords: ElevenLabs Agents, ElevenLabs voice agents, AI voice agents, conversational AI, @elevenlabs/react, @elevenlabs/client, @elevenlabs/react-native, @elevenlabs/elevenlabs-js, @elevenlabs/agents-cli, elevenlabs SDK, voice AI, TTS, text-to-speech, ASR, speech recognition, turn-taking model, WebRTC voice, WebSocket voice, ElevenLabs conversation, agent system prompt, agent tools, agent knowledge base, RAG voice agents, multi-voice agents, pronunciation dictionary, voice speed control, elevenlabs scribe, @11labs deprecated, Android audio cutoff, CSP violation elevenlabs, dynamic variables elevenlabs, case-sensitive tool names, webhook authentication
humanizer
IncludedHumanize AI-generated text by detecting and removing patterns typical of LLM output. Rewrites text to sound natural, specific, and human. Uses 28 pattern detectors, 560+ AI vocabulary terms across 3 tiers, and statistical analysis (burstiness, type-token ratio, readability) for comprehensive detection. Use when asked to humanize text, de-AI writing, make content sound more natural/human, review writing for AI patterns, score text for AI detection, or improve AI-generated drafts. Covers content, language, style, communication, and filler categories.
generating-mermaid-diagrams
IncludedSalesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says "diagram", "visualize", "ERD", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems.