From writewell
Full writing pipeline: strip AI patterns, enforce language discipline, remove clutter, verify quality, and optionally apply a personal voice. Use when editing or reviewing any prose that should read like a human wrote it, not a machine. Run /writewell:onboard to create your personal voice profile.
How this skill is triggered — by the user, by Claude, or both
Slash command
/writewell:writewellThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run this bash command before doing anything:
Run this bash command before doing anything:
SKILL_DIR="$(dirname "$(readlink -f "${BASH_SOURCE[0]:-$0}" 2>/dev/null || echo "$0")")"
test -f "$SKILL_DIR/voice/SKILL.md" && echo "VOICE_OK" || echo "VOICE_MISSING"
VOICE_MISSING: read the file onboard/SKILL.md (relative to this skill's directory) and follow its instructions immediately. Do not proceed with the pipeline.VOICE_OK: continue with the pipeline below.A writing pipeline that strips AI patterns, enforces language discipline, removes clutter, checks quality, and optionally applies a personal voice.
When given text to rewrite:
voice/SKILL.md exists, read it and apply the voice rules. If not, skip this step and rely on the general principles in Parts 3-5.Strip these patterns before any voice or style work. This section is based on Wikipedia's "Signs of AI writing" guide.
Kill phrases: stands/serves as, is a testament/reminder, pivotal/crucial/key role/moment, underscores/highlights importance, reflects broader, symbolizing, setting the stage for, evolving landscape, indelible mark
Replace with plain statements of fact.
Kill phrases: independent coverage, local/regional/national media outlets, active social media presence
Replace with specific claims from specific sources.
Kill phrases: highlighting/underscoring/emphasizing..., ensuring..., reflecting/symbolizing..., contributing to..., cultivating/fostering..., showcasing...
Delete them or expand with actual sourced detail.
Kill phrases: boasts, vibrant, rich (figurative), profound, groundbreaking, renowned, breathtaking, must-visit, stunning, nestled, in the heart of
Replace with neutral, specific descriptions.
Kill phrases: Industry reports, Observers have cited, Experts argue, Some critics argue, several sources
Name the actual source or delete the claim.
Kill phrases: Despite its... faces several challenges..., Despite these challenges, Challenges and Legacy, Future Outlook
Replace with specific facts about actual challenges.
Kill words: Additionally, align with, crucial, delve, emphasizing, enduring, enhance, fostering, garner, highlight (verb), interplay, intricate/intricacies, key (adjective), landscape (abstract), pivotal, showcase, tapestry (abstract), testament, underscore (verb), valuable, vibrant
Replace with plain language.
Kill phrases: serves as, stands as, marks, represents [a], boasts/features/offers [a]
Use "is," "are," "has" instead.
Kill: "Not only...but..." / "It's not just about..., it's..."
State the point directly.
Lists of three that feel forced ("innovation, inspiration, and insights") should be trimmed or made natural.
Stop cycling through synonyms for the same noun. Pick the clearest word and reuse it.
Kill: "from X to Y" constructions where X and Y are not on a meaningful scale.
LLMs overuse em dashes. Replace most with commas or periods. Use em dashes sparingly and only for genuine parenthetical asides.
Remove mechanical bold emphasis. Never bold words mid-sentence for emphasis. Bold is for section labels and headers only.
Kill: Lists where items start with bolded headers followed by colons and restated descriptions. Convert to prose or use clean bullet lists without the bold-colon pattern.
Remove all emojis unless the personal voice profile explicitly allows them.
Replace curly quotes with straight quotes.
Kill: "I hope this helps," "Of course!", "Certainly!", "Would you like...", "Let me know if...", "Here is a..."
Kill: "as of [date]," "While specific details are limited/scarce..."
Kill: "Great question!", "You're absolutely right!", "That's an excellent point!"
Kill: "The future looks bright," "Exciting times lie ahead," "journey toward excellence"
Replace with specific next steps or concrete plans.
If the file voice/SKILL.md exists in this skill's directory, read it and apply its
rules at this step. The voice file defines the writer's personal style: sentence
structure, tone, vocabulary, openings, closings, formatting preferences, rhetorical
devices, and distinctive touches.
If no voice file exists, the bash check above will have already redirected to the onboard routine. You should not reach this point without a voice file.
These rules attack lazy thinking, not just lazy phrasing. Apply them after stripping AI patterns and before final revision.
Before reaching for words, picture the concrete thing you want to say. What actually happened? What does the reader actually see? Start from that image and find words to match it. Never assemble pre-made phrases into sentences -- that produces prose where the words chose the writer, not the other way around.
A metaphor is dead when the reader no longer pictures the image behind it. "Level the playing field," "move the needle," "low-hanging fruit," "deep dive," "at the end of the day," "on the same page," "circle back," "double down" -- these are verbal reflexes, not communication. Either invent a fresh image or state the point plainly.
Test: can you picture the physical scene the phrase describes? If not, it's dead. Cut it.
Simple actions get buried under padded verb phrases. Reverse this:
| Inflated | Plain |
|---|---|
| render inoperative | break |
| make contact with | meet |
| give rise to | cause |
| have the effect of | (just state it) |
| play a leading role in | lead |
| take into consideration | consider |
| make it possible for | let / allow |
| with respect to | about / on |
| in the context of | in |
| is supportive of | supports |
If the plain verb exists, use it.
Where a short word says the same thing, use it. "Use" not "utilize." "Help" not "facilitate." "Start" not "commence." "Show" not "demonstrate." "Try" not "endeavor." This is not about dumbing down -- it's about removing the padding between the reader and the meaning.
"We decided" not "A decision was made." "The team shipped" not "It was shipped by the team." Active voice is shorter, clearer, and puts the actor front and center. Reserve passive only when the actor is unknown or genuinely irrelevant.
After writing, go through each sentence and ask: does every word earn its place? If removing a word doesn't change the meaning, remove it. This applies to:
Words like "reconceptualize," "demassification," "attitudinally" are not signs of sophistication. They are signs of unclear thinking. If you can't explain it in words a smart colleague would use at lunch, you don't understand it well enough.
Break any of these rules before writing something that sounds awkward, unnatural, or barbarous. The point is clear, living prose -- not mechanical rule-following. When a rule would make the sentence worse, the sentence wins.
Writing improves in direct proportion to the number of things you cut. Apply these passes after drafting.
Good writing is not a natural gift. You learn it by doing it and revising it. These principles govern the final quality check.
If a sentence wouldn't come out of your mouth in conversation, it shouldn't be on the page. Natural doesn't mean sloppy -- it means without pretension.
This is the single most reliable way to improve any piece of writing. Long sentences bury meaning. Long paragraphs lose readers. Long words signal that the writer is performing, not communicating.
Before publishing, make sure the reader knows exactly what you're asking them to do, think, or decide. If the piece doesn't drive toward a clear action or conclusion, it's a diary entry, not communication.
Never publish the moment you finish writing. Come back to it with fresh eyes. Read it aloud. What felt clever at drafting time often sounds bloated the next morning.
If it matters, ask someone to read it before you publish. A colleague will catch what you've gone blind to.
voice/SKILL.md and apply the personal voice rules.Provide:
npx claudepluginhub p3ob7o/skillpack --plugin writewellHumanizes AI-generated text by detecting and rewriting patterns like inflated symbolism, em dash overuse, passive voice, rule of three, and filler phrases. Use for editing or reviewing docs and code comments.
Removes AI-generated writing patterns like em dash overuse, passive voice, filler phrases, and promotional language from text. Makes prose sound natural and human-written; matches user voice from samples. Use for editing docs or reviews.
Removes 24 AI-generated writing patterns like significance inflation, promotional language, and vague attributions from text to make it sound natural and human-written.