agentleFS
mategogmategog/mateai-youtube-mcp/skills/yt-packaging/SKILL.md

yt-packaging

Skill1 starsChanged 11 days agoApache-2.0View on GitHub

Create optimized YouTube titles and thumbnail concepts for maximum CTR.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before writing titles, research what's already out there:

    line 41
  2. Distinctive:

    Search YouTube for the topic

    line 43
  3. Distinctive:

    Create 5-10 title options across different strategies:

    line 50
  4. Distinctive:

    Create intrigue without being misleading.

    line 59
  5. Distinctive:

    Create 3-5 thumbnail concepts.

    line 85
  6. Distinctive:

    Create optimized YouTube titles and thumbnail concepts for maximum CTR.

    line 162
  7. Distinctive:

    Document the configuration for team reference

    line 176

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

## 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

ErrorCauseResolution
Authentication failureInvalid or expired credentialsRefresh tokens or re-authenticate with optimization
Configuration conflictIncompatible settings detectedReview and resolve conflicting parameters
Resource not foundReferenced resource missingVerify 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.