devrel-content

Create technical content developers actually read.

What It Does

Guides you through creating blog posts, tutorials, and documentation that resonate with developers. Covers research, structure, code examples, technical accuracy, and SEO.

When to Use

Writing a technical blog post
Creating documentation or guides
Building thought leadership content
When you say "write a blog post," "technical article," "developer content," or "tutorial"

Quick Start

/devrel-content

Write a blog post about implementing rate limiting in Node.js.
Target: backend developers building APIs.

The skill will:

Load your developer audience context
Help you research and validate the topic
Guide you through the outline and structure
Ensure code examples are copy-paste ready
Check technical accuracy and SEO

Key Frameworks

Content Quality Signals

Show, don't tell — Code over prose
Address the "why" — Not just how, but when and why
Acknowledge tradeoffs — Developers respect honesty
Progressive disclosure — Start simple, add complexity

Code Example Requirements

Every code snippet must:

Run without modification
Include all imports
Show expected output
Handle errors properly
Use real values (not foo, bar)

SEO for Developers

Developers search differently:

Error messages ("TypeError: Cannot read property...")
How-to queries ("how to deploy next.js")
Comparisons ("prisma vs typeorm 2024")
Best practices ("typescript project structure")

Files

File	Description
`SKILL.md`	Full skill instructions with templates

Templates Included

Blog post structure
Comparison post format
Technical accuracy checklist
SEO optimization checklist

Tools

Octolens — Monitor where content gets shared and find ideas from developer conversations
Ahrefs/SEMrush — Keyword research
Carbon/Ray.so — Code screenshots

developer-audience-context — Know your readers first
technical-tutorials — Step-by-step deep dives
developer-newsletter — Distribute via email

README.md