@intentsolutionsio/youtube-strategy 1.0.0 → 1.0.1
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/agents/channel-analyzer.md +3 -0
- package/agents/idea-validator.md +5 -0
- package/agents/yt-scraper.md +1 -0
- package/commands/yt-pipeline.md +7 -0
- package/package.json +1 -1
- package/skills/yt-brief/SKILL.md +23 -8
- package/skills/yt-ideation/SKILL.md +28 -8
- package/skills/yt-outline/SKILL.md +30 -8
- package/skills/yt-packaging/SKILL.md +28 -8
- package/skills/yt-research/SKILL.md +26 -8
|
@@ -34,6 +34,7 @@ You are a YouTube competitive intelligence analyst. For each channel in your bat
|
|
|
34
34
|
### 4. Content Gap Identification
|
|
35
35
|
|
|
36
36
|
Using the strategy context provided:
|
|
37
|
+
|
|
37
38
|
- What topics does the target audience care about that this channel covers poorly or not at all?
|
|
38
39
|
- What content formats does this channel NOT use that could work?
|
|
39
40
|
- Where does this channel go too technical for the target audience?
|
|
@@ -42,6 +43,7 @@ Using the strategy context provided:
|
|
|
42
43
|
### 5. Opportunity Assessment
|
|
43
44
|
|
|
44
45
|
For each channel, produce:
|
|
46
|
+
|
|
45
47
|
- **Steal-worthy patterns:** What's working that should be adapted
|
|
46
48
|
- **Content gaps:** What they're missing that can be filled
|
|
47
49
|
- **Differentiation notes:** How a different approach would stand out for the same topic
|
|
@@ -50,6 +52,7 @@ For each channel, produce:
|
|
|
50
52
|
## Output Format
|
|
51
53
|
|
|
52
54
|
Save as JSON array to the specified file path:
|
|
55
|
+
|
|
53
56
|
```json
|
|
54
57
|
[
|
|
55
58
|
{
|
package/agents/idea-validator.md
CHANGED
|
@@ -13,6 +13,7 @@ You are a YouTube content strategy validator. For each video idea in your batch,
|
|
|
13
13
|
### 1. Search Demand Assessment
|
|
14
14
|
|
|
15
15
|
Use WebSearch to check:
|
|
16
|
+
|
|
16
17
|
- YouTube search volume signals (autocomplete suggestions, related searches)
|
|
17
18
|
- Google Trends data for the topic/tool
|
|
18
19
|
- Reddit/forum discussions indicating interest
|
|
@@ -23,6 +24,7 @@ Score: **High** (actively searched, trending up), **Medium** (some demand, stead
|
|
|
23
24
|
### 2. Competition Analysis
|
|
24
25
|
|
|
25
26
|
Use WebSearch to check YouTube for existing videos on this exact topic:
|
|
27
|
+
|
|
26
28
|
- How many videos already exist on this topic?
|
|
27
29
|
- Who made them? (competitor channels or random small channels?)
|
|
28
30
|
- How old are the top results? (old = opportunity for fresh content)
|
|
@@ -42,6 +44,7 @@ Score: **Rising** (trending up, act now), **Stable** (evergreen, no urgency), **
|
|
|
42
44
|
### 4. Audience Fit
|
|
43
45
|
|
|
44
46
|
Using the strategy context provided:
|
|
47
|
+
|
|
45
48
|
- Does this topic serve the target audience?
|
|
46
49
|
- Is the tool/feature accessible at the right skill level?
|
|
47
50
|
- Would the audience find this practically useful (not just interesting)?
|
|
@@ -52,6 +55,7 @@ Score: **Strong** (core audience, high relevance), **Moderate** (adjacent, some
|
|
|
52
55
|
### 5. Opportunity Score
|
|
53
56
|
|
|
54
57
|
Combine all signals into an overall opportunity score (1-10):
|
|
58
|
+
|
|
55
59
|
- High demand + Low competition + Rising trend + Strong audience fit = 9-10
|
|
56
60
|
- Medium demand + Medium competition + Stable trend + Strong fit = 6-8
|
|
57
61
|
- Low demand or High competition or Weak audience fit = 1-5
|
|
@@ -59,6 +63,7 @@ Combine all signals into an overall opportunity score (1-10):
|
|
|
59
63
|
## Output Format
|
|
60
64
|
|
|
61
65
|
Save as JSON array to the specified file path:
|
|
66
|
+
|
|
62
67
|
```json
|
|
63
68
|
[
|
|
64
69
|
{
|
package/agents/yt-scraper.md
CHANGED
|
@@ -53,6 +53,7 @@ Use `offset` and `limit` parameters for pagination on large datasets. Save each
|
|
|
53
53
|
## Output
|
|
54
54
|
|
|
55
55
|
Save JSON files to the specified directory. Report:
|
|
56
|
+
|
|
56
57
|
- Total channels scraped (with data vs without data)
|
|
57
58
|
- Total videos fetched
|
|
58
59
|
- Total search results fetched
|
package/commands/yt-pipeline.md
CHANGED
|
@@ -34,10 +34,12 @@ Use web research and optional sub-agents for parallel execution:
|
|
|
34
34
|
### 1.2 Merge and Report
|
|
35
35
|
|
|
36
36
|
After all research completes, merge results into:
|
|
37
|
+
|
|
37
38
|
- `niche-analysis.json` - structured data
|
|
38
39
|
- `niche-report.md` - human-readable summary
|
|
39
40
|
|
|
40
41
|
Report to user:
|
|
42
|
+
|
|
41
43
|
```
|
|
42
44
|
Research complete.
|
|
43
45
|
- Channels analyzed: [N]
|
|
@@ -48,6 +50,7 @@ Research complete.
|
|
|
48
50
|
|
|
49
51
|
Present the niche report and ask:
|
|
50
52
|
"Here's what I found. Ready to move to ideation, or want to research more channels?"
|
|
53
|
+
|
|
51
54
|
- Move to ideation
|
|
52
55
|
- Research additional channels
|
|
53
56
|
- Dig deeper into a specific channel
|
|
@@ -60,6 +63,7 @@ Present the niche report and ask:
|
|
|
60
63
|
### 2.1 Generate Ideas
|
|
61
64
|
|
|
62
65
|
Using research findings, generate 15-20 video ideas. Each idea must include:
|
|
66
|
+
|
|
63
67
|
- **Title concept** (working title)
|
|
64
68
|
- **Content tier** (Tier 1 or Tier 2)
|
|
65
69
|
- **Content type** (Full Tutorial, Feature Tutorial, Update Video, Use Case Video, etc.)
|
|
@@ -83,6 +87,7 @@ Here are the validated ideas, ranked by opportunity score:
|
|
|
83
87
|
|
|
84
88
|
Which ideas do you want to develop into briefs?
|
|
85
89
|
```
|
|
90
|
+
|
|
86
91
|
- Pick 1-3 ideas
|
|
87
92
|
- Generate more ideas
|
|
88
93
|
- Adjust the focus area
|
|
@@ -100,6 +105,7 @@ For each idea the user selects:
|
|
|
100
105
|
4. Present to user for review
|
|
101
106
|
|
|
102
107
|
"Here's the brief for '{idea title}'. Review and approve?"
|
|
108
|
+
|
|
103
109
|
- Approve and move to packaging
|
|
104
110
|
- Adjust the angle
|
|
105
111
|
- Change key points
|
|
@@ -116,6 +122,7 @@ For each approved brief:
|
|
|
116
122
|
3. Output: `packaging-{slug}.md`
|
|
117
123
|
|
|
118
124
|
"Here are the title and thumbnail options. Pick your favorites."
|
|
125
|
+
|
|
119
126
|
- Pick title + thumbnail direction
|
|
120
127
|
- Request more options
|
|
121
128
|
- Adjust the angle
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@intentsolutionsio/youtube-strategy",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.1",
|
|
4
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
5
|
"keywords": [
|
|
6
6
|
"youtube",
|
package/skills/yt-brief/SKILL.md
CHANGED
|
@@ -1,16 +1,26 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: yt-brief
|
|
3
|
-
description:
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
3
|
+
description: 'Refine a YouTube video idea into a structured production brief with
|
|
4
|
+
angle, key points, value proposition,
|
|
5
|
+
|
|
6
|
+
CTA asset, and audience segment. Use this skill whenever the user says "create a
|
|
7
|
+
brief", "brief this idea",
|
|
8
|
+
|
|
9
|
+
"develop this idea", "write a video brief", "production brief", or has selected
|
|
10
|
+
a video idea from ideation
|
|
11
|
+
|
|
12
|
+
and wants to define the angle and structure before packaging and outlining. Use
|
|
13
|
+
when working with yt brief. Trigger with ''yt'', ''brief''.
|
|
14
|
+
|
|
15
|
+
'
|
|
8
16
|
allowed-tools: WebSearch, Read, Write
|
|
9
17
|
version: 1.0.0
|
|
10
18
|
author: Claude Code Plugins <plugins@claudecodeplugins.io>
|
|
11
19
|
license: MIT
|
|
12
|
-
|
|
13
|
-
|
|
20
|
+
tags:
|
|
21
|
+
- productivity
|
|
22
|
+
- yt-brief
|
|
23
|
+
compatibility: Designed for Claude Code, also compatible with Codex and OpenClaw
|
|
14
24
|
---
|
|
15
25
|
# YouTube Brief
|
|
16
26
|
|
|
@@ -30,6 +40,7 @@ If the user is coming from the ideation flow, load `validated_ideas.json` for th
|
|
|
30
40
|
### Step 1: Research the Topic
|
|
31
41
|
|
|
32
42
|
Before writing the brief, understand the topic deeply:
|
|
43
|
+
|
|
33
44
|
- What does this feature/tool actually do? (Use WebSearch if needed)
|
|
34
45
|
- What are the common pain points or confusion points?
|
|
35
46
|
- What existing content exists? What angle would differentiate this video?
|
|
@@ -40,16 +51,19 @@ Before writing the brief, understand the topic deeply:
|
|
|
40
51
|
Work with the user to lock in:
|
|
41
52
|
|
|
42
53
|
**Content Type & Tier:**
|
|
54
|
+
|
|
43
55
|
- Confirm which tier and category this falls under
|
|
44
56
|
- This determines the format, length, and production approach
|
|
45
57
|
|
|
46
58
|
**The Angle:**
|
|
59
|
+
|
|
47
60
|
- What's the unique take? Why would someone click THIS video over alternatives?
|
|
48
61
|
- The angle should be specific and defensible, not generic
|
|
49
62
|
- Good: "How to use MCP integrations to automate your marketing reporting without any code"
|
|
50
63
|
- Bad: "MCP tutorial"
|
|
51
64
|
|
|
52
65
|
**Target Audience Segment:**
|
|
66
|
+
|
|
53
67
|
- Who is the primary viewer?
|
|
54
68
|
- What's their starting knowledge level for this topic?
|
|
55
69
|
|
|
@@ -80,6 +94,7 @@ Present the complete brief and ask:
|
|
|
80
94
|
```
|
|
81
95
|
|
|
82
96
|
"What would you like to adjust?"
|
|
97
|
+
|
|
83
98
|
- Approve - move to packaging
|
|
84
99
|
- Adjust the angle
|
|
85
100
|
- Add/remove key points
|
|
@@ -143,4 +158,4 @@ Refine a YouTube video idea into a structured production brief with angle, key p
|
|
|
143
158
|
|
|
144
159
|
- Official Yt Brief documentation
|
|
145
160
|
- Community best practices and patterns
|
|
146
|
-
- Related skills in this plugin pack
|
|
161
|
+
- Related skills in this plugin pack
|
|
@@ -1,16 +1,26 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: yt-ideation
|
|
3
|
-
description:
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
3
|
+
description: 'Generate and validate YouTube video ideas aligned with content pillars,
|
|
4
|
+
audience strategy,
|
|
5
|
+
|
|
6
|
+
and priority tiers. Use this skill whenever the user says "generate ideas", "brainstorm
|
|
7
|
+
videos",
|
|
8
|
+
|
|
9
|
+
"what should I make next", "video ideas", "content ideas", "ideation", "what topics
|
|
10
|
+
should I cover",
|
|
11
|
+
|
|
12
|
+
or wants to come up with new video concepts. Use when working with yt ideation.
|
|
13
|
+
Trigger with ''yt'', ''ideation''.
|
|
14
|
+
|
|
15
|
+
'
|
|
8
16
|
allowed-tools: WebSearch, Read, Write, Task
|
|
9
17
|
version: 1.0.0
|
|
10
18
|
author: Claude Code Plugins <plugins@claudecodeplugins.io>
|
|
11
19
|
license: MIT
|
|
12
|
-
|
|
13
|
-
|
|
20
|
+
tags:
|
|
21
|
+
- productivity
|
|
22
|
+
- yt-ideation
|
|
23
|
+
compatibility: Designed for Claude Code, also compatible with Codex and OpenClaw
|
|
14
24
|
---
|
|
15
25
|
# YouTube Ideation
|
|
16
26
|
|
|
@@ -31,6 +41,7 @@ If the user provided focus already, confirm and proceed.
|
|
|
31
41
|
### Step 1: Load Context
|
|
32
42
|
|
|
33
43
|
Understand the creator's:
|
|
44
|
+
|
|
34
45
|
- **Content pillars** - What core topics does the channel focus on?
|
|
35
46
|
- **Audience** - Who are the viewers? What's their skill level?
|
|
36
47
|
- **Content types** - What formats work best? (tutorials, reviews, updates, comparisons)
|
|
@@ -41,26 +52,31 @@ Understand the creator's:
|
|
|
41
52
|
Use these ideation methods:
|
|
42
53
|
|
|
43
54
|
**Method 1: Gap Analysis** (if research data available)
|
|
55
|
+
|
|
44
56
|
- Content gaps from competitor analysis
|
|
45
57
|
- Topics with high demand but low competition
|
|
46
58
|
- Complex concepts that need accessible translation
|
|
47
59
|
|
|
48
60
|
**Method 2: Trend Riding**
|
|
61
|
+
|
|
49
62
|
- Recent tool updates or feature launches
|
|
50
63
|
- Industry developments relevant to the audience
|
|
51
64
|
- Viral topics that can be made practical
|
|
52
65
|
|
|
53
66
|
**Method 3: Format Innovation**
|
|
67
|
+
|
|
54
68
|
- Existing topics in new formats (comparison, mega-guide, use-case compilation)
|
|
55
69
|
- Content types competitors aren't using
|
|
56
70
|
- Series potential (multi-part tutorials)
|
|
57
71
|
|
|
58
72
|
**Method 4: Audience Needs**
|
|
73
|
+
|
|
59
74
|
- Questions the audience is asking (Reddit, YouTube comments, community)
|
|
60
75
|
- Problems viewers face with the tools they use
|
|
61
76
|
- "How do I..." queries for the niche
|
|
62
77
|
|
|
63
78
|
For each idea, define:
|
|
79
|
+
|
|
64
80
|
- **Working title**
|
|
65
81
|
- **Content tier** (Tier 1: growth content, Tier 2: supporting content)
|
|
66
82
|
- **Content type** (Full Tutorial, Feature Tutorial, Update Video, Use Case Video, Comparison, etc.)
|
|
@@ -68,12 +84,14 @@ For each idea, define:
|
|
|
68
84
|
- **Timeliness** (trending/urgent or evergreen)
|
|
69
85
|
|
|
70
86
|
**Priority distribution:**
|
|
87
|
+
|
|
71
88
|
- 60-70% Tier 1 ideas (the growth engine)
|
|
72
89
|
- 30-40% Tier 2 ideas (supporting content)
|
|
73
90
|
|
|
74
91
|
### Step 3: Quick Self-Filter
|
|
75
92
|
|
|
76
93
|
Before validation, run each idea through a strategy test:
|
|
94
|
+
|
|
77
95
|
- Does it serve the target audience? (Must be yes)
|
|
78
96
|
- Can it be practically demonstrated? (Prefer yes)
|
|
79
97
|
- Does it support the content funnel? (Can we give away an asset?)
|
|
@@ -84,6 +102,7 @@ Remove ideas that fail the test. Note why for transparency.
|
|
|
84
102
|
### Step 4: Validate Ideas
|
|
85
103
|
|
|
86
104
|
Spawn `idea-validator` sub-agents (5 ideas per agent) to assess:
|
|
105
|
+
|
|
87
106
|
- Search demand (YouTube autocomplete, Google Trends, forums)
|
|
88
107
|
- Competition level (existing videos, quality bar)
|
|
89
108
|
- Trend direction (rising, stable, declining)
|
|
@@ -110,6 +129,7 @@ Which ideas do you want to develop into briefs?
|
|
|
110
129
|
```
|
|
111
130
|
|
|
112
131
|
Options:
|
|
132
|
+
|
|
113
133
|
- Pick 1-3 ideas to brief
|
|
114
134
|
- Generate more ideas in a different direction
|
|
115
135
|
- Refine a specific idea before briefing
|
|
@@ -165,4 +185,4 @@ Generate and validate YouTube video ideas aligned with content pillars, audience
|
|
|
165
185
|
|
|
166
186
|
- Official ORM documentation
|
|
167
187
|
- Community best practices and patterns
|
|
168
|
-
- Related skills in this plugin pack
|
|
188
|
+
- Related skills in this plugin pack
|
|
@@ -1,16 +1,26 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: yt-outline
|
|
3
|
-
description:
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
3
|
+
description: 'Build detailed step-by-step YouTube video outlines with demo prep, screen-share
|
|
4
|
+
sequences, and visual
|
|
5
|
+
|
|
6
|
+
planning. Use this skill whenever the user says "create an outline", "outline this
|
|
7
|
+
video", "video outline",
|
|
8
|
+
|
|
9
|
+
"build the outline", "production outline", or has an approved brief and packaging
|
|
10
|
+
and needs the final
|
|
11
|
+
|
|
12
|
+
pre-production document before demo prep and filming. Use when working with yt outline.
|
|
13
|
+
Trigger with ''yt'', ''outline''.
|
|
14
|
+
|
|
15
|
+
'
|
|
8
16
|
allowed-tools: WebSearch, Read, Write
|
|
9
17
|
version: 1.0.0
|
|
10
18
|
author: Claude Code Plugins <plugins@claudecodeplugins.io>
|
|
11
19
|
license: MIT
|
|
12
|
-
|
|
13
|
-
|
|
20
|
+
tags:
|
|
21
|
+
- productivity
|
|
22
|
+
- yt-outline
|
|
23
|
+
compatibility: Designed for Claude Code, also compatible with Codex and OpenClaw
|
|
14
24
|
---
|
|
15
25
|
# YouTube Outline
|
|
16
26
|
|
|
@@ -29,6 +39,7 @@ You need:
|
|
|
29
39
|
### Step 1: Research the Topic in Depth
|
|
30
40
|
|
|
31
41
|
Before writing the outline, deeply understand the feature/tool being demonstrated:
|
|
42
|
+
|
|
32
43
|
- Verify all steps work as expected (use WebSearch to check documentation)
|
|
33
44
|
- Identify potential gotchas or failure points
|
|
34
45
|
- Note any prerequisites the viewer needs
|
|
@@ -39,6 +50,7 @@ Before writing the outline, deeply understand the feature/tool being demonstrate
|
|
|
39
50
|
Based on the content type from the brief, choose the appropriate structure:
|
|
40
51
|
|
|
41
52
|
**For Feature Tutorials (15-30 min):**
|
|
53
|
+
|
|
42
54
|
1. Hook (30-60 sec) - What they'll be able to do by the end
|
|
43
55
|
2. Context (1-2 min) - Why this matters, brief overview
|
|
44
56
|
3. Core demonstration (10-20 min) - Step-by-step walkthrough
|
|
@@ -46,6 +58,7 @@ Based on the content type from the brief, choose the appropriate structure:
|
|
|
46
58
|
5. CTA + wrap (1-2 min) - Asset giveaway, community mention
|
|
47
59
|
|
|
48
60
|
**For Update Videos (10-20 min):**
|
|
61
|
+
|
|
49
62
|
1. Hook (30 sec) - What just changed
|
|
50
63
|
2. Overview (1-2 min) - What the update includes
|
|
51
64
|
3. Walkthrough (8-15 min) - Demo each new feature
|
|
@@ -53,6 +66,7 @@ Based on the content type from the brief, choose the appropriate structure:
|
|
|
53
66
|
5. CTA + wrap (1 min) - Asset giveaway
|
|
54
67
|
|
|
55
68
|
**For Use Case Videos (15-30 min):**
|
|
69
|
+
|
|
56
70
|
1. Hook (30-60 sec) - The impressive outcome
|
|
57
71
|
2. Problem (1-2 min) - What manual process this replaces
|
|
58
72
|
3. Solution overview (1-2 min) - High-level workflow
|
|
@@ -61,6 +75,7 @@ Based on the content type from the brief, choose the appropriate structure:
|
|
|
61
75
|
6. CTA + wrap (1-2 min) - Asset giveaway
|
|
62
76
|
|
|
63
77
|
**For Full Tutorials (30-90+ min):**
|
|
78
|
+
|
|
64
79
|
1. Hook (1-2 min) - What they'll know by the end
|
|
65
80
|
2. Overview/roadmap (2-3 min) - What the tutorial covers
|
|
66
81
|
3. Setup (5-10 min) - Getting started from scratch
|
|
@@ -74,27 +89,32 @@ Based on the content type from the brief, choose the appropriate structure:
|
|
|
74
89
|
For each section, specify:
|
|
75
90
|
|
|
76
91
|
**Talking points:**
|
|
92
|
+
|
|
77
93
|
- Key message for this section (not a script - bullet points)
|
|
78
94
|
- Transition from previous section
|
|
79
95
|
- Any specific phrases or analogies to use
|
|
80
96
|
|
|
81
97
|
**What's on screen:**
|
|
98
|
+
|
|
82
99
|
- Screen-share of what tool/feature
|
|
83
100
|
- Specific actions to perform (click here, type this, navigate there)
|
|
84
101
|
- Any diagrams, slides, or supporting visuals
|
|
85
102
|
|
|
86
103
|
**Demo sequence:**
|
|
104
|
+
|
|
87
105
|
- Exact steps to demonstrate
|
|
88
106
|
- Expected outcome the viewer should see
|
|
89
107
|
- What to do if something goes wrong (backup plan)
|
|
90
108
|
|
|
91
109
|
**Timing:**
|
|
110
|
+
|
|
92
111
|
- Target duration for this section
|
|
93
112
|
- Running total to stay within target video length
|
|
94
113
|
|
|
95
114
|
### Step 4: Create Demo Prep Checklist
|
|
96
115
|
|
|
97
116
|
For each demo in the outline, specify what the team needs to prepare:
|
|
117
|
+
|
|
98
118
|
- Accounts and tools to have logged in
|
|
99
119
|
- Sample data or projects to have ready
|
|
100
120
|
- Environment settings (clean workspace, no notifications, etc.)
|
|
@@ -121,6 +141,7 @@ Also present the demo prep checklist separately:
|
|
|
121
141
|
```
|
|
122
142
|
|
|
123
143
|
"Here's the outline and demo prep list. The team can start preparing."
|
|
144
|
+
|
|
124
145
|
- Approve and start prep
|
|
125
146
|
- Adjust section order
|
|
126
147
|
- Add/remove sections
|
|
@@ -130,6 +151,7 @@ Also present the demo prep checklist separately:
|
|
|
130
151
|
### Step 6: Save
|
|
131
152
|
|
|
132
153
|
Save two files:
|
|
154
|
+
|
|
133
155
|
- `video-outline-yt-outline.md` - The full outline
|
|
134
156
|
- `demo-prep-checklist-yt-outline.md` - The team's preparation checklist
|
|
135
157
|
|
|
@@ -184,4 +206,4 @@ Build detailed step-by-step YouTube video outlines with demo prep, screen-share
|
|
|
184
206
|
|
|
185
207
|
- Official Yt Outline documentation
|
|
186
208
|
- Community best practices and patterns
|
|
187
|
-
- Related skills in this plugin pack
|
|
209
|
+
- Related skills in this plugin pack
|
|
@@ -1,16 +1,26 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: yt-packaging
|
|
3
|
-
description:
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
3
|
+
description: 'Create optimized YouTube titles and thumbnail concepts for maximum CTR.
|
|
4
|
+
Use this skill whenever the user
|
|
5
|
+
|
|
6
|
+
says "title ideas", "thumbnail concepts", "package this video", "CTR optimization",
|
|
7
|
+
"title options", "packaging",
|
|
8
|
+
|
|
9
|
+
or has an approved brief and needs to finalize the title and thumbnail direction
|
|
10
|
+
before outlining. Packaging
|
|
11
|
+
|
|
12
|
+
determines whether viewers click. Use when working with yt packaging. Trigger with
|
|
13
|
+
''yt'', ''packaging''.
|
|
14
|
+
|
|
15
|
+
'
|
|
8
16
|
allowed-tools: WebSearch, Read, Write
|
|
9
17
|
version: 1.0.0
|
|
10
18
|
author: Claude Code Plugins <plugins@claudecodeplugins.io>
|
|
11
19
|
license: MIT
|
|
12
|
-
|
|
13
|
-
|
|
20
|
+
tags:
|
|
21
|
+
- productivity
|
|
22
|
+
- yt-packaging
|
|
23
|
+
compatibility: Designed for Claude Code, also compatible with Codex and OpenClaw
|
|
14
24
|
---
|
|
15
25
|
# YouTube Packaging
|
|
16
26
|
|
|
@@ -29,6 +39,7 @@ You need from the user:
|
|
|
29
39
|
### Step 1: Competitive Title Analysis
|
|
30
40
|
|
|
31
41
|
Before writing titles, research what's already out there:
|
|
42
|
+
|
|
32
43
|
- Search YouTube for the topic
|
|
33
44
|
- Note the top 5-10 existing titles
|
|
34
45
|
- Identify patterns: what words/structures appear in high-view videos?
|
|
@@ -40,25 +51,30 @@ Create 5-10 title options across different strategies:
|
|
|
40
51
|
|
|
41
52
|
**Strategy A: Direct Benefit**
|
|
42
53
|
Focus on what the viewer will be able to DO.
|
|
54
|
+
|
|
43
55
|
- "How to [Verb] [Tool] to [Outcome]"
|
|
44
56
|
- "Build [Thing] with [Tool] in [Time]"
|
|
45
57
|
|
|
46
58
|
**Strategy B: Curiosity Gap**
|
|
47
59
|
Create intrigue without being misleading.
|
|
60
|
+
|
|
48
61
|
- "The [Tool] Feature Nobody Is Talking About"
|
|
49
62
|
- "I Automated My Entire [Process] - Here's How"
|
|
50
63
|
|
|
51
64
|
**Strategy C: Authority/Definitive**
|
|
52
65
|
Position as THE resource.
|
|
66
|
+
|
|
53
67
|
- "The Complete [Tool] Guide for [Year]"
|
|
54
68
|
- "Everything You Need to Know About [Feature]"
|
|
55
69
|
|
|
56
70
|
**Strategy D: Trending/Urgency**
|
|
57
71
|
For update videos and time-sensitive content.
|
|
72
|
+
|
|
58
73
|
- "[Tool] Just Changed Everything - Here's What You Need to Know"
|
|
59
74
|
- "New [Feature] Walkthrough: [Specific Capability]"
|
|
60
75
|
|
|
61
76
|
**For each title:**
|
|
77
|
+
|
|
62
78
|
- Note which strategy it uses
|
|
63
79
|
- Estimate search-friendliness (contains searchable keywords?)
|
|
64
80
|
- Estimate curiosity factor (would you click?)
|
|
@@ -69,12 +85,14 @@ For update videos and time-sensitive content.
|
|
|
69
85
|
Create 3-5 thumbnail concepts. Each concept should include:
|
|
70
86
|
|
|
71
87
|
**Visual description:**
|
|
88
|
+
|
|
72
89
|
- Main visual element (screen-share preview, tool logo, face expression, graphic)
|
|
73
90
|
- Text overlay (1-4 words MAX - the thumbnail is not the title)
|
|
74
91
|
- Color scheme and contrast
|
|
75
92
|
- Layout (rule of thirds, focal point)
|
|
76
93
|
|
|
77
94
|
**For each concept:**
|
|
95
|
+
|
|
78
96
|
- How does it complement the title? (Title + thumbnail = one message, not two separate messages)
|
|
79
97
|
- Does it stand out in a feed of similar videos?
|
|
80
98
|
- Is it readable at mobile size (small thumbnail)?
|
|
@@ -83,6 +101,7 @@ Create 3-5 thumbnail concepts. Each concept should include:
|
|
|
83
101
|
### Step 4: A/B Test Variants
|
|
84
102
|
|
|
85
103
|
For the top 2-3 title + thumbnail combos, suggest A/B testing variants:
|
|
104
|
+
|
|
86
105
|
- Same title, different thumbnail approach
|
|
87
106
|
- Same thumbnail, different title strategy
|
|
88
107
|
- Small tweaks (word swaps, number inclusion)
|
|
@@ -118,6 +137,7 @@ Title #[X] + Thumbnail Concept [Y] because [reasoning]
|
|
|
118
137
|
```
|
|
119
138
|
|
|
120
139
|
"Pick your title and thumbnail direction."
|
|
140
|
+
|
|
121
141
|
- Go with recommended combo
|
|
122
142
|
- Mix and match (pick different title + thumbnail)
|
|
123
143
|
- Request more options
|
|
@@ -179,4 +199,4 @@ Create optimized YouTube titles and thumbnail concepts for maximum CTR.
|
|
|
179
199
|
|
|
180
200
|
- Official optimization documentation
|
|
181
201
|
- Community best practices and patterns
|
|
182
|
-
- Related skills in this plugin pack
|
|
202
|
+
- Related skills in this plugin pack
|
|
@@ -1,16 +1,26 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: yt-research
|
|
3
|
-
description:
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
3
|
+
description: 'Research competitor YouTube channels, niches, and trending topics for
|
|
4
|
+
your content strategy.
|
|
5
|
+
|
|
6
|
+
Use this skill whenever the user says "research channels", "analyze competitors",
|
|
7
|
+
"find trending topics",
|
|
8
|
+
|
|
9
|
+
"niche analysis", "competitive research", "what are other creators doing", "scrape
|
|
10
|
+
YouTube channels",
|
|
11
|
+
|
|
12
|
+
or wants to understand the competitive landscape for a specific tool or topic area.
|
|
13
|
+
Use when working with yt research. Trigger with ''yt'', ''research''.
|
|
14
|
+
|
|
15
|
+
'
|
|
8
16
|
allowed-tools: WebSearch, Read, Write, Task
|
|
9
17
|
version: 1.0.0
|
|
10
18
|
author: Claude Code Plugins <plugins@claudecodeplugins.io>
|
|
11
19
|
license: MIT
|
|
12
|
-
|
|
13
|
-
|
|
20
|
+
tags:
|
|
21
|
+
- productivity
|
|
22
|
+
- yt-research
|
|
23
|
+
compatibility: Designed for Claude Code, also compatible with Codex and OpenClaw
|
|
14
24
|
---
|
|
15
25
|
# YouTube Research
|
|
16
26
|
|
|
@@ -31,6 +41,7 @@ If the user provided context already, confirm your understanding and proceed.
|
|
|
31
41
|
### Step 1: Scope the Research
|
|
32
42
|
|
|
33
43
|
Define the research boundaries:
|
|
44
|
+
|
|
34
45
|
- Which channels to scrape (user-provided + discovered competitors)
|
|
35
46
|
- Which topics/keywords to search for
|
|
36
47
|
- Time horizon (recent 30 days, 90 days, or all-time)
|
|
@@ -40,6 +51,7 @@ Tell the user the plan: "I'll analyze [N] channels and search for [keywords]. Th
|
|
|
40
51
|
### Step 2: Collect Channel Data
|
|
41
52
|
|
|
42
53
|
Use web research to collect:
|
|
54
|
+
|
|
43
55
|
- Channel metadata (subscribers, total videos, posting frequency)
|
|
44
56
|
- Recent videos (last 30-50 per channel): titles, views, likes, comments, publish dates
|
|
45
57
|
- Video tags and categories where available
|
|
@@ -49,6 +61,7 @@ If Apify MCP is available, spawn `yt-scraper` sub-agent for bulk data collection
|
|
|
49
61
|
### Step 3: Analyze Channels
|
|
50
62
|
|
|
51
63
|
For each channel, analyze:
|
|
64
|
+
|
|
52
65
|
- Engagement pattern analysis (what gets views vs what doesn't)
|
|
53
66
|
- Content type distribution (tutorials, reviews, updates, opinions)
|
|
54
67
|
- Title pattern analysis (what structures and words correlate with views)
|
|
@@ -62,16 +75,19 @@ If analyzing 4+ channels, spawn `channel-analyzer` sub-agents (3 channels per ag
|
|
|
62
75
|
Using the analysis results, identify:
|
|
63
76
|
|
|
64
77
|
**Content Gaps:**
|
|
78
|
+
|
|
65
79
|
- Topics the audience searches for but competitors cover poorly
|
|
66
80
|
- Topics that are developer-focused everywhere but could be made accessible
|
|
67
81
|
- Recent tool updates/features with no quality coverage yet
|
|
68
82
|
|
|
69
83
|
**Trending Signals:**
|
|
84
|
+
|
|
70
85
|
- Tools/features getting increasing search interest
|
|
71
86
|
- Topics with recent outlier videos (sudden view spikes)
|
|
72
87
|
- Community discussions (Reddit, forums) indicating unmet demand
|
|
73
88
|
|
|
74
89
|
**Strategic Fit:**
|
|
90
|
+
|
|
75
91
|
- Which opportunities align with the creator's content pillars?
|
|
76
92
|
- Which serve the target audience?
|
|
77
93
|
- Which have the best effort-to-impact ratio?
|
|
@@ -90,9 +106,11 @@ Generate two outputs:
|
|
|
90
106
|
Present the report to the user:
|
|
91
107
|
|
|
92
108
|
"Here's the research report. Key findings:"
|
|
109
|
+
|
|
93
110
|
- [Top 3 findings]
|
|
94
111
|
|
|
95
112
|
"What would you like to do?"
|
|
113
|
+
|
|
96
114
|
- Move to ideation with these insights
|
|
97
115
|
- Research additional channels
|
|
98
116
|
- Dig deeper into a specific finding
|
|
@@ -148,4 +166,4 @@ Research competitor YouTube channels, niches, and trending topics for your conte
|
|
|
148
166
|
|
|
149
167
|
- Official content documentation
|
|
150
168
|
- Community best practices and patterns
|
|
151
|
-
- Related skills in this plugin pack
|
|
169
|
+
- Related skills in this plugin pack
|