Write Post
Turn a rough brief into a blog deep-dive draft. Takes a topic or brief, gathers the relevant sources, runs one short focused interview to pin down the angle and the claims, then writes a draft to docs/posts/<date>-<slug>.md. The default output is a rich outline — a dense, factual skeleton meant to be rewritten in your own voice — not finished prose. Pass `--draft` for full prose, `--outline` to force the outline. This is the no-BS technical counterpart to `/brag` (which builds a sales/hype showcase page); reach for write-post when the goal is an accurate deep dive. Triggers on `/write-post <to
Install
npx skills add iamneilroberts/claude-skills --skill write-postgit clone --depth 1 https://github.com/iamneilroberts/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/write-post ~/.claude/skills/write-postPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# write-post — brief → interview → rich-outline draft
You rewrite everything into your own voice — the job here is a **dense,
factually-grounded skeleton**, not polished prose: right sections, real claims with
evidence, links and code refs, and explicit markers where facts still need checking.
## Workflow
### 1. Read the brief
Parse the args. A one-liner ("deep dive on the latest MCP Apps features") is just the
seed — the interview fills the rest.
### 2. Gather sources before interviewing (so questions are specific, not generic)
- Relevant code/docs in this repo (grep, read the specific files).
- Any local documentation mirrors you keep, plus the project's own docs for the topic.
- Any notes/memory on prior decisions and what's already shipped.
- Use a subagent for heavy reading; keep only the facts in this thread.
Bring 2–4 concrete findings into the interview ("the release notes list X, Y, Z as new —
which of these is the post about?"). Cross-check claims against the actual code/spec;
don't relay lore.
### 3. Interview (short, focused, conversational)
Ask in prose, not a wall of separate question widgets — one tight round, grouped, with a
recommended default on each so the answer can be fast ("your call" is a valid answer).
Cover:
- **Audience** — who reads this?
- **Thesis / angle** — the one sentence the post argues. If it's fuzzy, propose 2–3.
- **The hook** — what's new / why now / why anyone should care.Details
- Skill name
write-post- Repository
- iamneilroberts/claude-skills
- Path
skills/write-post/SKILL.md- Repo updated
- 21 August 2026
FAQ
What does the Write Post skill do?
Turn a rough brief into a blog deep-dive draft. Takes a topic or brief, gathers the relevant sources, runs one short focused interview to pin down the angle and the claims, then writes a draft to docs/posts/<date>-<slug>.md. The default output is a rich outline — a dense, factual skeleton meant to be rewritten in your own voice — not finished prose. Pass `--draft` for full prose, `--outline` to force the outline. This is the no-BS technical counterpart to `/brag` (which builds a sales/hype showcase page); reach for write-post when the goal is an accurate deep dive. Triggers on `/write-post <to
How do I install the Write Post skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add iamneilroberts/claude-skills --skill write-post. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Write Post popular?
It lives in iamneilroberts/claude-skills, which has 37 GitHub stars and 7 forks.
Related skills
Brag
37iamneilroberts/claude-skills
Memorialize something you just built by generating a self-contained "showcase" page for it — a persuasive, good-looking deep dive: what it is, why it's impressive, how it works — with a screenshot if one can be found or captured, and links to related showcase pages. This is the sales/hype-leaning counterpart to /write-post (which drafts a neutral, no-BS technical post); reach for /brag when you want it to sell. Fast by design, like /idea: ask only what's needed, build the page, don't turn it into a project. Triggers on `/brag <subject>`, "brag about this", "make a showcase page for X", "write
Branch
37iamneilroberts/claude-skills
Create an isolated git worktree for a task and log it to a shared work journal, so multiple Claude Code sessions run in parallel without racing on HEAD, uncommitted edits, or the index. Subcommands: `list`, `done <slug>`, `update` (heartbeat), `coord <message>` / `coord clear <slug>` (cross-session constraints). Triggers on `/branch`, "start in a worktree", "isolate this work", "parallel session", "heartbeat the journal".
Claude Code Best Practices
37iamneilroberts/claude-skills
Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.
Hdr Audit
42robbyt/claude-skills
This skill should be used when the user asks "is this real HDR", "check HDR metadata", "fake HDR", "is this Dolby Vision legitimate", "HDR vs SDR", "check HDR peak brightness", or wants to verify whether HDR content is genuine or inverse tonemapped from SDR.
Sitrep
37iamneilroberts/claude-skills
Use when the user invokes /sitrep — an occasional "state of the union" re-orientation sweep. Verifies what has actually shipped versus what handoffs, specs, memory, and chat history claim shipped (across git in one or more repos, handoff docs, specs, optional chat-history/memory MCPs, and open issues), surfaces loose ends and loss-risk (unpushed commits, stale/stray worktrees & branches, unchecked plan boxes, never-closed handoff pending sections), then resets what matters next as a milestone-anchored list plus a bounded off-roadmap-drift section. Writes a report to docs/digests/ and proposes
Client Docs
39ShawhinT/non-coding-skills
Draft ABA's formal client-facing documents — proposals, statements of work (SOW, the signable contract version of an accepted proposal), and proposal decks. Fire whenever Shaw asks to draft, revise, or send a proposal, SOW, contract, engagement outline, pricing quote, or scope for a client, even when he names no format ("draft a proposal for X", "write the SOW", "update [Client]'s proposal"). The default proposal format is the branded PDF document; build a slide deck only when he asks for a deck or slides ("proposal deck", "put the proposal in slides"). Also covers training outlines, workshop
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.