Create Technical Content That Developers Actually Read

This skill guides creation of technical content that developers actually read - blog posts, tutorials, documentation, and thought leadership - built around a repeatable framework. It starts by loading audience context (role, seniority, tech stack, pain points, verbatim language, and voice and tone from a developer-audience-context file) before any writing begins. Phase one is research and validation: checking search intent, community signals on Reddit, Hacker News, and Stack Overflow, competitor content gaps, internal signals from support tickets and Discord and GitHub issues, and keyword search volume, while flagging red-flag topics that are already oversaturated, too broad, or too narrow to have any audience. Phase two selects the right content type for the goal - tutorial, guide, comparison, announcement, thought leadership, case study, or troubleshooting - each mapped to a best-for use case and structure. Phase three provides a full outline template: a value-promising title, a hook establishing credibility and promising a specific payoff, optional context, three or more meat sections each with explanation, code example, and pitfall or application, a complete working example, and a what's-next section with links and a call to action.

Code-example guidance enforces a copy-paste test - every snippet must run unmodified, include imports, show expected output, handle errors, and use realistic values instead of placeholder names - illustrated with a full install-code-run-output example, plus a per-language table of code-block tags, install commands, and environment-variable conventions for JavaScript, TypeScript, Python, Go, Rust, and shell. A technical accuracy checklist covers running every snippet, verifying current library versions, checking every link and CLI command, confirming screenshots and APIs aren't outdated, a security pass for hardcoded secrets, and peer review by an engineer. SEO guidance covers developer-specific search patterns - error messages, how-to queries, comparisons, best-practices, and alternatives-to searches - plus a technical SEO checklist for titles, meta descriptions, headings, code-block syntax highlighting, and internal and external linking, with before-and-after examples of vague versus keyword-rich titles. Quality signals separate strong devrel writing (code over prose, addressing the why, acknowledging tradeoffs, dated content, progressive disclosure, real production examples) from weak writing (walls of text, marketing speak, assumed knowledge, outdated content, buried answers, no code). Full blog-post and tool-comparison templates are provided in markdown, and content success is measured through page views, time on page, scroll depth, bounce rate, search rankings, backlinks, social shares, and conversion events tracked along a search-to-activation path.

Use it when creating technical content for developers - blog posts, tutorials, documentation, or thought leadership - especially where SEO performance and developer trust both matter.

Given a content topic and audience context, it produces a validated topic decision, a chosen content type and outline, copy-paste-ready code examples, and a pre-publish technical accuracy and SEO checklist.

Related skills for audience context, technical tutorials, developer newsletters, and Hacker News strategy; tools including content-monitoring services, Grammarly or Hemingway, code-screenshot tools, Excalidraw, Loom, Ahrefs or SEMrush, and Google Search Console.

Developer relations and technical content writers who need a repeatable framework for validating, structuring, and quality-checking content before it goes live.