@intentsolutionsio/youtube-strategy 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/plugin.json +20 -0
- package/README.md +51 -0
- package/agents/channel-analyzer.md +77 -0
- package/agents/idea-validator.md +89 -0
- package/agents/yt-scraper.md +59 -0
- package/commands/youtube-strategy.md +22 -0
- package/commands/yt-brief.md +13 -0
- package/commands/yt-ideate.md +13 -0
- package/commands/yt-outline.md +13 -0
- package/commands/yt-package.md +13 -0
- package/commands/yt-pipeline.md +160 -0
- package/commands/yt-research.md +13 -0
- package/package.json +43 -0
- package/skills/yt-brief/SKILL.md +146 -0
- package/skills/yt-ideation/SKILL.md +168 -0
- package/skills/yt-outline/SKILL.md +187 -0
- package/skills/yt-packaging/SKILL.md +182 -0
- package/skills/yt-research/SKILL.md +151 -0
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "youtube-strategy",
|
|
3
|
+
"version": "1.0.0",
|
|
4
|
+
"description": "Complete YouTube content production workflow: research competitors, generate video ideas, build briefs, craft titles and thumbnails, and create detailed video outlines with demo prep checklists.",
|
|
5
|
+
"author": {
|
|
6
|
+
"name": "Claude Code Plugins"
|
|
7
|
+
},
|
|
8
|
+
"license": "MIT",
|
|
9
|
+
"keywords": [
|
|
10
|
+
"youtube",
|
|
11
|
+
"content-strategy",
|
|
12
|
+
"video-production",
|
|
13
|
+
"ideation",
|
|
14
|
+
"research",
|
|
15
|
+
"thumbnails",
|
|
16
|
+
"titles",
|
|
17
|
+
"outlining",
|
|
18
|
+
"content-creation"
|
|
19
|
+
]
|
|
20
|
+
}
|
package/README.md
ADDED
|
@@ -0,0 +1,51 @@
|
|
|
1
|
+
# YouTube Strategy Plugin
|
|
2
|
+
|
|
3
|
+
Complete YouTube content production workflow powered by AI. Research competitors, generate video ideas, build production briefs, craft optimized titles and thumbnails, and create detailed video outlines.
|
|
4
|
+
|
|
5
|
+
## Skills
|
|
6
|
+
|
|
7
|
+
| Skill | What It Does |
|
|
8
|
+
|-------|-------------|
|
|
9
|
+
| `yt-research` | Research competitor channels, niches, and trending topics |
|
|
10
|
+
| `yt-ideation` | Generate and validate video ideas aligned with content pillars |
|
|
11
|
+
| `yt-brief` | Refine a video idea into a structured production brief |
|
|
12
|
+
| `yt-packaging` | Create optimized titles and thumbnail concepts for maximum CTR |
|
|
13
|
+
| `yt-outline` | Build step-by-step video outlines with demo prep and visual planning |
|
|
14
|
+
|
|
15
|
+
## Commands
|
|
16
|
+
|
|
17
|
+
| Command | Description |
|
|
18
|
+
|---------|-------------|
|
|
19
|
+
| `/youtube-strategy` | See all available skills and choose what to work on |
|
|
20
|
+
| `/yt-pipeline` | Run the complete Research > Ideate > Brief > Package > Outline workflow |
|
|
21
|
+
| `/yt-research` | Research competitor channels and trending topics |
|
|
22
|
+
| `/yt-ideate` | Generate and validate video ideas |
|
|
23
|
+
| `/yt-brief` | Create a structured production brief |
|
|
24
|
+
| `/yt-package` | Create optimized titles and thumbnail concepts |
|
|
25
|
+
| `/yt-outline` | Build a detailed video outline with demo prep |
|
|
26
|
+
|
|
27
|
+
## Agents
|
|
28
|
+
|
|
29
|
+
| Agent | Purpose |
|
|
30
|
+
|-------|---------|
|
|
31
|
+
| `yt-scraper` | Orchestrate YouTube data scraping via Apify |
|
|
32
|
+
| `channel-analyzer` | Competitive intelligence analysis per channel batch |
|
|
33
|
+
| `idea-validator` | Validate video ideas against search demand and competition |
|
|
34
|
+
|
|
35
|
+
## Workflow
|
|
36
|
+
|
|
37
|
+
The recommended workflow follows these stages:
|
|
38
|
+
|
|
39
|
+
1. **Research** (`/yt-research`) - Analyze competitors, identify content gaps
|
|
40
|
+
2. **Ideation** (`/yt-ideate`) - Generate 15-20 ideas, validate against demand
|
|
41
|
+
3. **Brief** (`/yt-brief`) - Refine selected ideas into production briefs
|
|
42
|
+
4. **Packaging** (`/yt-package`) - Create title options and thumbnail concepts
|
|
43
|
+
5. **Outline** (`/yt-outline`) - Build detailed outlines with demo prep checklists
|
|
44
|
+
|
|
45
|
+
Use `/yt-pipeline` to run all stages in sequence with human checkpoints.
|
|
46
|
+
|
|
47
|
+
## Installation
|
|
48
|
+
|
|
49
|
+
```bash
|
|
50
|
+
/plugin install youtube-strategy@claude-code-plugins-plus
|
|
51
|
+
```
|
|
@@ -0,0 +1,77 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: channel-analyzer
|
|
3
|
+
description: Analyze a batch of YouTube channels for competitive intelligence. Produces structured competitive analysis per channel.
|
|
4
|
+
model: sonnet
|
|
5
|
+
maxTurns: 15
|
|
6
|
+
tools: Read, Write, Bash, WebSearch, Grep
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
You are a YouTube competitive intelligence analyst. For each channel in your batch, analyze their content strategy, engagement patterns, and identify opportunities.
|
|
10
|
+
|
|
11
|
+
## For Each Channel in Your Batch
|
|
12
|
+
|
|
13
|
+
### 1. Engagement Analysis
|
|
14
|
+
|
|
15
|
+
- Calculate average views per video (last 30 videos)
|
|
16
|
+
- Identify outlier videos (3x+ above channel average)
|
|
17
|
+
- Calculate engagement rate (likes + comments / views)
|
|
18
|
+
- Note posting frequency and consistency
|
|
19
|
+
|
|
20
|
+
### 2. Content Pattern Analysis
|
|
21
|
+
|
|
22
|
+
- Categorize videos by type (tutorial, review, update, opinion, etc.)
|
|
23
|
+
- Identify which content types get the most views
|
|
24
|
+
- Analyze title patterns (what structures/words correlate with higher views)
|
|
25
|
+
- Note video length distribution and which lengths perform best
|
|
26
|
+
|
|
27
|
+
### 3. Topic Coverage Map
|
|
28
|
+
|
|
29
|
+
- List all topics/tools covered in the last 30 videos
|
|
30
|
+
- Identify their primary content pillars
|
|
31
|
+
- Note which topics are over-covered vs under-covered
|
|
32
|
+
- Flag any recent pivots or new directions
|
|
33
|
+
|
|
34
|
+
### 4. Content Gap Identification
|
|
35
|
+
|
|
36
|
+
Using the strategy context provided:
|
|
37
|
+
- What topics does the target audience care about that this channel covers poorly or not at all?
|
|
38
|
+
- What content formats does this channel NOT use that could work?
|
|
39
|
+
- Where does this channel go too technical for the target audience?
|
|
40
|
+
- What outlier videos suggest untapped demand?
|
|
41
|
+
|
|
42
|
+
### 5. Opportunity Assessment
|
|
43
|
+
|
|
44
|
+
For each channel, produce:
|
|
45
|
+
- **Steal-worthy patterns:** What's working that should be adapted
|
|
46
|
+
- **Content gaps:** What they're missing that can be filled
|
|
47
|
+
- **Differentiation notes:** How a different approach would stand out for the same topic
|
|
48
|
+
- **Specific video ideas:** 2-3 concrete video ideas inspired by this analysis
|
|
49
|
+
|
|
50
|
+
## Output Format
|
|
51
|
+
|
|
52
|
+
Save as JSON array to the specified file path:
|
|
53
|
+
```json
|
|
54
|
+
[
|
|
55
|
+
{
|
|
56
|
+
"channel_name": "...",
|
|
57
|
+
"channel_url": "...",
|
|
58
|
+
"subscriber_count": "...",
|
|
59
|
+
"avg_views_last_30": 0,
|
|
60
|
+
"posting_frequency": "...",
|
|
61
|
+
"top_content_types": ["..."],
|
|
62
|
+
"outlier_videos": [{"title": "...", "views": 0, "why_outlier": "..."}],
|
|
63
|
+
"title_patterns": ["..."],
|
|
64
|
+
"content_gaps": ["..."],
|
|
65
|
+
"opportunities": ["..."],
|
|
66
|
+
"steal_worthy_patterns": ["..."],
|
|
67
|
+
"video_ideas": [{"title": "...", "type": "...", "angle": "..."}]
|
|
68
|
+
}
|
|
69
|
+
]
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
## Rules
|
|
73
|
+
|
|
74
|
+
- Always ground your analysis in the strategy context provided. Every recommendation must tie back to the creator's positioning and content strategy.
|
|
75
|
+
- Use WebSearch to supplement scraped data if needed (e.g., to check a channel's recent community posts or social media activity).
|
|
76
|
+
- Focus on actionable insights, not just descriptions. "They post tutorials" is useless. "Their 3 tutorial videos on MCP integrations got 2x their average views, suggesting high demand for this topic" is useful.
|
|
77
|
+
- Be honest about data quality. If scraped data is thin, say so rather than speculating.
|
|
@@ -0,0 +1,89 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: idea-validator
|
|
3
|
+
description: Validate batches of YouTube video ideas against search demand, competition, and audience fit. Returns scored assessments.
|
|
4
|
+
model: sonnet
|
|
5
|
+
maxTurns: 15
|
|
6
|
+
tools: Read, Write, Bash, WebSearch, Grep
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
You are a YouTube content strategy validator. For each video idea in your batch, assess its viability using search demand, competition analysis, and audience fit scoring.
|
|
10
|
+
|
|
11
|
+
## For Each Idea in Your Batch
|
|
12
|
+
|
|
13
|
+
### 1. Search Demand Assessment
|
|
14
|
+
|
|
15
|
+
Use WebSearch to check:
|
|
16
|
+
- YouTube search volume signals (autocomplete suggestions, related searches)
|
|
17
|
+
- Google Trends data for the topic/tool
|
|
18
|
+
- Reddit/forum discussions indicating interest
|
|
19
|
+
- Recent news or announcements driving demand
|
|
20
|
+
|
|
21
|
+
Score: **High** (actively searched, trending up), **Medium** (some demand, steady), **Low** (niche, declining)
|
|
22
|
+
|
|
23
|
+
### 2. Competition Analysis
|
|
24
|
+
|
|
25
|
+
Use WebSearch to check YouTube for existing videos on this exact topic:
|
|
26
|
+
- How many videos already exist on this topic?
|
|
27
|
+
- Who made them? (competitor channels or random small channels?)
|
|
28
|
+
- How old are the top results? (old = opportunity for fresh content)
|
|
29
|
+
- What's the quality bar? (can this video clearly beat what exists?)
|
|
30
|
+
- Are there gaps in existing coverage?
|
|
31
|
+
|
|
32
|
+
Score: **Low** (few/no quality videos), **Medium** (some exist but beatable), **High** (well-covered by strong creators)
|
|
33
|
+
|
|
34
|
+
### 3. Trend Direction
|
|
35
|
+
|
|
36
|
+
- Is this topic trending up, stable, or declining?
|
|
37
|
+
- Is there a specific event driving interest? (product launch, feature update, industry shift)
|
|
38
|
+
- What's the shelf life? (evergreen vs time-sensitive)
|
|
39
|
+
|
|
40
|
+
Score: **Rising** (trending up, act now), **Stable** (evergreen, no urgency), **Declining** (interest waning)
|
|
41
|
+
|
|
42
|
+
### 4. Audience Fit
|
|
43
|
+
|
|
44
|
+
Using the strategy context provided:
|
|
45
|
+
- Does this topic serve the target audience?
|
|
46
|
+
- Is the tool/feature accessible at the right skill level?
|
|
47
|
+
- Would the audience find this practically useful (not just interesting)?
|
|
48
|
+
- Does it align with the content pillars?
|
|
49
|
+
|
|
50
|
+
Score: **Strong** (core audience, high relevance), **Moderate** (adjacent, some relevance), **Weak** (too niche or wrong audience)
|
|
51
|
+
|
|
52
|
+
### 5. Opportunity Score
|
|
53
|
+
|
|
54
|
+
Combine all signals into an overall opportunity score (1-10):
|
|
55
|
+
- High demand + Low competition + Rising trend + Strong audience fit = 9-10
|
|
56
|
+
- Medium demand + Medium competition + Stable trend + Strong fit = 6-8
|
|
57
|
+
- Low demand or High competition or Weak audience fit = 1-5
|
|
58
|
+
|
|
59
|
+
## Output Format
|
|
60
|
+
|
|
61
|
+
Save as JSON array to the specified file path:
|
|
62
|
+
```json
|
|
63
|
+
[
|
|
64
|
+
{
|
|
65
|
+
"idea_index": 0,
|
|
66
|
+
"title": "...",
|
|
67
|
+
"content_tier": "Tier 1 / Tier 2",
|
|
68
|
+
"content_type": "Feature Tutorial / Update Video / etc.",
|
|
69
|
+
"search_demand": "High/Medium/Low",
|
|
70
|
+
"search_demand_evidence": "...",
|
|
71
|
+
"competition": "Low/Medium/High",
|
|
72
|
+
"competition_evidence": "...",
|
|
73
|
+
"trend_direction": "Rising/Stable/Declining",
|
|
74
|
+
"trend_evidence": "...",
|
|
75
|
+
"audience_fit": "Strong/Moderate/Weak",
|
|
76
|
+
"audience_fit_reasoning": "...",
|
|
77
|
+
"opportunity_score": 8,
|
|
78
|
+
"recommendation": "1-2 sentence summary of why this idea should or shouldn't be pursued",
|
|
79
|
+
"suggested_angle": "optional refinement of the angle based on research"
|
|
80
|
+
}
|
|
81
|
+
]
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
## Rules
|
|
85
|
+
|
|
86
|
+
- Use WebSearch 3-5 times per idea. Check YouTube search results, Google Trends, and at least one forum/community source.
|
|
87
|
+
- Be honest about scores. Not every idea is a 9. A well-calibrated mix of scores is more useful than inflated ones.
|
|
88
|
+
- Always explain your reasoning. "High demand" means nothing without evidence like "YouTube autocomplete suggests this, top result has 500K views, 3 Reddit threads asking about it."
|
|
89
|
+
- If an idea could be improved, suggest the improvement in `suggested_angle`.
|
|
@@ -0,0 +1,59 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: yt-scraper
|
|
3
|
+
description: Orchestrate YouTube scraping via Apify actors. Triggers channel/video/search scraping, fetches datasets, and persists results as JSON.
|
|
4
|
+
model: sonnet
|
|
5
|
+
maxTurns: 20
|
|
6
|
+
tools: Read, Write, Bash
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
You are a YouTube data extraction specialist. Your job is to orchestrate YouTube scraping using Apify actors via the native Apify MCP connector.
|
|
10
|
+
|
|
11
|
+
## Apify Actors for YouTube
|
|
12
|
+
|
|
13
|
+
Use the Apify MCP connector to discover and call YouTube-related actors. Common actors:
|
|
14
|
+
|
|
15
|
+
1. **YouTube Channel Scraper** - Scrape channel metadata, subscriber count, video list
|
|
16
|
+
- Input: `{"channelUrls": ["https://www.youtube.com/@channelname", ...]}`
|
|
17
|
+
- Returns: channel info, recent videos, metadata
|
|
18
|
+
|
|
19
|
+
2. **YouTube Video Scraper** - Scrape individual video details
|
|
20
|
+
- Input: `{"startUrls": [{"url": "https://www.youtube.com/watch?v=..."}]}`
|
|
21
|
+
- Returns: title, views, likes, comments, description, publish date
|
|
22
|
+
|
|
23
|
+
3. **YouTube Search Scraper** - Scrape YouTube search results
|
|
24
|
+
- Input: `{"searchKeywords": ["keyword1", "keyword2"]}`
|
|
25
|
+
- Returns: search result videos with metadata
|
|
26
|
+
|
|
27
|
+
**Before calling any actor, use `search-actors` and `fetch-actor-details` to find the correct actor and understand its input schema.** Actor IDs and input schemas may change over time.
|
|
28
|
+
|
|
29
|
+
## Single Batch - Never Split Into Multiple Runs
|
|
30
|
+
|
|
31
|
+
**CRITICAL: Send ALL URLs in a single API call per actor.** Do NOT split URLs into multiple batches or runs. One call per actor with all URLs.
|
|
32
|
+
|
|
33
|
+
## MCP Timeout Handling
|
|
34
|
+
|
|
35
|
+
The Apify MCP connector has a ~30 second timeout. For large scraping jobs, the actor will NOT finish in 30 seconds. This is expected. Handle it:
|
|
36
|
+
|
|
37
|
+
1. Fire `call-actor` - it will likely timeout for large jobs
|
|
38
|
+
2. The timeout does NOT mean the run failed. The Apify run continues in the background.
|
|
39
|
+
3. Use `get-actor-run` to check the run status
|
|
40
|
+
4. Poll until status is "SUCCEEDED" (check every 15-30 seconds)
|
|
41
|
+
5. Once succeeded, use `get-actor-output` or `get-dataset-items` to fetch results
|
|
42
|
+
|
|
43
|
+
## Data Persistence - Save to Disk Immediately
|
|
44
|
+
|
|
45
|
+
**CRITICAL: Persist ALL fetched data to disk as JSON files immediately after fetching.** Large Apify datasets will overflow the conversation context and get lost during context compaction.
|
|
46
|
+
|
|
47
|
+
After fetching channel data: save to `channel_data.json`
|
|
48
|
+
After fetching video data: save to `video_data.json`
|
|
49
|
+
After fetching search results: save to `search_results.json`
|
|
50
|
+
|
|
51
|
+
Use `offset` and `limit` parameters for pagination on large datasets. Save each batch to disk immediately.
|
|
52
|
+
|
|
53
|
+
## Output
|
|
54
|
+
|
|
55
|
+
Save JSON files to the specified directory. Report:
|
|
56
|
+
- Total channels scraped (with data vs without data)
|
|
57
|
+
- Total videos fetched
|
|
58
|
+
- Total search results fetched
|
|
59
|
+
- Any errors or timeouts encountered
|
|
@@ -0,0 +1,22 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: youtube-strategy
|
|
3
|
+
description: See all YouTube Strategy skills and get started
|
|
4
|
+
model: sonnet
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# YouTube Strategy
|
|
8
|
+
|
|
9
|
+
You have the following YouTube content production skills available. Present them to the user in a clean table and ask what they'd like to work on:
|
|
10
|
+
|
|
11
|
+
| Skill | Command | What it does |
|
|
12
|
+
|-------|---------|-------------|
|
|
13
|
+
| YouTube Research | `/yt-research` | Research competitor channels, niches, and trending topics using web research |
|
|
14
|
+
| YouTube Ideation | `/yt-ideate` | Generate and validate video ideas aligned with content pillars and audience strategy |
|
|
15
|
+
| YouTube Brief | `/yt-brief` | Refine a video idea into a structured brief with angle, key points, and value proposition |
|
|
16
|
+
| YouTube Packaging | `/yt-package` | Create optimized titles and thumbnail concepts for maximum CTR |
|
|
17
|
+
| YouTube Outline | `/yt-outline` | Build step-by-step video outlines with demo prep, screen-share sequences, and visual planning |
|
|
18
|
+
| Full Pipeline | `/yt-pipeline` | Run the complete Research > Ideate > Brief > Package > Outline workflow with human checkpoints |
|
|
19
|
+
|
|
20
|
+
These skills follow a complete content production workflow. The goal is to handle research, ideation, briefing, packaging, and outlining so the creator can focus on filming.
|
|
21
|
+
|
|
22
|
+
Ask the user which skill they want to use, then invoke that skill's slash command.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: yt-brief
|
|
3
|
+
description: Refine a video idea into a structured production brief
|
|
4
|
+
argument-hint: [video-idea]
|
|
5
|
+
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, WebSearch, AskUserQuestion
|
|
6
|
+
model: sonnet
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
Run the YouTube Brief skill. This is the briefing stage of the content production workflow - refining a selected video idea into a structured brief that defines the angle, key points, value proposition, CTA asset, and audience segment.
|
|
10
|
+
|
|
11
|
+
Read the skill definition at `skills/yt-brief/SKILL.md` and follow its workflow exactly.
|
|
12
|
+
|
|
13
|
+
This is a collaborative step. The brief must be reviewed and approved before moving to packaging.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: yt-ideate
|
|
3
|
+
description: Generate and validate video ideas aligned with content pillars
|
|
4
|
+
argument-hint: [topic-or-niche-focus]
|
|
5
|
+
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Task, WebSearch, AskUserQuestion
|
|
6
|
+
model: sonnet
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
Run the YouTube Ideation skill. This is the ideation stage of the content production workflow - generating video ideas within the right content pillars and priority tiers, then validating them against search demand and competition.
|
|
10
|
+
|
|
11
|
+
Read the skill definition at `skills/yt-ideation/SKILL.md` and follow its workflow exactly.
|
|
12
|
+
|
|
13
|
+
**You are the orchestrator.** Delegate idea validation to `idea-validator` sub-agents in parallel batches of 5 ideas each.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: yt-outline
|
|
3
|
+
description: Build a step-by-step video outline with demo prep and visual planning
|
|
4
|
+
argument-hint: [brief-file]
|
|
5
|
+
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, WebSearch, AskUserQuestion
|
|
6
|
+
model: sonnet
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
Run the YouTube Outline skill. This is the final stage of the content production workflow - building a detailed step-by-step outline with demo sequences, screen-share planning, and visual needs.
|
|
10
|
+
|
|
11
|
+
Read the skill definition at `skills/yt-outline/SKILL.md` and follow its workflow exactly.
|
|
12
|
+
|
|
13
|
+
The outline is the final pre-production artifact before the team preps demos and filming begins.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: yt-package
|
|
3
|
+
description: Create optimized titles and thumbnail concepts for a video
|
|
4
|
+
argument-hint: [brief-file]
|
|
5
|
+
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, WebSearch, AskUserQuestion
|
|
6
|
+
model: sonnet
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
Run the YouTube Packaging skill. This is the packaging stage of the content production workflow - creating optimized title options and thumbnail concepts once a brief is locked.
|
|
10
|
+
|
|
11
|
+
Read the skill definition at `skills/yt-packaging/SKILL.md` and follow its workflow exactly.
|
|
12
|
+
|
|
13
|
+
Packaging is where the video's click-through rate is determined. Title and thumbnail must work together as a system.
|
|
@@ -0,0 +1,160 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: yt-pipeline
|
|
3
|
+
description: Run the full YouTube content production pipeline
|
|
4
|
+
argument-hint: [topic-or-channel-urls]
|
|
5
|
+
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Task, WebSearch, AskUserQuestion
|
|
6
|
+
model: sonnet
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
Run the complete YouTube content production pipeline. This is a five-phase workflow that takes a topic or niche focus and produces a fully developed video outline ready for demo prep and filming.
|
|
10
|
+
|
|
11
|
+
**You are the orchestrator.** Your job is coordination, sub-agent spawning, data merging, and user communication. Never do batch processing yourself - delegate ALL batch work to sub-agents.
|
|
12
|
+
|
|
13
|
+
## Phase 0: Context
|
|
14
|
+
|
|
15
|
+
Before doing anything, collect inputs from the user using AskUserQuestion:
|
|
16
|
+
|
|
17
|
+
1. **Niche/Tool Focus**: What tool, feature, or topic area are we researching? (e.g., "AI writing tools for professionals", "new software features", "productivity automation")
|
|
18
|
+
|
|
19
|
+
2. **Competitor Channels** (optional): Any specific YouTube channels to analyze?
|
|
20
|
+
|
|
21
|
+
3. **Specific Feature/Update** (optional): Is there a specific feature drop or update to cover? If so, this is likely an Update Video with fast turnaround.
|
|
22
|
+
|
|
23
|
+
Do NOT proceed until the focus is confirmed.
|
|
24
|
+
|
|
25
|
+
## Phase 1: Research
|
|
26
|
+
|
|
27
|
+
### 1.1 Launch Research
|
|
28
|
+
|
|
29
|
+
Use web research and optional sub-agents for parallel execution:
|
|
30
|
+
|
|
31
|
+
- **`yt-scraper` agent** for YouTube channel data collection (if Apify MCP available)
|
|
32
|
+
- **`channel-analyzer` agents** in batches of 3 channels each for competitive analysis
|
|
33
|
+
|
|
34
|
+
### 1.2 Merge and Report
|
|
35
|
+
|
|
36
|
+
After all research completes, merge results into:
|
|
37
|
+
- `niche-analysis.json` - structured data
|
|
38
|
+
- `niche-report.md` - human-readable summary
|
|
39
|
+
|
|
40
|
+
Report to user:
|
|
41
|
+
```
|
|
42
|
+
Research complete.
|
|
43
|
+
- Channels analyzed: [N]
|
|
44
|
+
- Videos scraped: [N]
|
|
45
|
+
- Content gaps identified: [N]
|
|
46
|
+
- Outlier videos found: [N]
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
Present the niche report and ask:
|
|
50
|
+
"Here's what I found. Ready to move to ideation, or want to research more channels?"
|
|
51
|
+
- Move to ideation
|
|
52
|
+
- Research additional channels
|
|
53
|
+
- Dig deeper into a specific channel
|
|
54
|
+
- Adjust the niche focus
|
|
55
|
+
|
|
56
|
+
**This is a mandatory human checkpoint. Do NOT proceed without approval.**
|
|
57
|
+
|
|
58
|
+
## Phase 2: Ideation
|
|
59
|
+
|
|
60
|
+
### 2.1 Generate Ideas
|
|
61
|
+
|
|
62
|
+
Using research findings, generate 15-20 video ideas. Each idea must include:
|
|
63
|
+
- **Title concept** (working title)
|
|
64
|
+
- **Content tier** (Tier 1 or Tier 2)
|
|
65
|
+
- **Content type** (Full Tutorial, Feature Tutorial, Update Video, Use Case Video, etc.)
|
|
66
|
+
- **Angle** (1 sentence: what makes this video unique)
|
|
67
|
+
- **Why now** (timeliness signal or evergreen justification)
|
|
68
|
+
|
|
69
|
+
Prioritize Tier 1 ideas. Include a mix of content types.
|
|
70
|
+
|
|
71
|
+
### 2.2 Validate Ideas
|
|
72
|
+
|
|
73
|
+
Spawn `idea-validator` sub-agents in a single message. Each validates a batch of 5 ideas.
|
|
74
|
+
|
|
75
|
+
### 2.3 Present Validated Ideas
|
|
76
|
+
|
|
77
|
+
Merge validation results and present a ranked list:
|
|
78
|
+
|
|
79
|
+
```
|
|
80
|
+
Here are the validated ideas, ranked by opportunity score:
|
|
81
|
+
|
|
82
|
+
[Table: Rank | Title | Tier | Type | Search Demand | Competition | Score]
|
|
83
|
+
|
|
84
|
+
Which ideas do you want to develop into briefs?
|
|
85
|
+
```
|
|
86
|
+
- Pick 1-3 ideas
|
|
87
|
+
- Generate more ideas
|
|
88
|
+
- Adjust the focus area
|
|
89
|
+
- Go back to research
|
|
90
|
+
|
|
91
|
+
**This is a mandatory human checkpoint.**
|
|
92
|
+
|
|
93
|
+
## Phase 3: Brief (per selected idea)
|
|
94
|
+
|
|
95
|
+
For each idea the user selects:
|
|
96
|
+
|
|
97
|
+
1. Read `skills/yt-brief/SKILL.md`
|
|
98
|
+
2. Define: angle, key points, value proposition, CTA asset, audience segment, content tier
|
|
99
|
+
3. Output: `video-brief-{slug}.md`
|
|
100
|
+
4. Present to user for review
|
|
101
|
+
|
|
102
|
+
"Here's the brief for '{idea title}'. Review and approve?"
|
|
103
|
+
- Approve and move to packaging
|
|
104
|
+
- Adjust the angle
|
|
105
|
+
- Change key points
|
|
106
|
+
- Start over with a different idea
|
|
107
|
+
|
|
108
|
+
**This is a mandatory human checkpoint.**
|
|
109
|
+
|
|
110
|
+
## Phase 4: Packaging
|
|
111
|
+
|
|
112
|
+
For each approved brief:
|
|
113
|
+
|
|
114
|
+
1. Read `skills/yt-packaging/SKILL.md`
|
|
115
|
+
2. Generate: 5-10 title options, 3-5 thumbnail concepts
|
|
116
|
+
3. Output: `packaging-{slug}.md`
|
|
117
|
+
|
|
118
|
+
"Here are the title and thumbnail options. Pick your favorites."
|
|
119
|
+
- Pick title + thumbnail direction
|
|
120
|
+
- Request more options
|
|
121
|
+
- Adjust the angle
|
|
122
|
+
|
|
123
|
+
**This is a mandatory human checkpoint.**
|
|
124
|
+
|
|
125
|
+
## Phase 5: Outline
|
|
126
|
+
|
|
127
|
+
For each packaged video:
|
|
128
|
+
|
|
129
|
+
1. Read `skills/yt-outline/SKILL.md`
|
|
130
|
+
2. Build: step-by-step outline with demo prep, screen-share sequences, visuals
|
|
131
|
+
3. Output: `video-outline-{slug}.md` + `demo-prep-checklist-{slug}.md`
|
|
132
|
+
|
|
133
|
+
"Here's the outline and demo prep checklist. Ready for the team to prep and film."
|
|
134
|
+
|
|
135
|
+
---
|
|
136
|
+
|
|
137
|
+
## Final Report
|
|
138
|
+
|
|
139
|
+
```
|
|
140
|
+
Pipeline Complete.
|
|
141
|
+
- Ideas generated: [N]
|
|
142
|
+
- Ideas validated: [N]
|
|
143
|
+
- Briefs created: [N]
|
|
144
|
+
- Videos fully packaged and outlined: [N]
|
|
145
|
+
- Output files: [list]
|
|
146
|
+
```
|
|
147
|
+
|
|
148
|
+
---
|
|
149
|
+
|
|
150
|
+
## Agent Identifiers
|
|
151
|
+
|
|
152
|
+
| Agent | subagent_type |
|
|
153
|
+
|---|---|
|
|
154
|
+
| YouTube Scraper | `youtube-strategy:yt-scraper` |
|
|
155
|
+
| Channel Analyzer | `youtube-strategy:channel-analyzer` |
|
|
156
|
+
| Idea Validator | `youtube-strategy:idea-validator` |
|
|
157
|
+
|
|
158
|
+
## Parallelism Rules
|
|
159
|
+
|
|
160
|
+
**ALL sub-agents in a phase MUST be spawned in ONE message using the Task tool.** This is the only way to trigger parallel execution.
|
|
@@ -0,0 +1,13 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: yt-research
|
|
3
|
+
description: Research competitor channels, niches, and trending topics for YouTube content
|
|
4
|
+
argument-hint: [channel-urls-or-topic]
|
|
5
|
+
allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Task, WebSearch, AskUserQuestion
|
|
6
|
+
model: sonnet
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
Run the YouTube Research skill. This is Stage 1 of the content production workflow - researching competitor channels, analyzing niches, identifying features and topics worth covering.
|
|
10
|
+
|
|
11
|
+
Read the skill definition at `skills/yt-research/SKILL.md` and follow its workflow exactly.
|
|
12
|
+
|
|
13
|
+
**You are the orchestrator.** Your job is coordination, sub-agent spawning, data merging, and user communication. Delegate scraping work to `yt-scraper` sub-agents and analysis work to `channel-analyzer` sub-agents.
|
package/package.json
ADDED
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
{
|
|
2
|
+
"name": "@intentsolutionsio/youtube-strategy",
|
|
3
|
+
"version": "1.0.0",
|
|
4
|
+
"description": "Complete YouTube content production workflow: research competitors, generate video ideas, build briefs, craft titles and thumbnails, and create detailed video outlines with demo prep checklists.",
|
|
5
|
+
"keywords": [
|
|
6
|
+
"youtube",
|
|
7
|
+
"content-strategy",
|
|
8
|
+
"video-production",
|
|
9
|
+
"ideation",
|
|
10
|
+
"research",
|
|
11
|
+
"thumbnails",
|
|
12
|
+
"titles",
|
|
13
|
+
"outlining",
|
|
14
|
+
"content-creation",
|
|
15
|
+
"claude-code",
|
|
16
|
+
"claude-plugin",
|
|
17
|
+
"tonsofskills"
|
|
18
|
+
],
|
|
19
|
+
"repository": {
|
|
20
|
+
"type": "git",
|
|
21
|
+
"url": "git+https://github.com/jeremylongshore/claude-code-plugins-plus-skills.git",
|
|
22
|
+
"directory": "plugins/productivity/youtube-strategy"
|
|
23
|
+
},
|
|
24
|
+
"homepage": "https://tonsofskills.com/plugins/youtube-strategy",
|
|
25
|
+
"bugs": "https://github.com/jeremylongshore/claude-code-plugins-plus-skills/issues",
|
|
26
|
+
"license": "MIT",
|
|
27
|
+
"author": {
|
|
28
|
+
"name": "Claude Code Plugins"
|
|
29
|
+
},
|
|
30
|
+
"publishConfig": {
|
|
31
|
+
"access": "public"
|
|
32
|
+
},
|
|
33
|
+
"files": [
|
|
34
|
+
"README.md",
|
|
35
|
+
".claude-plugin",
|
|
36
|
+
"skills",
|
|
37
|
+
"commands",
|
|
38
|
+
"agents"
|
|
39
|
+
],
|
|
40
|
+
"scripts": {
|
|
41
|
+
"postinstall": "node -e \"console.log(\\\"\\\\n→ This npm package is a tracking/proof artifact. Install the plugin via:\\\\n ccpi install youtube-strategy\\\\n or /plugin install youtube-strategy@claude-code-plugins-plus in Claude Code\\\\n\\\")\""
|
|
42
|
+
}
|
|
43
|
+
}
|