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

yt-research

Skill1 starsChanged 12 days agoApache-2.0View on GitHub

Research competitor YouTube channels, niches, and trending topics for

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. utillayer/youtube-agent-skill★ 10same name
    2. qwwiwi/agentos-skills-public★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository11 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user provided context already, confirm your understanding and proceed.

    line 37
  2. Distinctive:

    Use web research to collect:

    line 53
  3. Very specific:

    If Apify MCP is available, spawn yt-scraper sub-agent for bulk data collection.

    line 59
  4. Very specific:

    If analyzing 4+ channels, spawn channel-analyzer sub-agents (3 channels per agent) for parallel processing.

    line 71
  5. Distinctive:

    Strategy-first: - Every finding must connect back to the creator's goals and audience.

    line 121
  6. Distinctive:

    Actionable outputs: - Every content gap should translate directly into a potential video idea.

    line 123
  7. Distinctive:

    Respect rate limits: - When using APIs, handle timeouts gracefully and never hammer endpoints.

    line 124
  8. Distinctive:

    Document the configuration for team reference

    line 143

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 Research

You are conducting competitive research for a YouTube channel. Your goal is to analyze competitor channels, identify content gaps, discover trending topics, and surface opportunities aligned with the creator's strategy.

Before You Start

You need from the user:

  1. Research focus - What niche, tool, or topic area to research (e.g., "AI tools for professionals", "MCP integrations", "productivity software")
  2. Competitor channels (optional) - Specific YouTube channel URLs to analyze
  3. Specific angle (optional) - Is there a particular feature, update, or trend they want to investigate?

If the user provided context already, confirm your understanding and proceed.

The Research Process

Step 1: Scope the Research

Define the research boundaries:

  • Which channels to scrape (user-provided + discovered competitors)
  • Which topics/keywords to search for
  • Time horizon (recent 30 days, 90 days, or all-time)

Tell the user the plan: "I'll analyze [N] channels and search for [keywords]. This will involve web research and data collection."

Step 2: Collect Channel Data

Use web research to collect:

  • Channel metadata (subscribers, total videos, posting frequency)
  • Recent videos (last 30-50 per channel): titles, views, likes, comments, publish dates
  • Video tags and categories where available

If Apify MCP is available, spawn yt-scraper sub-agent for bulk data collection.

Step 3: Analyze Channels

For each channel, analyze:

  • Engagement pattern analysis (what gets views vs what doesn't)
  • Content type distribution (tutorials, reviews, updates, opinions)
  • Title pattern analysis (what structures and words correlate with views)
  • Outlier video identification (3x+ above channel average)
  • Topic coverage map (what's covered, what's missing)

If analyzing 4+ channels, spawn channel-analyzer sub-agents (3 channels per agent) for parallel processing.

Step 4: Identify Opportunities

Using the analysis results, identify:

Content Gaps:

  • Topics the audience searches for but competitors cover poorly
  • Topics that are developer-focused everywhere but could be made accessible
  • Recent tool updates/features with no quality coverage yet

Trending Signals:

  • Tools/features getting increasing search interest
  • Topics with recent outlier videos (sudden view spikes)
  • Community discussions (Reddit, forums) indicating unmet demand

Strategic Fit:

  • Which opportunities align with the creator's content pillars?
  • Which serve the target audience?
  • Which have the best effort-to-impact ratio?

Step 5: Export Results

Generate two outputs:

  1. niche-analysis.json - Structured data with per-channel metrics, outlier videos, content gaps, and opportunity scores
  2. niche-report.md - Human-readable research report with:
    • Executive summary (3-5 key findings)
    • Per-channel analysis highlights
    • Top 10 content opportunities ranked by potential
    • Recommended next steps

Present the report to the user:

"Here's the research report. Key findings:"

  • [Top 3 findings]

"What would you like to do?"

  • Move to ideation with these insights
  • Research additional channels
  • Dig deeper into a specific finding
  • Export and save for later

Key Principles

  • Strategy-first - Every finding must connect back to the creator's goals and audience. Don't surface opportunities that don't serve the target audience.
  • Data over opinion - Ground insights in actual view counts, engagement rates, and search data. "This seems popular" is useless. "This video got 3.2x the channel average with 45K views in 2 weeks" is useful.
  • Actionable outputs - Every content gap should translate directly into a potential video idea. Don't just say "competitors don't cover X" - say "competitors don't cover X, and here's evidence that people are searching for it."
  • Respect rate limits - When using APIs, handle timeouts gracefully and never hammer endpoints.
  • Save everything to disk - Persist all collected data and analysis results as JSON files immediately. Never hold large datasets only in conversation context.

Overview

Research competitor YouTube channels, niches, and trending topics for your content strategy.

Prerequisites

  • Access to the content environment or API
  • Required CLI tools installed and authenticated
  • Familiarity with content concepts and terminology

Instructions

  1. Assess the current state of the content 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 content
Configuration conflictIncompatible settings detectedReview and resolve conflicting parameters
Resource not foundReferenced resource missingVerify resource exists and permissions are correct

Examples

Basic usage: Apply yt research to a standard project setup with default configuration options.

Advanced scenario: Customize yt research for production environments with multiple constraints and team-specific requirements.

Resources

  • Official content 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.