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
| Approach |
How |
| Direct search |
"top [your tech] podcasts" |
| Guest networks |
Podmatch, Matchmaker.fm |
| Peer asks |
"What podcasts do you listen to?" |
| Twitter search |
"[topic] podcast episode" |
| Listen Notes |
Podcast search engine |
Pitch Template
Subject: Guest Idea: [Specific Topic] for [Podcast Name]
Hi [Host Name],
I've been listening to [Podcast] for [time] — loved your episode on [specific episode].
I'd love to come on and talk about [specific topic]. Here's the angle:
[2-3 sentences on what you'd discuss and why it matters to their audience]
A bit about me:
- [Relevant credential 1]
- [Relevant credential 2]
- [Link to past podcast/talk]
Would this be a fit?
[Your name]
Pre-Podcast Prep
| Prep Item |
Details |
| Research the show |
Listen to 2-3 episodes, understand format |
| Research the host |
Their interests, style, Twitter |
| Prep talking points |
3-5 main things you want to say |
| Prep stories |
Specific examples, not generalities |
| Audio setup |
Good mic, quiet room, headphones |
| Water nearby |
You'll be talking a lot |
During the Podcast
| Do |
Don't |
| Tell stories with specifics |
Give generic advice |
| Pause before answering |
Um and ah nervously |
| Disagree respectfully |
Always agree to be polite |
| Promote subtly |
Hard sell your product |
| Be concise |
Ramble without structure |
| Show enthusiasm |
Be monotone |
Post-Podcast
| Action |
Timing |
| Thank the host |
Same day |
| Share when published |
Immediately |
| Engage with comments |
First week |
| Cross-promote |
Your newsletter, blog |
| Stay in touch |
Ongoing relationship |
Building in Public
What to Share
| Category |
Content Ideas |
| Progress |
"Shipped X today, here's what I learned" |
| Challenges |
"Stuck on X, tried Y and Z, here's what worked" |
| Decisions |
"Why we chose X over Y" |
| Metrics |
Revenue, users, growth (transparently) |
| Behind scenes |
Team, process, tools |
| Learnings |
"Mistake we made and how we fixed it" |
Build in Public Formats
| Format |
Platform |
Cadence |
| Tweet thread |
Twitter/X |
Daily-weekly |
| Changelog |
Blog, Notion, website |
Weekly |
| Indie hacker posts |
Indie Hackers, HN |
Monthly |
| Video update |
YouTube, Loom |
Weekly-monthly |
| Newsletter |
Email |
Weekly |
| Livestream |
Twitch, YouTube |
Weekly |
What NOT to Share
| Avoid |
Why |
| Customer data |
Privacy, trust |
| Team conflicts |
Professionalism |
| Security details |
Vulnerability |
| Competitor attacks |
Looks petty |
| Venting |
Not productive |
Social Presence (Twitter/X)
Developer Twitter Playbook
| Content Type |
% of Posts |
Example |
| Value content |
60% |
Tips, tutorials, insights |
| Engagement |
20% |
Replies, retweets with commentary |
| Personal |
10% |
Behind-the-scenes, personality |
| Promotion |
10% |
Your product, talks, content |
Tweet Formats That Work
| Format |
Example |
| Thread |
"10 things I learned building X" |
| Hot take |
"Unpopular opinion: [opinion]" |
| Quick tip |
"TIL: You can do X by..." |
| Question |
"What's your favorite way to..." |
| Meme/humor |
Tech jokes, relatable content |
| Showcase |
"Just shipped X, here's how it works" |
| Appreciation |
"Shoutout to @person for..." |
Engagement Strategy
| Action |
Frequency |
| Tweet original content |
Daily |
| Reply to others |
5-10x daily |
| Quote tweet with value |
2-3x weekly |
| DM interesting people |
Weekly |
| Join Twitter Spaces |
As relevant |
Growing Your Presence
| Tactic |
Implementation |
| Consistency |
Post daily, engage daily |
| Niche down |
Be known for ONE thing first |
| Reply game |
Add value to big accounts' tweets |
| Collaborate |
Twitter Spaces, threads together |
| Cross-promote |
Newsletter, talks, blog |
Measuring Impact
Advocacy Metrics
| Activity |
Metrics |
| Talks |
Attendees, feedback scores, recording views |
| Content |
Views, shares, engagement |
| Social |
Followers, engagement rate, reach |
| Podcasts |
Listener estimates, traffic spikes |
| Community |
Growth, engagement, sentiment |
Attribution Challenges
Developer advocacy impact is notoriously hard to measure. Proxy metrics:
| Signal |
What It Indicates |
| Traffic spikes |
Content/talk/podcast drove visits |
| "How did you hear about us?" |
Direct attribution |
| Social mentions |
Brand awareness |
| Inbound leads quality |
Community-qualified leads |
| Conference invites |
Growing reputation |
Reporting Framework
Monthly advocacy report:
# Developer Advocacy Report - [Month]
## Talks & Appearances
- [Talk 1]: [Conference], [Attendees], [Link]
- [Podcast 1]: [Show], [Episode link]
## Content Published
- [Article 1]: [Views], [Engagement]
- [Video 1]: [Views]
## Social Growth
- Twitter: +X followers, Y impressions
- Notable tweets: [Links]
## Community
- Discord/Slack: +X members, Y messages
- Notable threads/discussions
## Learnings
- What worked: [X]
- What didn't: [Y]
- Trying next: [Z]
Advocacy Career Path
Role Levels
| Level |
Focus |
| Junior DA |
Content creation, community support, talk prep |
| Developer Advocate |
Talks, own content strategy, community building |
| Senior DA |
Strategy, mentoring, major conferences |
| Staff DA |
Cross-company impact, industry thought leadership |
| Head of DevRel |
Team building, strategy, executive alignment |
Skill Development
| Skill |
How to Develop |
| Public speaking |
Meetups, Toastmasters, practice |
| Writing |
Blog consistently, get feedback |
| Video |
YouTube, live streaming, improve iteratively |
| Technical depth |
Build projects, contribute to OSS |
| Community |
Moderate, organize events, connect people |
Tools
| Tool |
Use Case |
| Octolens |
Monitor your name/brand across GitHub, Twitter, Reddit, HN, Stack Overflow. Track conference mentions. Find podcast opportunities. Measure share of voice. |
| Cal.com / Calendly |
Schedule podcast appearances |
| StreamYard |
Live streaming setup |
| Descript |
Video/podcast editing |
| Canva / Figma |
Slides and graphics |
| Otter.ai |
Transcription for talks |
| Notion |
Talk prep, content calendar |
| Buffer / Typefully |
Social scheduling |
Related Skills
developer-audience-context — Know who you're reachingdevrel-content — Written content strategycommunity-building — Community managementopen-source-marketing — OSS-specific advocacyhacker-news-strategy — HN engagement
Limitations
- Use this skill only when the task clearly matches its upstream source and local project context.
- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
1---2name: developer-advocacy3description: 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,"...4license: MIT5---67# 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| Approach | How |166|----------|-----|167| **Direct search** | "top [your tech] podcasts" |168| **Guest networks** | Podmatch, Matchmaker.fm |169| **Peer asks** | "What podcasts do you listen to?" |170| **Twitter search** | "[topic] podcast episode" |171| **Listen Notes** | Podcast search engine |172173### Pitch Template174175```176Subject: Guest Idea: [Specific Topic] for [Podcast Name]177178Hi [Host Name],179180I've been listening to [Podcast] for [time] — loved your episode on [specific episode].181182I'd love to come on and talk about [specific topic]. Here's the angle:183184[2-3 sentences on what you'd discuss and why it matters to their audience]185186A bit about me:187- [Relevant credential 1]188- [Relevant credential 2]189- [Link to past podcast/talk]190191Would this be a fit?192193[Your name]194```195196### Pre-Podcast Prep197198| Prep Item | Details |199|-----------|---------|200| **Research the show** | Listen to 2-3 episodes, understand format |201| **Research the host** | Their interests, style, Twitter |202| **Prep talking points** | 3-5 main things you want to say |203| **Prep stories** | Specific examples, not generalities |204| **Audio setup** | Good mic, quiet room, headphones |205| **Water nearby** | You'll be talking a lot |206207### During the Podcast208209| Do | Don't |210|----|-------|211| Tell stories with specifics | Give generic advice |212| Pause before answering | Um and ah nervously |213| Disagree respectfully | Always agree to be polite |214| Promote subtly | Hard sell your product |215| Be concise | Ramble without structure |216| Show enthusiasm | Be monotone |217218### Post-Podcast219220| Action | Timing |221|--------|--------|222| Thank the host | Same day |223| Share when published | Immediately |224| Engage with comments | First week |225| Cross-promote | Your newsletter, blog |226| Stay in touch | Ongoing relationship |227228---229230## Building in Public231232### What to Share233234| Category | Content Ideas |235|----------|---------------|236| **Progress** | "Shipped X today, here's what I learned" |237| **Challenges** | "Stuck on X, tried Y and Z, here's what worked" |238| **Decisions** | "Why we chose X over Y" |239| **Metrics** | Revenue, users, growth (transparently) |240| **Behind scenes** | Team, process, tools |241| **Learnings** | "Mistake we made and how we fixed it" |242243### Build in Public Formats244245| Format | Platform | Cadence |246|--------|----------|---------|247| **Tweet thread** | Twitter/X | Daily-weekly |248| **Changelog** | Blog, Notion, website | Weekly |249| **Indie hacker posts** | Indie Hackers, HN | Monthly |250| **Video update** | YouTube, Loom | Weekly-monthly |251| **Newsletter** | Email | Weekly |252| **Livestream** | Twitch, YouTube | Weekly |253254### What NOT to Share255256| Avoid | Why |257|-------|-----|258| **Customer data** | Privacy, trust |259| **Team conflicts** | Professionalism |260| **Security details** | Vulnerability |261| **Competitor attacks** | Looks petty |262| **Venting** | Not productive |263264---265266## Social Presence (Twitter/X)267268### Developer Twitter Playbook269270| Content Type | % of Posts | Example |271|--------------|------------|---------|272| **Value content** | 60% | Tips, tutorials, insights |273| **Engagement** | 20% | Replies, retweets with commentary |274| **Personal** | 10% | Behind-the-scenes, personality |275| **Promotion** | 10% | Your product, talks, content |276277### Tweet Formats That Work278279| Format | Example |280|--------|---------|281| **Thread** | "10 things I learned building X" |282| **Hot take** | "Unpopular opinion: [opinion]" |283| **Quick tip** | "TIL: You can do X by..." |284| **Question** | "What's your favorite way to..." |285| **Meme/humor** | Tech jokes, relatable content |286| **Showcase** | "Just shipped X, here's how it works" |287| **Appreciation** | "Shoutout to @person for..." |288289### Engagement Strategy290291| Action | Frequency |292|--------|-----------|293| Tweet original content | Daily |294| Reply to others | 5-10x daily |295| Quote tweet with value | 2-3x weekly |296| DM interesting people | Weekly |297| Join Twitter Spaces | As relevant |298299### Growing Your Presence300301| Tactic | Implementation |302|--------|----------------|303| **Consistency** | Post daily, engage daily |304| **Niche down** | Be known for ONE thing first |305| **Reply game** | Add value to big accounts' tweets |306| **Collaborate** | Twitter Spaces, threads together |307| **Cross-promote** | Newsletter, talks, blog |308309---310311## Measuring Impact312313### Advocacy Metrics314315| Activity | Metrics |316|----------|---------|317| **Talks** | Attendees, feedback scores, recording views |318| **Content** | Views, shares, engagement |319| **Social** | Followers, engagement rate, reach |320| **Podcasts** | Listener estimates, traffic spikes |321| **Community** | Growth, engagement, sentiment |322323### Attribution Challenges324325Developer advocacy impact is notoriously hard to measure. Proxy metrics:326327| Signal | What It Indicates |328|--------|-------------------|329| **Traffic spikes** | Content/talk/podcast drove visits |330| **"How did you hear about us?"** | Direct attribution |331| **Social mentions** | Brand awareness |332| **Inbound leads quality** | Community-qualified leads |333| **Conference invites** | Growing reputation |334335### Reporting Framework336337Monthly advocacy report:338339```markdown340# Developer Advocacy Report - [Month]341342## Talks & Appearances343- [Talk 1]: [Conference], [Attendees], [Link]344- [Podcast 1]: [Show], [Episode link]345346## Content Published347- [Article 1]: [Views], [Engagement]348- [Video 1]: [Views]349350## Social Growth351- Twitter: +X followers, Y impressions352- Notable tweets: [Links]353354## Community355- Discord/Slack: +X members, Y messages356- Notable threads/discussions357358## Learnings359- What worked: [X]360- What didn't: [Y]361- Trying next: [Z]362```363364---365366## Advocacy Career Path367368### Role Levels369370| Level | Focus |371|-------|-------|372| **Junior DA** | Content creation, community support, talk prep |373| **Developer Advocate** | Talks, own content strategy, community building |374| **Senior DA** | Strategy, mentoring, major conferences |375| **Staff DA** | Cross-company impact, industry thought leadership |376| **Head of DevRel** | Team building, strategy, executive alignment |377378### Skill Development379380| Skill | How to Develop |381|-------|----------------|382| **Public speaking** | Meetups, Toastmasters, practice |383| **Writing** | Blog consistently, get feedback |384| **Video** | YouTube, live streaming, improve iteratively |385| **Technical depth** | Build projects, contribute to OSS |386| **Community** | Moderate, organize events, connect people |387388---389390## Tools391392| Tool | Use Case |393|------|----------|394| **[Octolens](https://octolens.com)** | Monitor your name/brand across GitHub, Twitter, Reddit, HN, Stack Overflow. Track conference mentions. Find podcast opportunities. Measure share of voice. |395| **Cal.com / Calendly** | Schedule podcast appearances |396| **StreamYard** | Live streaming setup |397| **Descript** | Video/podcast editing |398| **Canva / Figma** | Slides and graphics |399| **Otter.ai** | Transcription for talks |400| **Notion** | Talk prep, content calendar |401| **Buffer / Typefully** | Social scheduling |402403---404405## Related Skills406407- `developer-audience-context` — Know who you're reaching408- `devrel-content` — Written content strategy409- `community-building` — Community management410- `open-source-marketing` — OSS-specific advocacy411- `hacker-news-strategy` — HN engagement412413## Limitations414415- Use this skill only when the task clearly matches its upstream source and local project context.416- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.417- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.
humaisali