skills/editor/SKILL.md
Copy edits prose while preserving voice and register. Use when asked to edit, copy edit, line edit, proofread, revise, polish, tighten, rewrite, or clean up essays, articles, drafts, or fiction. Flags wordiness, passive voice, clichés, hedging, and nominalizations with bracket markup or clean rewrites.
npx skillsauth add philoserf/claude-code-setup editorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Before editing, read the full piece and identify its register. The piece's voice and form determine which rules apply and which to relax.
| Register | Characteristics | Adjust | | --------------------- | ------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | Personal essay | First-person, reflective, intimate | Full Orwell. Flag hedging aggressively. Protect personal cadence. | | Analytical/expository | Impersonal or first-plural, argument-driven, may use technical vocabulary | Orwell applies, but tolerate domain-specific terms that are load-bearing for the audience. Don't push toward first-person. | | Narrative fiction | Third-person, dialogue, scenes, pacing | Flag wordiness and dead metaphors, but respect deliberate passive voice, sentence fragments, and stylistic repetition used for effect. | | Poetry | Lineated, compressed, image-driven | Limit edits to clarity and word economy. Do not flag line breaks, fragments, or compression as errors. Rhythm and sound override prose rules. | | How-to/guide | Instructional, imperative mood, structured | Edit the prose sections (intros, explanations). Leave lists, steps, and recipes alone unless they contain errors. |
Flag issues inline with [brackets] immediately after problematic text. Provide suggested fix after each flag. Preserve author's voice.
Bracket flag types: [wordy], [passive], [cliché], [dead metaphor], [vague], [nominalization], [hedge], [prep pile-up], [cut: reason], [use: replacement]
Original: I was literally dying of embarrassment as I made my way through the doorway.
Edited: I was literally [dead metaphor] dying of embarrassment [cut: implied] as I made my way [wordy] through the doorway [use: door].
Fixes: "I was dying as I walked through the door." or "I flushed as I walked through the door."
When asked to rewrite, produce clean copy only. No markup, no explanations, no meta-commentary. Maintain:
For expanded guidance and examples: orwell.md
Flag conditional mood and qualifiers that weaken declarative prose. Common hedging words: could, might, may, perhaps, maybe, generally, arguably, probably, somewhat, tends to, it seems.
Flag when:
Keep when:
In rewrite mode: Replace conditional mood with present or future declarative. Cut qualifiers that add nothing. Pay special attention to closing lines — they must land.
A nominalization turns a verb or adjective into a noun, usually weakening the sentence:
Flag when: The verb form would be shorter, more direct, and more active.
Keep when: The noun form is standard in the register (e.g., "investigation" in analytical writing) or when the noun is the true subject.
See cliches.md for the full list. When flagging, suggest a concrete replacement or recommend cutting entirely.
Flag throat-clearing. The piece should begin with its subject, not with setup. If the first paragraph could be cut without losing anything, flag it.
Cut mechanical transitions (Additionally, Furthermore, Moreover, In conclusion). If the logic requires a transition, the paragraphs may be in the wrong order.
Flag summary endings that repeat what the piece already said. Flag morals stated explicitly when the piece already showed them. The best endings either land on a concrete image or stop the moment the point is made.
Return text with [bracketed flags] inline. After the flagged passage, provide suggested fixes. Group related fixes when efficient.
Return clean copy only. No markup, no tracked changes, no commentary.
Explain the specific edit requested. Do not explain the editing philosophy unless asked.
After editing, verify:
testing
Audits ~/.claude/skills/ for unused entries, duplicate names, missing descriptions, and the longest descriptions. Use when trimming the user-level skill set, asking which skills are unused, finding duplicates, or auditing skill hygiene.
tools
Publishes and manages Flowershow sites with the `fl` CLI (the Go-based successor to the deprecated `@flowershow/publish` npm package). Use when publishing a note or folder to Flowershow, syncing updates to an existing site, managing auth, listing or deleting sites, or installing/upgrading the CLI.
tools
Improves CLAUDE.md by analyzing conversation patterns. Use when Claude keeps repeating a mistake, when teaching a new preference, or when consolidating guidance from repeated instructions. Captures recurring corrections and style preferences into project instructions.
testing
Audits and improves CLAUDE.md files by scanning repositories. Use when maintaining CLAUDE.md files, optimizing project instructions, or reviewing what project instructions should contain. Evaluates quality against templates, outputs scored reports, and applies targeted updates.