A rigorous copy editor for Claude Code, inspired by the Hemingway Editor. It analyzes your writing for clarity, directness, and economy of words — then rewrites it.
Point it at marketing copy, technical docs, blog posts, specs, or AI-generated text. It flags passive voice, adverbs, jargon, bloated sentences, and AI slop, explains why each is a problem, and gives you a stronger version.
"Every word must earn its place. If it can be cut without losing meaning, cut it."
- Sentence complexity — flags sentences over 25 and 40 words, suggests breaking them up
- Passive voice — finds every instance and rewrites it active
- Adverb audit — kills weakening adverbs ("ran quickly" → "sprinted")
- Simpler alternatives — swaps jargon for plain words (utilize → use, leverage → use)
- Weak constructions — hedge words, nominalizations, empty phrases, throat-clearing
- Readability score — word count, average sentence length, and a Flesch-Kincaid grade level
It returns a summary, readability stats, a list of issues with rewrites, a fully revised version, and key takeaways.
Trigger a mode by mentioning it in your prompt.
| Mode | Trigger | What it adds |
|---|---|---|
| Quick review | "quick review" | Summary + revised version only |
| Just stats | "just stats" | Readability statistics only |
| Focus | "focus on passive voice" | A single dimension |
| Make it shorter | "make it shorter" | Aggressive cuts that keep meaning |
| Product marketing | "product marketing", "marketing copy" | Specificity, value-prop clarity, buzzword kills, CTA and social-proof checks |
| Technical spec | "technical spec", "spec review" | Precision, completeness, structure enforcement (RFC 2119) |
| Technical blog | "technical blog", "tech blog" | Hook audit, code-prose ratio, depth checks, narrative arc |
| SEO blog | "seo blog", "seo content" | Search intent, headings, snippets, keyword integration, E-E-A-T |
| De-slop AI text | "de-slop", "deslop", "ai cleanup" | Targets AI writing patterns: enthusiasm padding, filler transitions, fake structure |
There are two ways to install. Pick one.
Add this repo as a plugin marketplace, then install the plugin:
/plugin marketplace add Nikhil-Kasukurthi/hemingway-skill
/plugin install hemingway@hemingway-skill
Restart Claude Code if prompted. That's it.
Copy the skill into your personal skills directory:
git clone https://github.com/Nikhil-Kasukurthi/hemingway-skill.git
mkdir -p ~/.claude/skills
cp -r hemingway-skill/skills/hemingway ~/.claude/skills/hemingwayOr symlink it so you stay up to date with git pull:
git clone https://github.com/Nikhil-Kasukurthi/hemingway-skill.git
ln -s "$(pwd)/hemingway-skill/skills/hemingway" ~/.claude/skills/hemingwayClaude Code picks up skills in ~/.claude/skills/ automatically.
Once installed, just ask Claude to review your writing — the skill activates on its own when it's relevant. Some example prompts:
- "Review this landing page copy."
- "De-slop this — it reads like ChatGPT wrote it."
- "Quick review of my README intro."
- "This is a technical spec, do a spec review."
- "Make this paragraph shorter without losing the meaning."
- "Just stats for this blog post."
Input:
The decision was made by the committee to utilize a more robust framework that would facilitate better outcomes for all stakeholders involved in the process.
Output (abridged):
## Summary
Bloated with passive voice and corporate jargon. 26 words that say what 5 could.
**Readability Stats:**
- Words: 26 | Sentences: 1 | Avg length: 26 words
- Grade level: 14 (Target: 8)
- Passive voice: 1 | Adverbs: 0 | Complex sentences: 1
## Revised Version
The committee chose a stronger framework.
## Key Takeaways
- Lead with who did what (active voice)
- "Utilize" always means "use"
- Delete phrases that add no meaning ("involved in the process")
- Author: Nikhil Kasukurthi
- Inspired by the Hemingway Editor and Ernest Hemingway's principles of plain, direct prose.