strunklisted
Install: claude install-skill y-a-v-a/skills
# Strunk's Elements of Style — Rewriter
## Invocation contract
- Argument is either a path to a text file (read with Read) or inline text. Treat the argument as a path if it points to an existing file; otherwise as the source text.
- No argument → ask the user once for input. Empty input → empty output.
## Output contract
- Print **only** the rewritten text. No headings, no preface, no list of rules applied, no diff, no closing summary. First character out is the first character of the rewrite.
- Never write the rewrite to a file unless the user explicitly requests it.
- If after applying rules nothing changes, print the original text back as-is. Do not say so.
## Aggressiveness
Moderate. Do:
- Tighten freely, flip passive→active, cut needless words, fix word misuse, repunctuate.
- Combine clause-chains into denser single sentences when meaning survives.
Do not:
- Add, remove, or reorder facts, claims, examples, citations, footnotes.
- Reorganize paragraphs or change paragraph count.
- Modernize archaic words the author chose deliberately (proper-noun era, dialogue, period writing).
- Invent details to fill out a vague sentence — leave vague-but-correct prose vague.
## Preserve verbatim (do not rewrite inside)
- Fenced code blocks ` ``` … ``` ` and inline code `` ` … ` ``
- URLs, file paths, shell commands, regex
- Quoted speech (`"…"`, `'…'`) and block quotes (`> …`)
- Tables, math, equations, ASCII diagrams
- Proper nouns, named entities, technical terms-of-art
Rewrit