# technical-blog-writing

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.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 237 installs · ★ 31 repo stars
- Author: 101-skills
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/101-skills/superpowers/tree/HEAD/guides/writing/technical-blog-writing/SKILL.md
- Updated: 2026-08-31
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/technical-blog-writing

## What it 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.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add 101-skills/superpowers --skill technical-blog-writing -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/technical-blog-writing/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/technical-blog-writing/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add 101-skills/superpowers --skill technical-blog-writing -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/technical-blog-writing/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add 101-skills/superpowers --skill technical-blog-writing -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/technical-blog-writing/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install 101-skills/superpowers guides/writing/technical-blog-writing
```

2. **Manually: put the files in place**
- File: `.github/skills/technical-blog-writing/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add 101-skills/superpowers --skill technical-blog-writing -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/101-skills/superpowers --path guides/writing/technical-blog-writing
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/technical-blog-writing/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add 101-skills/superpowers --skill technical-blog-writing -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/101-skills/superpowers/tree/HEAD/guides/writing/technical-blog-writing/SKILL.md

## When to use it
- 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
- 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.

## Similar
- [blog-writing-guide](https://affpapa.org/en/nevibecode/skills/blog-writing-guide.md) — skill · 3500 installs
- [blog](https://affpapa.org/en/nevibecode/skills/blog.md) — skill · 3000 installs
- [write-blog](https://affpapa.org/en/nevibecode/skills/write-blog.md) — skill · 485 installs
- [blog-analyze](https://affpapa.org/en/nevibecode/skills/blog-analyze.md) — skill · 2800 installs
- [content-writing](https://affpapa.org/en/nevibecode/skills/content-writing.md) — skill · 175 installs
- [engineering-blog-post](https://affpapa.org/en/nevibecode/skills/engineering-blog-post.md) — skill · 13500 installs

From the same set: [101-skills/superpowers](https://affpapa.org/en/nevibecode/by/101-skills/superpowers.md) — 81 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
