yt-research

Research competitor YouTube channels, niches, and trending topics for your content strategy. Use this skill whenever the user says "research channels", "analyze competitors", "find trending topics", "niche analysis", "competitive research", "what are other creators doing", "scrape YouTube channels", or wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.

1,868 stars

Best use case

yt-research is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Research competitor YouTube channels, niches, and trending topics for your content strategy. Use this skill whenever the user says "research channels", "analyze competitors", "find trending topics", "niche analysis", "competitive research", "what are other creators doing", "scrape YouTube channels", or wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.

Teams using yt-research 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

$curl -o ~/.claude/skills/yt-research/SKILL.md --create-dirs "https://raw.githubusercontent.com/jeremylongshore/claude-code-plugins-plus-skills/main/plugins/productivity/youtube-strategy/skills/yt-research/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/yt-research/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How yt-research Compares

Feature / Agentyt-researchStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Research competitor YouTube channels, niches, and trending topics for your content strategy. Use this skill whenever the user says "research channels", "analyze competitors", "find trending topics", "niche analysis", "competitive research", "what are other creators doing", "scrape YouTube channels", or wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.

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

SKILL.md Source

# 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

| Error | Cause | Resolution |
|-------|-------|------------|
| Authentication failure | Invalid or expired credentials | Refresh tokens or re-authenticate with content |
| 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 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

Related Skills

creating-github-issues-from-web-research

1868
from jeremylongshore/claude-code-plugins-plus-skills

Execute this skill enhances AI assistant's ability to conduct web research and translate findings into actionable github issues. it automates the process of extracting key information from web search results and formatting it into a well-structured issue, ready... Use when managing version control. Trigger with phrases like 'commit', 'branch', or 'git'.

research-to-deploy

1868
from jeremylongshore/claude-code-plugins-plus-skills

Researches infrastructure best practices and generates deployment-ready configurations, Terraform modules, Dockerfiles, and CI/CD pipelines. Use when the user needs to deploy services, set up infrastructure, or create cloud configurations based on current best practices. Trigger with phrases like "research and deploy", "set up Cloud Run", "create Terraform for", "deploy this to AWS", or "generate infrastructure configs".

schema-optimization-orchestrator

1868
from jeremylongshore/claude-code-plugins-plus-skills

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

1868
from jeremylongshore/claude-code-plugins-plus-skills

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

1868
from jeremylongshore/claude-code-plugins-plus-skills

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

1868
from jeremylongshore/claude-code-plugins-plus-skills

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

1868
from jeremylongshore/claude-code-plugins-plus-skills

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

1868
from jeremylongshore/claude-code-plugins-plus-skills

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

1868
from jeremylongshore/claude-code-plugins-plus-skills

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

1868
from jeremylongshore/claude-code-plugins-plus-skills

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

1868
from jeremylongshore/claude-code-plugins-plus-skills

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

1868
from jeremylongshore/claude-code-plugins-plus-skills

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".