| name | developer-advocacy |
| description | 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,"... |
| risk | unknown |
| source | https://github.com/jonathimer/devmarketing-skills/tree/main/skills/developer-advocacy |
| source_repo | jonathimer/devmarketing-skills |
| source_type | community |
| date_added | 2026-07-01T00:00:00.000Z |
| license | MIT |
| license_source | https://github.com/jonathimer/devmarketing-skills/blob/main/LICENSE |
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]
[Time] Introduction / Problem statement
[Time] Section 1
[Time] Section 2
[Time] Section 3
[Time] Live demo / walkthrough
[Time] Key takeaways / Q&A
[Who this is for]
[Prerequisite knowledge]
[What they'll learn]
[Your relevant experience]
[Why you're qualified]
