skills/youtube-devrel/SKILL.md
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."
npx skillsauth add jonathimer/devmarketing-skills youtube-devrelInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
.agents/developer-audience-context.md if it exists| Audience | What they want | Video length | |----------|----------------|--------------| | Learning developers | Complete tutorials | 15-45 min | | Working developers | Quick solutions | 5-15 min | | Senior developers | Deep dives, architecture | 30-60 min | | Decision makers | Demos, overviews | 3-10 min | | Conference attendees | Recorded talks | 20-45 min |
| Content type | View potential | Effort | Notes | |--------------|----------------|--------|-------| | Tutorial (build X) | Very high | High | Evergreen traffic | | Problem/solution | High | Medium | Search-driven | | Tool comparisons | High | Medium | High search volume | | Live coding | Medium-high | Low | Engagement-focused | | Project updates | Medium | Low | Community building | | Conference talks | Medium | Low | Repurpose content | | Shorts | High reach | Low | Discovery-focused |
| Channel | Style | Why it works | |---------|-------|--------------| | Fireship | Fast, dense, opinionated | Respects viewer time | | ThePrimeagen | Personality, live reactions | Authentic, entertaining | | Traversy Media | Clear, beginner-friendly | Comprehensive tutorials | | Hussein Nasser | Deep dives, whiteboard | Engineering depth | | Ben Awad | Casual, real coding | Relatable, genuine |
0:00 - Hook (what you'll build/learn)
0:30 - Prerequisites & setup
2:00 - Concept explanation (why)
4:00 - Step 1: [First major step]
8:00 - Step 2: [Second major step]
...
XX:00 - Final result demo
XX:30 - Recap & next steps
XX:45 - CTA (subscribe, comment)
| Element | Purpose | |---------|---------| | Show the end result | Prove it's worth watching | | State what they'll learn | Set expectations | | Mention prerequisites | Qualify viewers | | Estimated time | Respect their time |
Example hook:
"By the end of this video, you'll have a working CLI tool
that can scrape any website and export to JSON. We'll use
Node.js and Cheerio — you just need basic JavaScript
knowledge. This should take about 20 minutes. Let's go."
| Video length | Segment length | Notes | |--------------|----------------|-------| | 5-10 min | 1-2 min segments | Fast, focused | | 15-30 min | 3-5 min segments | Standard tutorial | | 30-60 min | 5-10 min segments | Deep dive |
| Mistake | Impact | Fix | |---------|--------|-----| | Too much setup | Viewers drop off | Skip to interesting parts | | Not showing end result | No motivation | Show finished product first | | Going too fast | Confusion | Pause on key steps | | Going too slow | Boredom | Edit out pauses, typos | | No timestamps | Poor navigation | Add chapters | | Walls of code | Overwhelming | Build incrementally |
| Equipment | Budget option | Better option | |-----------|---------------|---------------| | Microphone | Blue Snowball ($50) | Shure SM7B ($400) | | Screen recording | OBS (free) | ScreenFlow ($170) | | Webcam | Built-in | Logitech C920 ($80) | | Lighting | Window light | Ring light ($30) | | Editor | DaVinci Resolve (free) | Premiere Pro ($22/mo) |
| Priority | Why | |----------|-----| | 1. Clear audio | Bad audio = immediate click away | | 2. Readable code | Text must be crisp | | 3. Good lighting | For facecam sections | | 4. High resolution | 1080p minimum |
| Setting | Recommendation | |---------|----------------| | Resolution | 1920x1080 or 2560x1440 | | Font size | 18-24pt in editor | | Theme | Dark theme (easier on eyes) | | Zoom | Use IDE zoom for key sections | | Notifications | Disable all | | Browser | Use clean profile, no bookmarks bar |
| Format | Length | Platform | |--------|--------|----------| | Twitch stream → YouTube | 1-4 hours | Both | | YouTube Live | 30-90 min | YouTube | | Pre-recorded "live" | 20-45 min | YouTube |
| Do | Don't | |----|-------| | Explain your thinking | Code silently | | Embrace mistakes | Pretend you know everything | | Read chat | Ignore audience | | Have a goal | Meander aimlessly | | Take breaks | Marathon without pause | | Use timestamps post-stream | Leave as giant blob |
| Content | Example | |---------|---------| | Project from scratch | "Building a REST API live" | | Code review | "Reviewing subscriber PRs" | | Problem solving | "LeetCode medium problems" | | Exploring new tech | "Learning Rust in public" | | Bug hunting | "Fixing production issues live" |
| Aspect | Best practice | |--------|---------------| | Hook | Immediate (first 1-2 seconds) | | Length | 30-45 seconds optimal | | Aspect ratio | 9:16 (vertical) | | Content | One tip, one concept | | Text | Big, on-screen captions | | Audio | Clear voiceover |
| Type | Example | |------|---------| | Quick tips | "One command to speed up Git" | | Syntax shortcuts | "JavaScript spread operator in 30s" | | Tool demos | "VS Code extension you need" | | Code transformations | "Before/after refactoring" | | Hot takes | "Stop using X, here's why" |
| Goal | Approach | |------|----------| | Grow subscribers | Post 3-5 shorts/week | | Drive to long-form | Tease tutorials in shorts | | Algorithm favor | Consistent posting schedule | | Repurpose content | Cut from long videos |
| Long-form | Shorts | |-----------|--------| | Search traffic | Discovery traffic | | Watch time revenue | Low revenue | | Depth | Breadth | | Subscribers who stay | Subscribers who scroll | | Comments, community | Less engagement |
| Element | Guideline | |---------|-----------| | Text | 3-5 words max | | Face | Expression adds emotion | | Logo/icon | Tech being discussed | | Colors | High contrast, brand consistent | | Composition | Rule of thirds |
| Pattern | Example | |---------|---------| | Face + tech logo + emotion | [Surprised face] + [React logo] + "It changed everything" | | Before/after | [Broken code] → [Working code] | | Big text + icon | "STOP" + [X mark] | | Comparison | [Tech A] vs [Tech B] | | Result preview | [Screenshot of finished app] |
| Tool | Best for | |------|----------| | Canva | Quick, easy templates | | Figma | Design control | | Photoshop | Advanced editing | | Thumbnail templates | Consistency |
YouTube allows thumbnail testing:
| Location | Impact | Best practice | |----------|--------|---------------| | Title | Highest | Primary keyword early | | Description | High | First 2 sentences keyword-rich | | Tags | Low | Include, but don't overthink | | Captions/transcript | Medium | Auto-generated + edit | | Filename | Low | Include keyword anyway |
| Formula | Example | |---------|---------| | [Tech] Tutorial: [What you'll build] | "React Tutorial: Build a Todo App from Scratch" | | How to [Task] with [Tech] | "How to Deploy to AWS with Docker" | | [Tech A] vs [Tech B]: Which is Better? | "Next.js vs Remix: Which Should You Learn?" | | [Number] [Topic] Tips in [Time] | "10 VS Code Tips in 10 Minutes" | | Why I [Action] [Tech] | "Why I Switched from React to Svelte" |
[First 150 chars: Compelling summary with main keyword]
In this video, I'll show you [what they'll learn].
Timestamps:
0:00 - Introduction
2:00 - [Section 1]
[...]
Resources mentioned:
- [Link 1]
- [Link 2]
Links:
🔗 My website: [URL]
🔗 GitHub repo: [URL]
🔗 Discord: [URL]
#[keyword1] #[keyword2] #[keyword3]
| Tool | Use for | |------|---------| | YouTube search autocomplete | Real search queries | | TubeBuddy/VidIQ | Search volume, competition | | Google Trends | Trending topics | | Competitor titles | What's working |
| Day | Content | |-----|---------| | Monday | Shorts (tip/trick) | | Wednesday | Long-form tutorial | | Friday | Shorts (from Wednesday video) | | Weekend | Edit next week's content |
| Week | Focus | |------|-------| | Week 1 | Tutorial (main content) | | Week 2 | Live stream or Q&A | | Week 3 | Tutorial (main content) | | Week 4 | Comparison or review |
| Tool | Use case | |------|----------| | Octolens | Monitor YouTube and social for mentions of your tech topics, competitors, and find what developers are asking about. | | OBS Studio | Free screen recording and streaming | | ScreenFlow | Mac recording and editing | | DaVinci Resolve | Free professional editing | | Descript | Edit video by editing transcript | | Canva | Thumbnail creation | | TubeBuddy | YouTube SEO tools | | Riverside.fm | Remote recording |
First video:
developer-audience-context — Know who's watchingdev-to-hashnode — Turn videos into blog postslinkedin-technical — Share videos on LinkedInx-devs — Promote videos on Twittergithub-presence — Link repos in descriptionsdevelopment
When the user wants to build a developer following on Twitter/X, write technical threads, or understand what works for dev audiences on X. Trigger phrases include "Twitter," "X," "developer Twitter," "tech Twitter," "technical threads," "building dev following," or "Twitter for developers."
development
Design pricing models that developers understand, accept, and can predict. Trigger phrases: usage-based pricing, API pricing, metered billing, developer pricing, pricing page, cost calculator, pay as you go, pricing transparency, competitive pricing, developer billing
development
When the user wants to create step-by-step technical tutorials, quickstarts, or code walkthroughs. Trigger phrases include "tutorial," "quickstart," "getting started guide," "walkthrough," "step by step," "how to guide," "hands-on guide," or "code tutorial."
tools
Design SDKs that developers love to use—APIs that feel native, error messages that guide, and experiences that reduce friction. This skill covers creating SDKs that drive adoption through exceptional developer experience rather than aggressive marketing. Trigger phrases: "SDK design", "developer experience", "API design", "SDK DX", "error messages", "type safety", "IDE integration", "SDK versioning", "migration guides", "client library design", "making SDKs feel native", "SDK best practices"