youtube-devrel

Name: youtube-devrel
Author: jonathimer

74installs6forks

How to install youtube-devrel?

jonathimer/devmarketing-skills/youtube-devrel

$npx -y skills add jonathimer/devmarketing-skills --skill youtube-devrel

Installs into the current project.

Summary

When the user wants to create developer YouTube content, technical screencasts, or video tutorials. Trigger phrases include "YouTube," "developer video," "screencast," "video tutorial," "live coding," "YouTube for developers," "tech YouTube," or "YouTube thumbnails.

Files · 1

View on GitHub

SKILL.md

1	# YouTube for Developer Relations
2
3	YouTube is the second-largest search engine and where developers go to learn. This skill covers tutorial structure, screen recording setup, live coding, shorts vs long-form, thumbnails, and SEO for technical content.
4
5	---
6
7	## Before You Start
8
9	1. Read `.agents/developer-audience-context.md` if it exists
10	2. Audit existing technical YouTube channels in your space
11	3. Understand: Developer YouTube is a long game — consistency > perfection
12
13	---
14
15	## Understanding Developer YouTube
16
17	### Who Watches Dev Content
18
19	\| Audience \| What they want \| Video length \|
20	\|----------\|----------------\|--------------\|
21	\| Learning developers \| Complete tutorials \| 15-45 min \|
22	\| Working developers \| Quick solutions \| 5-15 min \|
23	\| Senior developers \| Deep dives, architecture \| 30-60 min \|
24	\| Decision makers \| Demos, overviews \| 3-10 min \|
25	\| Conference attendees \| Recorded talks \| 20-45 min \|
26
27	### Content Types That Work
28
29	\| Content type \| View potential \| Effort \| Notes \|
30	\|--------------\|----------------\|--------\|-------\|
31	\| Tutorial (build X) \| Very high \| High \| Evergreen traffic \|
32	\| Problem/solution \| High \| Medium \| Search-driven \|
33	\| Tool comparisons \| High \| Medium \| High search volume \|
34	\| Live coding \| Medium-high \| Low \| Engagement-focused \|
35	\| Project updates \| Medium \| Low \| Community building \|
36	\| Conference talks \| Medium \| Low \| Repurpose content \|
37	\| Shorts \| High reach \| Low \| Discovery-focused \|
38
39	### Successful Dev YouTube Channels
40
41	\| Channel \| Style \| Why it works \|
42	\|---------\|-------\|--------------\|
43	\| Fireship \| Fast, dense, opinionated \| Respects viewer time \|
44	\| ThePrimeagen \| Personality, live reactions \| Authentic, entertaining \|
45	\| Traversy Media \| Clear, beginner-friendly \| Comprehensive tutorials \|
46	\| Hussein Nasser \| Deep dives, whiteboard \| Engineering depth \|
47	\| Ben Awad \| Casual, real coding \| Relatable, genuine \|
48
49	---
50
51	## Tutorial Structure
52
53	### The Tutorial Template
54
55	```
56	0:00 - Hook (what you'll build/learn)
57	0:30 - Prerequisites & setup
58	2:00 - Concept explanation (why)
59	4:00 - Step 1: [First major step]
60	8:00 - Step 2: [Second major step]
61	...
62	XX:00 - Final result demo
63	XX:30 - Recap & next steps
64	XX:45 - CTA (subscribe, comment)
65	```
66
67	### Opening Hook (First 30 Seconds)
68
69	\| Element \| Purpose \|
70	\|---------\|---------\|
71	\| Show the end result \| Prove it's worth watching \|
72	\| State what they'll learn \| Set expectations \|
73	\| Mention prerequisites \| Qualify viewers \|
74	\| Estimated time \| Respect their time \|
75
76	Example hook:
77	```
78	"By the end of this video, you'll have a working CLI tool
79	that can scrape any website and export to JSON. We'll use
80	Node.js and Cheerio — you just need basic JavaScript
81	knowledge. This should take about 20 minutes. Let's go."
82	```
83
84	### Pacing Guidelines
85
86	\| Video length \| Segment length \| Notes \|
87	\|--------------\|----------------\|-------\|
88	\| 5-10 min \| 1-2 min segments \| Fast, focused \|
89	\| 15-30 min \| 3-5 min segments \| Standard tutorial \|
90	\| 30-60 min \| 5-10 min segments \| Deep dive \|
91
92	### Common Tutorial Mistakes
93
94	\| Mistake \| Impact \| Fix \|
95	\|---------\|--------\|-----\|
96	\| Too much setup \| Viewers drop off \| Skip to interesting parts \|
97	\| Not showing end result \| No motivation \| Show finished product first \|
98	\| Going too fast \| Confusion \| Pause on key steps \|
99	\| Going too slow \| Boredom \| Edit out pauses, typos \|
100	\| No timestamps \| Poor navigation \| Add chapters \|
101	\| Walls of code \| Overwhelming \| Build incrementally \|
102
103	---
104
105	## Screen Recording Setup
106
107	### Essential Equipment
108
109	\| Equipment \| Budget option \| Better option \|
110	\|-----------\|---------------\|---------------\|
111	\| Microphone \| Blue Snowball ($50) \| Shure SM7B ($400) \|
112	\| Screen recording \| OBS (free) \| ScreenFlow ($170) \|
113	\| Webcam \| Built-in \| Logitech C920 ($80) \|
114	\| Lighting \| Window light \| Ring light ($30) \|
115	\| Editor \| DaVinci Resolve (free) \| Premiere Pro ($22/mo) \|
116
117	### Audio is More Important Than Video
118
119	\| Priority \| Why \|
120	\|----------\|-----\|
121	\| 1. Clear audio \| Bad audio = immediate click away \|
122	\| 2. Readable code \| Text must be crisp \|
123	\| 3. Good lighting \| For facecam sections \|
124	\| 4. High resolution \| 1080p minimum \|
125
126	### Screen Recording Best Practices
127
128	\| Setting \| Recommendation \|
129	\|---------\|----------------\|
130	\| Resolution \| 1920x1080 or 2560x1440 \|
131	\| Font size \| 18-24pt in editor \|
132	\| Theme \| Dark theme (easier on eyes) \|
133	\| Zoom \| Use IDE zoom for key sections \|
134	\| Notifications \| Disable all \|
135	\| Browser \| Use clean profile, no bookmarks bar \|
136
137	### Recording Workflow
138
139	1. Script key points (don't read verbatim)
140	2. Test audio levels before recording
141	3. Record in segments (easier editing)
142	4. Leave pauses for edits (clap or say "edit")
143	5. Show face at transitio

People who liked this also viewed

6 picks

Type

youtube-devrel

74installs6forks

View on GitHub

How to install youtube-devrel?

jonathimer/devmarketing-skills/youtube-devrel

$npx -y skills add jonathimer/devmarketing-skills --skill youtube-devrel

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# YouTube for Developer Relations
2
3	YouTube is the second-largest search engine and where developers go to learn. This skill covers tutorial structure, screen recording setup, live coding, shorts vs long-form, thumbnails, and SEO for technical content.
4
5	---
6
7	## Before You Start
8
9	1. Read `.agents/developer-audience-context.md` if it exists
10	2. Audit existing technical YouTube channels in your space
11	3. Understand: Developer YouTube is a long game — consistency > perfection
12
13	---
14
15	## Understanding Developer YouTube
16
17	### Who Watches Dev Content
18
19	\| Audience \| What they want \| Video length \|
20	\|----------\|----------------\|--------------\|
21	\| Learning developers \| Complete tutorials \| 15-45 min \|
22	\| Working developers \| Quick solutions \| 5-15 min \|
23	\| Senior developers \| Deep dives, architecture \| 30-60 min \|
24	\| Decision makers \| Demos, overviews \| 3-10 min \|
25	\| Conference attendees \| Recorded talks \| 20-45 min \|
26
27	### Content Types That Work
28
29	\| Content type \| View potential \| Effort \| Notes \|
30	\|--------------\|----------------\|--------\|-------\|
31	\| Tutorial (build X) \| Very high \| High \| Evergreen traffic \|
32	\| Problem/solution \| High \| Medium \| Search-driven \|
33	\| Tool comparisons \| High \| Medium \| High search volume \|
34	\| Live coding \| Medium-high \| Low \| Engagement-focused \|
35	\| Project updates \| Medium \| Low \| Community building \|
36	\| Conference talks \| Medium \| Low \| Repurpose content \|
37	\| Shorts \| High reach \| Low \| Discovery-focused \|
38
39	### Successful Dev YouTube Channels
40
41	\| Channel \| Style \| Why it works \|
42	\|---------\|-------\|--------------\|
43	\| Fireship \| Fast, dense, opinionated \| Respects viewer time \|
44	\| ThePrimeagen \| Personality, live reactions \| Authentic, entertaining \|
45	\| Traversy Media \| Clear, beginner-friendly \| Comprehensive tutorials \|
46	\| Hussein Nasser \| Deep dives, whiteboard \| Engineering depth \|
47	\| Ben Awad \| Casual, real coding \| Relatable, genuine \|
48
49	---
50
51	## Tutorial Structure
52
53	### The Tutorial Template
54
55	```
56	0:00 - Hook (what you'll build/learn)
57	0:30 - Prerequisites & setup
58	2:00 - Concept explanation (why)
59	4:00 - Step 1: [First major step]
60	8:00 - Step 2: [Second major step]
61	...
62	XX:00 - Final result demo
63	XX:30 - Recap & next steps
64	XX:45 - CTA (subscribe, comment)
65	```
66
67	### Opening Hook (First 30 Seconds)
68
69	\| Element \| Purpose \|
70	\|---------\|---------\|
71	\| Show the end result \| Prove it's worth watching \|
72	\| State what they'll learn \| Set expectations \|
73	\| Mention prerequisites \| Qualify viewers \|
74	\| Estimated time \| Respect their time \|
75
76	Example hook:
77	```
78	"By the end of this video, you'll have a working CLI tool
79	that can scrape any website and export to JSON. We'll use
80	Node.js and Cheerio — you just need basic JavaScript
81	knowledge. This should take about 20 minutes. Let's go."
82	```
83
84	### Pacing Guidelines
85
86	\| Video length \| Segment length \| Notes \|
87	\|--------------\|----------------\|-------\|
88	\| 5-10 min \| 1-2 min segments \| Fast, focused \|
89	\| 15-30 min \| 3-5 min segments \| Standard tutorial \|
90	\| 30-60 min \| 5-10 min segments \| Deep dive \|
91
92	### Common Tutorial Mistakes
93
94	\| Mistake \| Impact \| Fix \|
95	\|---------\|--------\|-----\|
96	\| Too much setup \| Viewers drop off \| Skip to interesting parts \|
97	\| Not showing end result \| No motivation \| Show finished product first \|
98	\| Going too fast \| Confusion \| Pause on key steps \|
99	\| Going too slow \| Boredom \| Edit out pauses, typos \|
100	\| No timestamps \| Poor navigation \| Add chapters \|
101	\| Walls of code \| Overwhelming \| Build incrementally \|
102
103	---
104
105	## Screen Recording Setup
106
107	### Essential Equipment
108
109	\| Equipment \| Budget option \| Better option \|
110	\|-----------\|---------------\|---------------\|
111	\| Microphone \| Blue Snowball ($50) \| Shure SM7B ($400) \|
112	\| Screen recording \| OBS (free) \| ScreenFlow ($170) \|
113	\| Webcam \| Built-in \| Logitech C920 ($80) \|
114	\| Lighting \| Window light \| Ring light ($30) \|
115	\| Editor \| DaVinci Resolve (free) \| Premiere Pro ($22/mo) \|
116
117	### Audio is More Important Than Video
118
119	\| Priority \| Why \|
120	\|----------\|-----\|
121	\| 1. Clear audio \| Bad audio = immediate click away \|
122	\| 2. Readable code \| Text must be crisp \|
123	\| 3. Good lighting \| For facecam sections \|
124	\| 4. High resolution \| 1080p minimum \|
125
126	### Screen Recording Best Practices
127
128	\| Setting \| Recommendation \|
129	\|---------\|----------------\|
130	\| Resolution \| 1920x1080 or 2560x1440 \|
131	\| Font size \| 18-24pt in editor \|
132	\| Theme \| Dark theme (easier on eyes) \|
133	\| Zoom \| Use IDE zoom for key sections \|
134	\| Notifications \| Disable all \|
135	\| Browser \| Use clean profile, no bookmarks bar \|
136
137	### Recording Workflow
138
139	1. Script key points (don't read verbatim)
140	2. Test audio levels before recording
141	3. Record in segments (easier editing)
142	4. Leave pauses for edits (clap or say "edit")
143	5. Show face at transitio

People who liked this also viewed

6 picks

Type