1---
2name: developer-advocacy
3description: "Plans DevRel work: conference CFPs, talk prep, live-coding demos (10-3-1 checkpoints), podcast pitches, building-in-public, and advocacy metrics. Use when the user mentions developer advocacy, DevRel, CFP, conference talk, live coding, podcast guesting, or building in public. Not for product marketing copy, authoring SKILL.md, or implementing the product. Never skip audience context or share customer or security data while building in public."
4version: 1.0.1
5risk: unknown
6source: https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-advocacy
7source_repo: jonathimer/devmarketing-skills
8source_type: community
9date_added: 2026-07-01
10license: MIT
11license_source: https://github.com/jonathimer/devmarketing-skills/blob/main/LICENSE
12metadata:
13 source: https://skillmd.com/skills/kayforkind/developer-advocacy
14---
15
16# Developer Advocacy
17
18## When to Use
19
20Use this skill when the user wants to plan or execute developer advocacy activities. Trigger phrases include:
21
22- "developer advocacy" / "devrel"
23- "conference talk" / "CFP" / "call for papers"
24- "live coding" / "demo prep"
25- "podcast" / "podcast pitch"
26- "building in public" / "social presence"
27- "advocacy metrics" / "advocacy report"
28
29This skill covers the full advocacy lifecycle: finding conferences, writing talk proposals, preparing live demos, pitching and appearing on podcasts, building in public, managing social presence, and measuring impact.
30
31## Prerequisites
32
331. **Load audience context first.** Before any advocacy work, read `.agents/developer-audience-context.md` to understand:
34 - Who you're trying to reach (conferences they attend, podcasts they listen to)
35 - What topics resonate (pain points, interests)
36 - Your product's positioning (what story to tell)
37 - Voice & tone (how formal/technical to be)
38
392. If the context file does not exist, run the `developer-audience-context` skill first to generate it.
40
413. **Templates live in this skill.** Use them at these moments:
42 - Conference talk proposal — CFP template in §1.2.
43 - Live coding demo — pre-demo checklist in §2.2.
44 - Podcast guest pitch — pitch template in §3.2.
45 - Monthly advocacy report — report template in §6.3.
46
47## Procedure
48
49### 1. Conference Talks
50
51#### 1.1 Finding the Right Conferences
52
53| Conference Type | Best For | Examples |
54|-----------------|----------|----------|
55| **Large industry** | Brand awareness, reach | KubeCon, AWS re:Invent, React Summit |
56| **Regional** | Local community, accessible | Local meetups, city tech conferences |
57| **Niche** | Targeted audience, expertise | GraphQL Conf, RustConf |
58| **Company-hosted** | Ecosystem presence | Vercel Ship, GitHub Universe |
59| **Unconferences** | Community connection | BarCamps, DevOpsDays |
60
61#### 1.2 Writing a Talk Proposal (CFP)
62
63**Winning formula:**
64
65```
66Specific Problem + Unique Angle + Clear Takeaways = Accepted Talk
67```
68
69**CFP Template:**
70
71```markdown
72# Title
73[Action verb] + [specific outcome] + [with/using what]
74Example: "Building Real-Time Features with Edge Functions and WebSockets"
75
76# Abstract (100-200 words)
77[Hook: Problem or curiosity gap]
78[What you'll cover]
79[What attendees will learn/be able to do]
80
81# Description (detailed, for reviewers)
82[Problem context]
83[Why this approach]
84[Talk structure]
85[Your credibility to give this talk]
86
87# Outline
88- [Time] Introduction / Problem statement
89- [Time] Section 1
90- [Time] Section 2
91- [Time] Section 3
92- [Time] Live demo / walkthrough
93- [Time] Key takeaways / Q&A
94
95# Audience
96[Who this is for]
97[Prerequisite knowledge]
98[What they'll learn]
99
100# Bio
101[Your relevant experience]
102[Why you're qualified]
103```
104
105**Title patterns that work:**
106
107| Pattern | Example |
108|---------|---------|
109| **How I X** | "How I Reduced Deploy Time by 80%" |
110| **X in Y Minutes** | "Kubernetes Security in 15 Minutes" |
111| **The X of Y** | "The Psychology of Error Messages" |
112| **Beyond X** | "Beyond Console.log: Modern Debugging" |
113| **X for Y** | "GraphQL for REST Developers" |
114| **Lessons from X** | "Lessons from 1000 Production Outages" |
115
116**Talk types:**
117
118| Type | Length | Best For |
119|------|--------|----------|
120| **Lightning** | 5-10 min | Single concept, quick demo |
121| **Standard** | 25-45 min | Technical deep-dive |
122| **Keynote** | 45-60 min | Big picture, inspiring |
123| **Workshop** | 2-4 hours | Hands-on learning |
124| **Panel** | 30-60 min | Discussion, multiple perspectives |
125
126#### 1.3 Talk Prep Checklist
127
128| Phase | Tasks |
129|-------|-------|
130| **2 months before** | Outline, start slides, test demos |
131| **1 month before** | Draft complete, first practice run |
132| **2 weeks before** | Slides polished, demos solid, practice 3x |
133| **1 week before** | Record yourself, get feedback, finalize |
134| **Day before** | Test all tech, backup slides, rest |
135| **Day of** | Arrive early, test A/V, hydrate |
136
137### 2. Live Coding & Demos
138
139#### 2.1 The 10-3-1 Rule
140
141- Run your demo **10 times** in practice
142- Have **3 checkpoints** you can jump to if stuck
143- **1 backup** (video recording of it working)
144
145#### 2.2 Pre-Demo Checklist
146
147- [ ] Close unnecessary apps
148- [ ] Clear browser history/tabs
149- [ ] Notifications OFF (Slack, email, calendar)
150- [ ] Font size: 24pt+ for terminal, 20pt+ for editor
151- [ ] Git stash/branch for clean starting point
152- [ ] Environment variables ready
153- [ ] Test on the actual projector/screen if possible
154
155#### 2.3 Demo Danger Zone — Risk Mitigation
156
157| Risk | Mitigation |
158|------|------------|
159| **Internet fails** | Pre-record backup, local server |
160| **Typo freezes you** | Practice typing same code 20x |
161| **Error you can't fix** | Have working checkpoints to jump to |
162| **Runs over time** | Time yourself, cut ruthlessly |
163| **Code too small** | Zoom in, use large font (24pt+) |
164| **Dark theme blinding** | Use high-contrast, light-friendly theme |
165
166#### 2.4 Live Coding Tips
167
168| Tip | Why |
169|-----|-----|
170| **Type slowly** | Audience needs to follow |
171| **Narrate what you type** | "I'm creating a new handler..." |
172| **Explain errors** | "This error means X, let me fix it" |
173| **Use snippets** | For boilerplate, not core concepts |
174| **Show the result** | Always run the code, show output |
175| **Checkpoint commits** | `git checkout checkpoint-1` |
176
177### 3. Podcast Guesting
178
179#### 3.1 Finding Podcasts
180
181| Approach | How |
182|----------|-----|
183| **Direct search** | "top [your tech] podcasts" |
184| **Guest networks** | Podmatch, Matchmaker.fm |
185| **Peer asks** | "What podcasts do you listen to?" |
186| **Twitter search** | "[topic] podcast episode" |
187| **Listen Notes** | Podcast search engine |
188
189#### 3.2 Pitch Template
190
191```
192Subject: Guest Idea: [Specific Topic] for [Podcast Name]
193
194Hi [Host Name],
195
196I've been listening to [Podcast] for [time] — loved your episode on [specific episode].
197
198I'd love to come on and talk about [specific topic]. Here's the angle:
199
200[2-3 sentences on what you'd discuss and why it matters to their audience]
201
202A bit about me:
203- [Relevant credential 1]
204- [Relevant credential 2]
205- [Link to past podcast/talk]
206
207Would this be a fit?
208
209[Your name]
210```
211
212#### 3.3 Pre-Podcast Prep
213
214| Prep Item | Details |
215|-----------|---------|
216| **Research the show** | Listen to 2-3 episodes, understand format |
217| **Research the host** | Their interests, style, Twitter |
218| **Prep talking points** | 3-5 main things you want to say |
219| **Prep stories** | Specific examples, not generalities |
220| **Audio setup** | Good mic, quiet room, headphones |
221| **Water nearby** | You'll be talking a lot |
222
223#### 3.4 During the Podcast
224
225| Do | Don't |
226|----|-------|
227| Tell stories with specifics | Give generic advice |
228| Pause before answering | Um and ah nervously |
229| Disagree respectfully | Always agree to be polite |
230| Promote subtly | Hard sell your product |
231| Be concise | Ramble without structure |
232| Show enthusiasm | Be monotone |
233
234#### 3.5 Post-Podcast
235
236| Action | Timing |
237|--------|--------|
238| Thank the host | Same day |
239| Share when published | Immediately |
240| Engage with comments | First week |
241| Cross-promote | Your newsletter, blog |
242| Stay in touch | Ongoing relationship |
243
244### 4. Building in Public
245
246#### 4.1 What to Share
247
248| Category | Content Ideas |
249|----------|---------------|
250| **Progress** | "Shipped X today, here's what I learned" |
251| **Challenges** | "Stuck on X, tried Y and Z, here's what worked" |
252| **Decisions** | "Why we chose X over Y" |
253| **Metrics** | Revenue, users, growth (transparently) |
254| **Behind scenes** | Team, process, tools |
255| **Learnings** | "Mistake we made and how we fixed it" |
256
257#### 4.2 Build in Public Formats
258
259| Format | Platform | Cadence |
260|--------|----------|---------|
261| **Tweet thread** | Twitter/X | Daily-weekly |
262| **Changelog** | Blog, Notion, website | Weekly |
263| **Indie hacker posts** | Indie Hackers, HN | Monthly |
264| **Video update** | YouTube, Loom | Weekly-monthly |
265| **Newsletter** | Email | Weekly |
266| **Livestream** | Twitch, YouTube | Weekly |
267
268#### 4.3 What NOT to Share
269
270| Avoid | Why |
271|-------|-----|
272| **Customer data** | Privacy, trust |
273| **Team conflicts** | Professionalism |
274| **Security details** | Vulnerability |
275| **Competitor attacks** | Looks petty |
276| **Venting** | Not productive |
277
278### 5. Social Presence (Twitter/X)
279
280#### 5.1 Content Mix
281
282| Content Type | % of Posts | Example |
283|--------------|------------|---------|
284| **Value content** | 60% | Tips, tutorials, insights |
285| **Engagement** | 20% | Replies, retweets with commentary |
286| **Personal** | 10% | Behind-the-scenes, personality |
287| **Promotion** | 10% | Your product, talks, content |
288
289#### 5.2 Tweet Formats That Work
290
291| Format | Example |
292|--------|---------|
293| **Thread** | "10 things I learned building X" |
294| **Hot take** | "Unpopular opinion: [opinion]" |
295| **Quick tip** | "TIL: You can do X by..." |
296| **Question** | "What's your favorite way to..." |
297| **Meme/humor** | Tech jokes, relatable content |
298| **Showcase** | "Just shipped X, here's how it works" |
299| **Appreciation** | "Shoutout to @person for..." |
300
301#### 5.3 Engagement Strategy
302
303| Action | Frequency |
304|--------|-----------|
305| Tweet original content | Daily |
306| Reply to others | 5-10x daily |
307| Quote tweet with value | 2-3x weekly |
308| DM interesting people | Weekly |
309| Join Twitter Spaces | As relevant |
310
311#### 5.4 Growing Your Presence
312
313| Tactic | Implementation |
314|--------|----------------|
315| **Consistency** | Post daily, engage daily |
316| **Niche down** | Be known for ONE thing first |
317| **Reply game** | Add value to big accounts' tweets |
318| **Collaborate** | Twitter Spaces, threads together |
319| **Cross-promote** | Newsletter, talks, blog |
320
321### 6. Measuring Impact
322
323#### 6.1 Advocacy Metrics
324
325| Activity | Metrics |
326|----------|---------|
327| **Talks** | Attendees, feedback scores, recording views |
328| **Content** | Views, shares, engagement |
329| **Social** | Followers, engagement rate, reach |
330| **Podcasts** | Listener estimates, traffic spikes |
331| **Community** | Growth, engagement, sentiment |
332
333#### 6.2 Attribution Signals
334
335Developer advocacy impact is notoriously hard to measure. Use these proxy metrics:
336
337| Signal | What It Indicates |
338|--------|-------------------|
339| **Traffic spikes** | Content/talk/podcast drove visits |
340| **"How did you hear about us?"** | Direct attribution |
341| **Social mentions** | Brand awareness |
342| **Inbound leads quality** | Community-qualified leads |
343| **Conference invites** | Growing reputation |
344
345#### 6.3 Monthly Advocacy Report
346
347```markdown
348# Developer Advocacy Report - [Month]
349
350## Talks & Appearances
351- [Talk 1]: [Conference], [Attendees], [Link]
352- [Podcast 1]: [Show], [Episode link]
353
354## Content Published
355- [Article 1]: [Views], [Engagement]
356- [Video 1]: [Views]
357
358## Social Growth
359- Twitter: +X followers, Y impressions
360- Notable tweets: [Links]
361
362## Community
363- Discord/Slack: +X members, Y messages
364- Notable threads/discussions
365
366## Learnings
367- What worked: [X]
368- What didn't: [Y]
369- Trying next: [Z]
370```
371
372### 7. Advocacy Career Path
373
374| Level | Focus |
375|-------|-------|
376| **Junior DA** | Content creation, community support, talk prep |
377| **Developer Advocate** | Talks, own content strategy, community building |
378| **Senior DA** | Strategy, mentoring, major conferences |
379| **Staff DA** | Cross-company impact, industry thought leadership |
380| **Head of DevRel** | Team building, strategy, executive alignment |
381
382| Skill | How to Develop |
383|-------|----------------|
384| **Public speaking** | Meetups, Toastmasters, practice |
385| **Writing** | Blog consistently, get feedback |
386| **Video** | YouTube, live streaming, improve iteratively |
387| **Technical depth** | Build projects, contribute to OSS |
388| **Community** | Moderate, organize events, connect people |
389
390### 8. Tools
391
392| 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 |
402
403## Pitfalls
404
405- **Skipping audience context.** Writing a CFP or pitch without loading `.agents/developer-audience-context.md` leads to generic proposals that get rejected. Always load context first.
406- **No demo backup.** Live demos fail. If you have no pre-recorded fallback or checkpoint commits, you risk a blank screen in front of hundreds of attendees. Follow the 10-3-1 rule.
407- **Hard-selling on podcasts.** Overt product pitches damage host relationships and reduce future invitations. Promote subtly; lead with value and stories.
408- **Oversharing sensitive data.** Never share customer data, security details, or team conflicts when building in public. This breaks privacy, trust, and professionalism.
409- **Ignoring attribution.** Advocacy without measurement is invisible to leadership. Always include proxy metrics and "how did you hear about us?" tracking in your reporting.
410- **Inconsistent social presence.** Posting in bursts then going silent kills algorithmic reach. Post daily and engage daily for sustained growth.
411- **Under-practicing talks.** One practice run is not enough. Aim for 3 full run-throughs in the final 2 weeks, plus a recording for self-review.
412
413## Verification
414
4151. **Audience context loaded:**
416 ```powershell
417 Test-Path .agents\developer-audience-context.md
418 ```
419 Expected output: `True`. If `False`, run the `developer-audience-context` skill first.
420
4212. **CFP completeness check** — Confirm your proposal has all required sections:
422 ```powershell
423 Select-String -Path .\cfp-draft.md -Pattern "^# (Title|Abstract|Description|Outline|Audience|Bio)"
424 ```
425 Expected: 6 matching lines. If fewer, add the missing sections.
426
4273. **Demo checkpoint commits exist:**
428 ```powershell
429 git tag --list "checkpoint-*"
430 ```
431 Expected: at least 3 tags (e.g., `checkpoint-1`, `checkpoint-2`, `checkpoint-3`).
432
4334. **Font size for live coding** — Verify terminal and editor fonts are 24pt+ and 20pt+ respectively before the talk. Visually confirm on the projector if possible.
434
4355. **Monthly report generated** — Confirm the report file exists and contains all sections:
436 ```powershell
437 Select-String -Path .\advocacy-report.md -Pattern "^## (Talks & Appearances|Content Published|Social Growth|Community|Learnings)"
438 ```
439 Expected: 5 matching lines.
440
441## Related Skills
442
443- `developer-audience-context` — Know who you're reaching
444- `devrel-content` — Written content strategy
445- `community-building` — Community management
446- `open-source-marketing` — OSS-specific advocacy
447- `hacker-news-strategy` — HN engagement
448
449## Limitations
450
451- Use this skill only when the task clearly matches its upstream source and local project context.
452- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
453- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.