technical-blog-writing — Claude Code skill: technical blog posts
technical-blog-writing sets the skeleton for a dev-facing post: article types, rules for code samples, and depth matched to the reader. Useful when a tutorial or architecture write-up has to ship.
no license 237 installs ★ 31 updated 2026-08-31
npx skills add 101-skills/superpowers --skill technical-blog-writing -a claude-codeWhat technical-blog-writing does
Each post shape arrives with its own section order. Tutorial, postmortem, benchmark comparison, architecture write-up: pick one and follow the outline from problem statement through results to links on the full code.
Code samples carry the tightest rules. Blocks have to run, dependency versions get pinned, output follows the snippet. A separate table names what irritates developers: warm-up filler, “simply do X”, calling something obvious. Depth tracks the audience you declare up front, so a beginner walkthrough spells out every step while a tool comparison skips fundamentals.
Topic research and the header image run through belt, the inference.sh CLI. Log in with belt login first, and install the CLI separately using npx skills add belt-sh/cli. Those two steps fail without it, since allowed-tools is capped at Bash(belt *) and no other shell command is in reach.
What it helps with
- draft a tutorial whose code blocks actually run
- turn an outage into a postmortem with a timeline and root cause
- compare two tools with a stated method and real numbers
- cut warm-up filler and marketing tone out of a draft
- set explanation depth for the reader you name
Example prompts for the agent
- Write a technical post about moving to connection pooling: tutorial structure, runnable samples, pinned dependency versions.
- Turn last night's outage into a postmortem — timeline, root cause, what we changed.
- Rewrite this draft's intro without the warm-up; the reader should learn what we built in the first line.
How to install technical-blog-writing
1Skills CLI (Vercel)
npx skills add 101-skills/superpowers --skill technical-blog-writing -a claude-code2Manually: put the files in place
~/.claude/skills/technical-blog-writing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/technical-blog-writing/
1Skills CLI (Vercel)
npx skills add 101-skills/superpowers --skill technical-blog-writing -a codex2Manually: put the files in place
.agents/skills/technical-blog-writing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add 101-skills/superpowers --skill technical-blog-writing -a cursor2Manually: put the files in place
.cursor/skills/technical-blog-writing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install 101-skills/superpowers guides/writing/technical-blog-writing2Manually: put the files in place
.github/skills/technical-blog-writing/SKILL.md1Skills CLI (Vercel)
npx skills add 101-skills/superpowers --skill technical-blog-writing -a gemini-cli2Platform CLI
gemini skills install https://github.com/101-skills/superpowers --path guides/writing/technical-blog-writingManually: put the files in place
.devin/skills/technical-blog-writing/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add 101-skills/superpowers --skill technical-blog-writing -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about technical-blog-writing
How do I install technical-blog-writing in Claude Code?
Run npx skills add 101-skills/superpowers --skill technical-blog-writing -a claude-code. The skill then sits at ~/.claude/skills/technical-blog-writing/SKILL.md.
What does technical-blog-writing do?
It structures engineering blog posts: an outline per article type, rules for code examples, and explanation depth tied to the audience you state.
What does it need for the research and header image steps?
The belt CLI from inference.sh, installed with npx skills add belt-sh/cli, plus belt login before the first run.