Developer Advocacy
When to Use
Use this skill when you need when the user wants to do developer advocacy activities including conference talks, live coding, podcasts, and building in public. Trigger phrases include "developer advocacy," "devrel," "conference talk," "CFP," "call for papers," "live coding," "podcast," "building in public,"...
This skill helps you with developer advocacy activities: conference talks, live coding demos, podcast appearances, and building in public. Covers talk proposals, demo prep, social presence, and measuring impact.
Before You Start
Load your audience context first. Read .agents/developer-audience-context.md to understand:
- Who you're trying to reach (conferences they attend, podcasts they listen to)
- What topics resonate (pain points, interests)
- Your product's positioning (what story to tell)
- Voice & tone (how formal/technical to be)
If the context file doesn't exist, run the developer-audience-context skill first.
Conference Talks
Finding the Right Conferences
| Conference Type |
Best For |
Examples |
| Large industry |
Brand awareness, reach |
KubeCon, AWS re:Invent, React Summit |
| Regional |
Local community, accessible |
Local meetups, city tech conferences |
| Niche |
Targeted audience, expertise |
GraphQL Conf, RustConf |
| Company-hosted |
Ecosystem presence |
Vercel Ship, GitHub Universe |
| Unconferences |
Community connection |
BarCamps, DevOpsDays |
Talk Proposal (CFP) Framework
The winning formula:
Specific Problem + Unique Angle + Clear Takeaways = Accepted Talk
CFP Template:
# Title
[Action verb] + [specific outcome] + [with/using what]
Example: "Building Real-Time Features with Edge Functions and WebSockets"
# Abstract (100-200 words)
[Hook: Problem or curiosity gap]
[What you'll cover]
[What attendees will learn/be able to do]
# Description (detailed, for reviewers)
[Problem context]
[Why this approach]
[Talk structure]
[Your credibility to give this talk]
# Outline
- [Time] Introduction / Problem statement
- [Time] Section 1
- [Time] Section 2
- [Time] Section 3
- [Time] Live demo / walkthrough
- [Time] Key takeaways / Q&A
# Audience
[Who this is for]
[Prerequisite knowledge]
[What they'll learn]
# Bio
[Your relevant experience]
[Why you're qualified]
Title Patterns That Work
| Pattern |
Example |
| How I X |
"How I Reduced Deploy Time by 80%" |
| X in Y Minutes |
"Kubernetes Security in 15 Minutes" |
| The X of Y |
"The Psychology of Error Messages" |
| Beyond X |
"Beyond Console.log: Modern Debugging" |
| X for Y |
"GraphQL for REST Developers" |
| Lessons from X |
"Lessons from 1000 Production Outages" |
Talk Types
| Type |
Length |
Best For |
| Lightning |
5-10 min |
Single concept, quick demo |
| Standard |
25-45 min |
Technical deep-dive |
| Keynote |
45-60 min |
Big picture, inspiring |
| Workshop |
2-4 hours |
Hands-on learning |
| Panel |
30-60 min |
Discussion, multiple perspectives |
Talk Prep Checklist
| Phase |
Tasks |
| 2 months before |
Outline, start slides, test demos |
| 1 month before |
Draft complete, first practice run |
| 2 weeks before |
Slides polished, demos solid, practice 3x |
| 1 week before |
Record yourself, get feedback, finalize |
| Day before |
Test all tech, backup slides, rest |
| Day of |
Arrive early, test A/V, hydrate |
Live Coding & Demos
The Demo Danger Zone
| Risk |
Mitigation |
| Internet fails |
Pre-record backup, local server |
| Typo freezes you |
Practice typing same code 20x |
| Error you can't fix |
Have working checkpoints to jump to |
| Runs over time |
Time yourself, cut ruthlessly |
| Code too small |
Zoom in, use large font (24pt+) |
| Dark theme blinding |
Use high-contrast, light-friendly theme |
Demo Prep Framework
The 10-3-1 Rule:
- Run your demo 10 times in practice
- Have 3 checkpoints you can jump to if stuck
- 1 backup (video recording of it working)
Pre-demo checklist:
Live Coding Tips
| Tip |
Why |
| Type slowly |
Audience needs to follow |
| Narrate what you type |
"I'm creating a new handler..." |
| Explain errors |
"This error means X, let me fix it" |
| Use snippets |
For boilerplate, not core concepts |
| Show the result |
Always run the code, show output |
| Checkpoint commits |
git checkout checkpoint-1 |
Podcast Guesting
Finding Podcasts
|
1---2name: developer-advocacy3description: When the user wants to do developer advocacy activities including conference talks, live coding, podcasts, and building in public.4---567# Developer Advocacy8## When to Use910Use this skill when you need when the user wants to do developer advocacy activities including conference talks, live coding, podcasts, and building in public. Trigger phrases include "developer advocacy," "devrel," "conference talk," "CFP," "call for papers," "live coding," "podcast," "building in public,"...111213This skill helps you with developer advocacy activities: conference talks, live coding demos, podcast appearances, and building in public. Covers talk proposals, demo prep, social presence, and measuring impact.1415---1617## Before You Start1819**Load your audience context first.** Read `.agents/developer-audience-context.md` to understand:2021- Who you're trying to reach (conferences they attend, podcasts they listen to)22- What topics resonate (pain points, interests)23- Your product's positioning (what story to tell)24- Voice & tone (how formal/technical to be)2526If the context file doesn't exist, run the `developer-audience-context` skill first.2728---2930## Conference Talks3132### Finding the Right Conferences3334| Conference Type | Best For | Examples |35|-----------------|----------|----------|36| **Large industry** | Brand awareness, reach | KubeCon, AWS re:Invent, React Summit |37| **Regional** | Local community, accessible | Local meetups, city tech conferences |38| **Niche** | Targeted audience, expertise | GraphQL Conf, RustConf |39| **Company-hosted** | Ecosystem presence | Vercel Ship, GitHub Universe |40| **Unconferences** | Community connection | BarCamps, DevOpsDays |4142### Talk Proposal (CFP) Framework4344**The winning formula:**45```46Specific Problem + Unique Angle + Clear Takeaways = Accepted Talk47```4849**CFP Template:**5051```markdown52# Title53[Action verb] + [specific outcome] + [with/using what]54Example: "Building Real-Time Features with Edge Functions and WebSockets"5556# Abstract (100-200 words)57[Hook: Problem or curiosity gap]58[What you'll cover]59[What attendees will learn/be able to do]6061# Description (detailed, for reviewers)62[Problem context]63[Why this approach]64[Talk structure]65[Your credibility to give this talk]6667# Outline68- [Time] Introduction / Problem statement69- [Time] Section 170- [Time] Section 271- [Time] Section 372- [Time] Live demo / walkthrough73- [Time] Key takeaways / Q&A7475# Audience76[Who this is for]77[Prerequisite knowledge]78[What they'll learn]7980# Bio81[Your relevant experience]82[Why you're qualified]83```8485### Title Patterns That Work8687| Pattern | Example |88|---------|---------|89| **How I X** | "How I Reduced Deploy Time by 80%" |90| **X in Y Minutes** | "Kubernetes Security in 15 Minutes" |91| **The X of Y** | "The Psychology of Error Messages" |92| **Beyond X** | "Beyond Console.log: Modern Debugging" |93| **X for Y** | "GraphQL for REST Developers" |94| **Lessons from X** | "Lessons from 1000 Production Outages" |9596### Talk Types9798| Type | Length | Best For |99|------|--------|----------|100| **Lightning** | 5-10 min | Single concept, quick demo |101| **Standard** | 25-45 min | Technical deep-dive |102| **Keynote** | 45-60 min | Big picture, inspiring |103| **Workshop** | 2-4 hours | Hands-on learning |104| **Panel** | 30-60 min | Discussion, multiple perspectives |105106### Talk Prep Checklist107108| Phase | Tasks |109|-------|-------|110| **2 months before** | Outline, start slides, test demos |111| **1 month before** | Draft complete, first practice run |112| **2 weeks before** | Slides polished, demos solid, practice 3x |113| **1 week before** | Record yourself, get feedback, finalize |114| **Day before** | Test all tech, backup slides, rest |115| **Day of** | Arrive early, test A/V, hydrate |116117---118119## Live Coding & Demos120121### The Demo Danger Zone122123| Risk | Mitigation |124|------|------------|125| **Internet fails** | Pre-record backup, local server |126| **Typo freezes you** | Practice typing same code 20x |127| **Error you can't fix** | Have working checkpoints to jump to |128| **Runs over time** | Time yourself, cut ruthlessly |129| **Code too small** | Zoom in, use large font (24pt+) |130| **Dark theme blinding** | Use high-contrast, light-friendly theme |131132### Demo Prep Framework133134**The 10-3-1 Rule:**135- Run your demo **10 times** in practice136- Have **3 checkpoints** you can jump to if stuck137- **1 backup** (video recording of it working)138139**Pre-demo checklist:**140- [ ] Close unnecessary apps141- [ ] Clear browser history/tabs142- [ ] Notifications OFF (Slack, email, calendar)143- [ ] Font size: 24pt+ for terminal, 20pt+ for editor144- [ ] Git stash/branch for clean starting point145- [ ] Environment variables ready146- [ ] Test on the actual projector/screen if possible147148### Live Coding Tips149150| Tip | Why |151|-----|-----|152| **Type slowly** | Audience needs to follow |153| **Narrate what you type** | "I'm creating a new handler..." |154| **Explain errors** | "This error means X, let me fix it" |155| **Use snippets** | For boilerplate, not core concepts |156| **Show the result** | Always run the code, show output |157| **Checkpoint commits** | `git checkout checkpoint-1` |158159---160161## Podcast Guesting162163### Finding Podcasts164165|
ranbot-ai