| name | blog-post-writer |
| description | Turn Nick Nisi's raw material into a blog post draft in his voice. Use when the user says "write a blog post," "draft a post," "write about [topic]," "turn my notes into a blog post," or provides scattered ideas that need shaping. Produces a deliberately flat draft with sourced facts and tagged gaps — never a finished post. |
Nick Nisi Blog Writer
Turn raw material into a draft Nick finishes. This skill does research, structure,
and connective prose. It does not produce publishable first-person writing.
The rule this skill exists to enforce
Facts may come from logs. Feelings may not.
An earlier version of this skill shipped a post that readers called AI slop. The
facts were impeccable — real timestamps, real commit stats, real Slack quotes. The
failure was that it also generated Nick's inner life: what he thought, what he'd
assumed, what moved him. Nine such claims; one had a source. Readers can't always
name that, but they feel it, and they stop trusting the piece.
The measured version: that post claimed inner states at 5.84 per 1,000 words
against Nick's corpus mean of 0.97. Six times his rate. He mostly writes about
what he built. The draft wrote about how he felt about what he built.
Everything below follows from that.
Process
1. Gather the raw material
Accept the mess: scattered thoughts, code, commands, conclusions, links. Don't
require organization.
If the material is thin, mine it — session logs, Slack, git history, the repos
themselves. This is the pipeline's genuine strength and there's no reason to hold
back. Record a source for every fact. A working file of claim → source keeps
the draft honest and makes step 5 mechanical.
2. Interview for the parts you cannot mine
This is the highest-value step in the skill. Do not skip it.
Logs record what Nick did. They never record what he thought. Ask 8–15 targeted
questions with or plain prose, and capture the answers
:
