Technical Article Writer

This is a full pipeline for writing technical blog posts and articles that don't suck. It starts by interviewing you about topic, audience, content type, and conversion goal before writing a word, then walks through title generation, hook writing (delegates to a separate copywriting skill), and structured drafting based on templates like "The Bug Hunt" or "How We Built It." The philosophy is tight: developer audiences smell BS, most articles fail structurally not conceptually, and the best content comes from what you struggled with rather than what you mastered. Built on frameworks from Julia Evans and Julian Shapiro. If you've ever stared at a half-written draft wondering why it feels flat, this gives you the questions you should have asked yourself two hours ago.

skills.sh installs: 5.5K
GitHub stars: 242
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add samber/cc-skills --skill technical-article-writer --agent claude-code

Installs into .claude/skills of the current project.

Files

Questions: Ask the user through the environment's question tool — never as plain-text prose. One question at a time, 2–4 tappable options, wait for the answer. If the environment has no question tool, ask in prose with the same options, one at a time.

Technical Article Writer

Write technical articles that developers actually want to read. This skill combines structural frameworks from technical writing, hook engineering from copywriting, and practitioner-tested patterns for developer content.

Core philosophy

Most technical articles fail because of structural problems, not bad ideas: burying the lede, mixing content types, weak openings, no clear motivation, or trying to cover too much.

Developer audiences have a built-in BS detector. The best technical content leads with specificity and honesty. It sounds like a smart colleague explaining something interesting, not a marketer pitching. Acknowledge your expertise level, solve a specific problem, use real examples.

Not for reference documentation aimed at non-native readers or machine translation (→ See samber/cc-skills@humanizer-en-asd-ste100 skill for ASD-STE100 Simplified Technical English).