Devrel Content skills for AI agents

Write engineering blog posts that bring traffic, build trust, and inform the technical decisions of readers. Covers the post taxonomy (incident report, deep dive, architecture decision), structure, the SEO-without-being-cheesy discipline, and the publication cadence that builds a reputation. Use when launching or sustaining a technical blog.

Plan, write, and deliver a 25–45 minute developer conference talk that builds your company's reputation while genuinely helping the audience. Covers topic selection, structure, the demo discipline, slide design, and the difference between a talk that lands and a talk that empties the room. Use when accepting a CFP or building a talk for major conferences.

Run an open-source community around a project — issue triage, PR review, release notes, contributor recognition, governance. The discipline that turns "we open-sourced our code" into "we have a thriving project people want to contribute to." Use when starting or operating an OSS project that aspires to be more than a code dump.

Prepare for technical talks, podcasts, panels, and AMAs. Covers rehearsal discipline, vocal delivery, anxiety management, and the difference between preparing for a talk you've given before vs. one you're giving for the first time. Use when scheduled to speak in any recorded or live technical setting.

Write tutorials that get developers to working code in their first 20 minutes with your product. Covers the structure, the discipline of the runnable example, the difference between tutorials and reference, and the maintenance discipline that keeps tutorials from rotting. Use when introducing new developers to a product, library, or framework.