Plan and Execute Developer Advocacy Campaigns

Comprehensive guidance for developer advocacy activities - conference talks, live coding demos, podcast appearances, and building in public - covering talk proposals, demo prep, social presence, and measuring impact. It requires loading audience context first from .agents/developer-audience-context.md, or running a separate developer-audience-context skill if that file doesn't exist, to know who to reach, what topics resonate, product positioning, and voice and tone. For conference talks it maps five conference types to their best use - large industry, regional, niche, company-hosted, unconferences - gives a CFP formula:

Specific Problem + Unique Angle + Clear Takeaways = Accepted Talk

alongside a full CFP template covering title, abstract, description, timed outline, audience, and bio, six title patterns that work such as "How I X" or "X in Y Minutes," a talk-type table by length from 5-10 minute lightning talks through 2-4 hour workshops, and a six-phase prep checklist from two months out through day-of. For live coding it names six demo failure risks with mitigations - internet failure, typo freezes, unfixable errors, running over time, illegible code, blinding dark themes - a "10-3-1 rule" of practicing ten times with three checkpoints and one backup recording, a seven-item pre-demo checklist, and live-coding delivery tips like typing slowly, narrating, explaining errors, and using checkpoint commits. For podcast guesting it covers finding shows through direct search, guest networks like Podmatch or Matchmaker.fm, peer asks, and Listen Notes, a full pitch email template, pre-podcast research and prep, do/don't behavior during the recording, and a post-podcast follow-up sequence. For building in public it lists what to share - progress, challenges, decisions, metrics, behind-the-scenes, learnings - versus what never to share - customer data, team conflicts, security details, competitor attacks, venting - and six formats with typical cadence. For social presence on Twitter/X it gives a content-mix playbook of 60% value, 20% engagement, 10% personal, 10% promotion, seven tweet formats that work, an engagement-frequency table, and growth tactics like consistency, niching down, replying to big accounts, and collaboration. It closes with advocacy metrics per activity type, a proxy-metric table for the notoriously hard attribution problem, a monthly reporting template, a five-level DevRel career ladder from Junior DA to Head of DevRel with skill-development paths, and a named tools list including Octolens for brand and mention monitoring, Cal.com/Calendly, StreamYard, Descript, Canva/Figma, Otter.ai, Notion, and Buffer/Typefully.

Use it when the user wants to do developer advocacy activities including conference talks, live coding, podcasts, or building in public. It explicitly defers related work to sibling skills rather than covering it itself: developer-audience-context for audience research, devrel-content for written content strategy, community-building for community management, open-source-marketing for OSS-specific advocacy, and hacker-news-strategy for HN engagement.

Input is a developer-advocacy activity to plan - a talk proposal, a live-coding demo, a podcast pitch, a build-in-public post, a social strategy - plus the loaded audience-context file. Output is the corresponding artifact, a filled CFP submission, a demo prep checklist, a podcast pitch email, or a monthly advocacy report, following the documented templates and frameworks.

References a companion .agents/developer-audience-context.md file and skill, plus named external tools for monitoring (Octolens), scheduling (Cal.com/Calendly), streaming (StreamYard), editing (Descript), design (Canva/Figma), transcription (Otter.ai), planning (Notion), and social scheduling (Buffer/Typefully).

Developer advocates, DevRel practitioners, and founders building a public technical presence who need concrete templates and checklists for talks, demos, podcasts, and social growth rather than generic advice.