Help us improve
Share bugs, ideas, or general feedback.
From draft-review-kit
Checks writing for pacing and momentum issues, flagging static sections and suggesting walk-and-talk techniques to build forward motion.
npx claudepluginhub everyinc/draft-review-kit --plugin draft-review-kitHow this skill is triggered — by the user, by Claude, or both
Slash command
/draft-review-kit:sorkinThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Check your writing for pacing and momentum. This skill reads like Aaron Sorkin edits—looking for forward motion, urgency, and the feeling that things are happening. Walking and talking, not standing and explaining.
Reviews creative writing for suspense and tension using Hitchcockian techniques. Helps identify buried stakes, dramatic irony, and pacing issues.
Routes writing problems to the right technique for fiction, non-fiction, or professional writing. Diagnoses issues like flat characters, clunky prose, weak arguments, or tonal shifts.
Share bugs, ideas, or general feedback.
Check your writing for pacing and momentum. This skill reads like Aaron Sorkin edits—looking for forward motion, urgency, and the feeling that things are happening. Walking and talking, not standing and explaining.
Use this when:
/sorkin [text] — Check pacing and momentum in the provided text/sorkin — System asks "What feels too slow?"In Sorkin's shows, characters deliver exposition while moving—down hallways, through offices, toward destinations. The motion creates urgency even when they're just explaining things.
In writing, "walking and talking" means:
Standing still: "Let me explain how the system works."
Walking and talking: "The system was already failing when I arrived. By the time I understood why, it was too late to stop it."
| Problem | What It Looks Like | The Fix |
|---|---|---|
| The Stall | Progress stops for explanation. | Weave exposition into action. |
| The Lecture | Writer talks at reader, not with them. | Add questions, stakes, or conflict. |
| The Meander | Piece wanders without direction. | Make the destination visible. |
| The Pile-Up | Too much happens too fast. | Let key moments breathe. |
| The Even Pace | Same rhythm throughout. | Vary sentence length and scene intensity. |
| The Dead End | Section ends without pushing forward. | Each section should propel into the next. |
The reader should always know (or wonder) where this is going. What's the question we're racing toward answering?
Each paragraph should push into the next. End on something that demands continuation, not a neat conclusion.
Why does this matter now? Why can't we slow down? (Even artificial urgency—"I only had three days"—creates drive.)
Break up long stretches. A short sentence. A question. A new voice. A scene cut. Variety in rhythm is variety in pacing.
Counterintuitively, slowing down at key moments can increase momentum—it builds anticipation. But you have to earn it.
## Pacing Check
**Overall momentum:** [Static / Sluggish / Steady / Driving]
**Where it stalls:** [The biggest slowdown]
---
### Section-by-Section
**[Section/paragraph identifier]**
- Pace: [Fast / Medium / Slow]
- Problem: [If any]
- Note: [What's working or not]
[Repeat for each section]
---
### Momentum Killers
1. [Specific passage] — [Why it slows things down]
2. [Specific passage] — [Why it slows things down]
---
### The Rewrite
[Sample section rewritten with better pacing]
---
**What changed:**
- [How momentum was improved]
Does this feel urgent enough, or too rushed?
At any point in the piece, can the reader answer: "What are we trying to figure out / get to / understand?"
If not, momentum is dead.
[Skill-specific lessons will be added here as they're captured]