From writing-tools
This skill should be used when the user asks to "revise text", "make writing clearer", "improve readability", "edit for busy readers", "make text scannable", "tighten up writing", "cut filler words", "lead with the point", or wants text revised for clarity and conciseness.
How this skill is triggered — by the user, by Claude, or both
Slash command
/writing-tools:writing-revisionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Revise text to be clear, scannable, and action-oriented for busy readers.
Revise text to be clear, scannable, and action-oriented for busy readers.
Activate this skill when revising:
Inline text: Output the revised text directly with no wrapper, labels, or explanation.
File input: Use the Edit tool to modify the file in place.
Apply these principles in priority order:
First sentence states the key message or request. Details follow.
Before: "I wanted to reach out because I've been thinking about the project timeline and after reviewing the dependencies, I believe we need to push back the launch date."
After: "We need to push the launch date back two weeks. The authentication integration has dependencies we didn't anticipate."
Spell out exactly what's needed and by when. One main ask per message.
Before: "It would be great if someone could take a look at this when they get a chance."
After: "Please review the attached PR by Thursday EOD. I need your sign-off before merging."
Cut filler words: "just", "really", "I think maybe", "kind of", "actually", "basically", "in order to".
Before: "I just wanted to quickly check in to see if you've had a chance to basically review the document I sent over."
After: "Have you reviewed the document?"
First line of each section = key idea. Rest is optional detail.
Use bullets, numbered lists, bold for key terms. Break up walls of text.
Default to everyday words. Define jargon briefly if unavoidable.
| Instead of | Use |
|---|---|
| utilize | use |
| facilitate | help |
| leverage | use |
| synergize | work together |
| actionable | practical |
One topic per message. If multiple topics, use clear sub-headings.
State recommendation and alternatives explicitly.
Before: "There are several options we could consider..."
After: "Recommendation: Option A (fastest). Alternatives: Option B (cheapest), Option C (most flexible)."
Who does what, by when. Keep it to a short block.
Format:
**Next steps:**
- [Person]: [Action] by [Date]
- [Person]: [Action] by [Date]
For detailed patterns and examples:
references/patterns.md - Extended examples and edge casesnpx claudepluginhub staticaland/skills --plugin writing-toolsApplies Strunk's Elements of Style rules to edit documentation, commit messages, error messages, UI text, reports, and explanations for clarity and conciseness.
Applies Strunk's Elements of Style rules to edit documentation, commit messages, error messages, UI text, reports, and explanations for clarity and conciseness.