Plan and Execute Developer Advocacy Campaigns

This skill supports developer advocacy work: conference talk proposals and prep, live-coding demo safety, podcast guesting, building in public, developer-focused social presence, and measuring advocacy impact. Before starting, it loads audience context from .agents/developer-audience-context.md (who you're reaching, what resonates, product positioning, voice/tone), running the developer-audience-context skill first if that file doesn't exist.

Use it on trigger phrases like "developer advocacy," "devrel," "conference talk," "CFP," "live coding," "podcast," or "building in public." It covers writing a CFP (Title + Abstract + Description + Outline + Audience + Bio) using the formula Specific Problem + Unique Angle + Clear Takeaways, picking a title pattern ("How I X," "X in Y Minutes," "Beyond X"), choosing a talk length (5-10 min lightning to 2-4 hour workshop) and matching conference type (large industry, regional, niche, company-hosted, unconference) to the goal, running a live-coding demo safely via the 10-3-1 rule (practice 10 times, 3 checkpoints, 1 backup recording), pitching and prepping for a podcast appearance, and deciding what to share vs withhold when building in public.

Produces a CFP submission (structured per the template above), a talk-prep timeline (2 months out through day-of), a demo pre-flight checklist (font size 24pt+/20pt+, notifications off, git checkpoint commits, tested on the actual screen), a podcast pitch email, and a monthly advocacy report (talks/appearances, content published, social growth, community, learnings). It explicitly lists what NOT to share when building in public: customer data, team conflicts, security details, competitor attacks, venting. Because advocacy impact is notoriously hard to attribute directly, it tracks proxy signals instead: traffic spikes after a talk or podcast, how-did-you-hear-about-us answers, social mentions, inbound lead quality, and conference invites.

Names specific tools by use case: Octolens for monitoring brand mentions and finding podcast opportunities, Cal.com/Calendly for scheduling, StreamYard for live streaming, Descript for video/podcast editing, Canva/Figma for slides, Otter.ai for transcription, Notion for talk prep and content calendars, and Buffer/Typefully for social scheduling. A Twitter/X playbook allocates post mix (60% value content, 20% engagement, 10% personal, 10% promotion), and recommends growing a presence by niching down to one topic first, adding value in replies to bigger accounts, and collaborating via joint Twitter Spaces or threads, rather than posting into a vacuum. It names related skills to chain with - devrel-content, community-building, open-source-marketing, hacker-news-strategy.

Developer advocates and DevRel practitioners at any career stage (Junior DA through Head of DevRel) preparing a conference talk, podcast appearance, or public-building content plan, who need concrete templates and checklists rather than generic advice on "getting your name out there." It maps a career ladder from Junior DA (content creation, community support, talk prep) through Developer Advocate, Senior DA, Staff DA, to Head of DevRel, and names how to build each underlying skill - public speaking via meetups/Toastmasters/practice, writing by blogging consistently and getting feedback, video by iterating on YouTube/live streaming, technical depth by building projects and contributing to open source, and community skills by moderating and organizing events.