Converts a Claude Code session into a blog post, case study, or Reddit post. Use when publishing dev blog content or community posts from real sessions.
Converts a Claude Code session into a blog post, case study, or Reddit post. Use when publishing dev blog content or community posts from real sessions.
Capture what happened in a Claude Code session and turn it into a
blog post, case study, or social media thread that others can learn from.
The skill extracts the real story from git history, file changes, and
conversation context, then shapes it into a narrative that shows
process, not just results.
When To Use
After completing a meaningful chunk of work you want to share
Creating dev blog content from real sessions
Building case studies for tools, libraries, or techniques
Producing marketing content that demonstrates capability
Documenting a process for teammates who weren't in the session
Sharing a session story with a Reddit community (r/programming,
r/rust, r/Python, r/ClaudeAI, etc.)
When NOT To Use
Writing API reference documentation (use scribe:doc-generator)
Conversation context: the user's goals, constraints, and decisions
made during the session
Step 2: Identify the Story
Every session post answers three questions:
What were we trying to do?: the goal, not the task list
What did we actually do?: the real path, including pivots
What came out of it?: concrete, measurable results
Look for:
The hook: what makes this interesting? A hard problem, a
surprising approach, an impressive result
Turning points: where did the plan change? What broke?
What worked unexpectedly?
The number: one metric that captures the outcome
(lines written, tests passing, performance gain, time saved)
Step 3: Draft the Post
Choose format first:
Format
Module
When
Blog post
narrative-structure
Dev blog, company blog, personal site
Case study
narrative-structure
Marketing, tool demonstrations
Social thread
narrative-structure
Twitter/X, Bluesky, LinkedIn
Reddit post
reddit-format
Community engagement, r/programming etc.
For Reddit: load modules/reddit-format.md instead of the blog
template below. The structure, tone, and quality gate differ.
Load the narrative-structure module for blog/case-study templates.
Blog post structure (adapt to content):
# Title: [Verb] + [What] + [With What]## Opening (2-3 sentences)
What we set out to do and why. No throat-clearing.
## Starting Point
Where things stood before. Concrete: file counts, code state,
what worked and what didn't.
## The Work
Key phases. Focus on decisions and pivots, not keystrokes.
- Phase 1: [what and why]
- Phase 2: [what and why]
Include GIFs from scry recordings where visual.
## How We Tested It
What verification looked like. Show the test run, the proof-of-work
evidence. Include terminal recording GIF of tests passing.
## Results
Hard numbers. Before/after. What works now.
Screenshots or browser recording GIF if visual.
## What's Next
Honest remaining work. No false completeness.
Tone:
Write like explaining to a colleague over coffee
Specifics over adjectives ("180 tests" not "comprehensive suite")
Show the mess: readers connect with pivots and debugging
Credit the tools and techniques that made it work
Under 1500 words unless the content demands more
Step 4: Quality Gate
For blog posts and case studies:
Slop check: Skill(scribe:slop-detector) on the draft
Proof-of-work: Skill(imbue:proof-of-work) on all claims
Recording check: does any section need a GIF?
Title test: would you click this? Does it promise
something specific?
Opening test: does paragraph one say what the post is about?
For Reddit posts (additional gates):
TL;DR present: is it after --- at the end?
Lede not buried: is the most interesting thing in the
first two sentences?
Subreddit fit: does the content match the target subreddit's
norms? Check the subreddit's top posts of the month.
First comment drafted: are the repo link and any reference
material ready to post as a follow-up comment?
Header count: if the post is under 600 words, are headers
absent (or replaced with bold inline labels)?
Step 5: Output
Write the post to the requested location (default:
docs/posts/).
Report:
Format used (blog post / case study / Reddit post)
Word count
Slop score (blog/case-study only)
Verifiable claims count
Recordings generated (if any)
For Reddit: target subreddit and first-comment content
Example
A session that ported a Quake 2 engine from C to Rust:
Title: Rewriting a Quake 2 Engine in Rust with Claude Code
Opening: We took a 150,000-line C game engine and started
rewriting it in Rust targeting WebAssembly. In one session we went
from an empty workspace to a prototype loading real game data in
the browser.
Starting point: A Yamagi Quake II fork compiled with Emscripten.
Goal: idiomatic Rust with wasm-bindgen, glow for WebGL2, and
matchbox for P2P multiplayer.
The work: Seven parallel agents built subsystems (collision,
movement, filesystem, networking, renderer, server, client) while
the main session coordinated integration. A Makefile with
prerequisite checks automated the full build-to-browser pipeline
including game data download.
How we tested: 180 unit tests across 13 crates. BSP loading
verified against real Quake 2 demo pak0.pak. Browser diagnostics
logged every init step. [Terminal GIF: make test output]
Results: 10,950 lines of Rust, 180 tests, real game data
loading and flat-shaded BSP rendering in the browser with WASD
movement and mouse look.
