youtube-devrel
Skill5 starsChanged 8 months agoMITView on GitHub
Create developer YouTube content, technical screencasts, and video tutorials. Covers tutorial structure, screen recording setup, live coding, shorts vs long-form, thumbnails, and SEO for technical content. Use when: YouTube, developer video, screencast, video tutorial, live coding, YouTube for developers, tech YouTube, YouTube thumbnails.
In this repository29 other files it gives its agents.
- skills/architect/CLAUDE.mdCLAUDE.md
- skills/council/CLAUDE.mdCLAUDE.md
- agent-browserSkill
- app-store-screenshotsSkill
- architectSkill
- architecture-reviewerSkill
- c-cpp-analyzerSkill
- councilSkill
- c-to-rust-migrationSkill
- demo-pipelineSkill
- e2e-pipelineSkill
- founder-modeSkill
- full-evalSkill
- hackathon-jurySkill
- idea-labSkill
- ios-glass-ui-designerSkill
- learn-by-mistakeSkill
- maestro-mobile-testingSkill
- migration-validatorSkill
- mobile-design-systemSkill
- noricum-devSkill
- oss-readinessSkill
- pdf-presentationSkill
- playwright-recordingSkill
- post-run-analysisSkill
- rust-migrationSkill
- ui-ux-polishSkill
- vc-evaluatorSkill
- webreelSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 142
If topic is too broad: suggest 3 narrower angles
- Distinctive: line 143
If topic is too niche: suggest broadening with comparison format
- Distinctive: line 144
If no target audience specified: default to "working developers wanting quick solutions" (5-15 min)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
YouTube DevRel
Generate developer YouTube content — from idea to publish-ready assets.
Workflow
Given a video idea, produce:
- Title — SEO-optimized using proven formulas:
[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"
- Description — first 150 chars keyword-rich, timestamps placeholder, resource links, hashtags:
[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] - Outline — timed segments with hook (first 30s shows end result), chapters, CTA placement:
0:00 - Hook (show the finished result) 0:30 - Prerequisites & setup 2:00 - Concept explanation (why this matters) 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) - Script Notes — key points per segment (not verbatim script — bullet points to talk from)
- Thumbnail Brief — text (3-5 words), composition (face + logo + emotion), colors:
- Patterns that work: Face + tech logo + emotion, Before/after, Big text + icon, Comparison, Result preview
- High contrast, brand consistent colors
- Rule of thirds composition
- Tags — 10-15 relevant tags mixing broad and specific
For Shorts:
- Hook in first 2 seconds
- One concept, 30-45 seconds
- Big on-screen captions
- Vertical format (9:16)
Shorts Content Ideas
- 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"
Example Output
Video idea: "Build a CLI tool with Node.js"
Title: How to Build a CLI Tool with Node.js (Step by Step)
Description:
Build a powerful command-line tool with Node.js from scratch. We'll create a CLI that fetches GitHub stats using Commander.js and Chalk for beautiful output.
In this video, I'll walk you through building a real-world CLI tool — from parsing arguments to publishing on npm.
Timestamps:
0:00 - What we're building (demo)
0:30 - Project setup & dependencies
2:00 - Parsing CLI arguments with Commander.js
5:00 - Fetching data from GitHub API
8:00 - Formatting output with Chalk
11:00 - Adding error handling
13:00 - Publishing to npm
15:00 - Recap & next steps
Resources:
- GitHub repo: https://github.com/...
- Commander.js docs: https://github.com/tj/commander.js
- Chalk docs: https://github.com/chalk/chalk
#nodejs #cli #javascript #tutorial #programmingOutline:
0:00 - Hook: Show the finished CLI running in terminal (3 commands, colorful output)
0:30 - Prerequisites: Node.js 18+, basic JS knowledge. "Should take about 15 minutes."
2:00 - Why CLI tools? Quick explanation of when/why you'd build one
3:00 - Step 1: npm init, install commander + chalk
5:00 - Step 2: Set up Commander with basic command parsing
8:00 - Step 3: Add GitHub API fetch with error handling
11:00 - Step 4: Format output with Chalk (colors, tables)
13:00 - Step 5: Add to package.json bin field, test with npx
15:00 - Final demo, recap key concepts, CTAScript Notes:
- Hook: Run
ghstats --user torvalds— show colorful output with repos, stars, contributions - Setup: "Two dependencies — that's it. Commander for argument parsing, Chalk for colors."
- API section: Show the raw JSON first, then the formatted version — visual before/after
- Publishing: "The bin field is the magic — it tells npm this is an executable"
Thumbnail Brief:
- Text: "Build a CLI" (3 words)
- Composition: Terminal screenshot (left) + Node.js logo (top right) + face showing excitement (right)
- Colors: Dark background (terminal-like), green accent (#00ff00), Node.js green
Tags: nodejs, cli tool, command line, node.js tutorial, build cli, commander.js, chalk, npm publish, javascript cli, terminal tool, node.js project, coding tutorial, web development, programming tutorial
Error Handling
- If topic is too broad: suggest 3 narrower angles
- If topic is too niche: suggest broadening with comparison format
- If no target audience specified: default to "working developers wanting quick solutions" (5-15 min)
References
references/strategy.md— audience segments, content types, calendar planningreferences/production.md— equipment, recording setup, editing workflow
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

