Prose fix
Fix prose formatting, typos, and clarity issues in markdown or text files. Use when user asks to "fix dashes", "fix typos", "clean up text", "improve sentences", or "/prose-fix". Don't use for code style, linting, or full rewrites.From its SKILL.md
npx -y skills add helderberto/agent-skills --skill prose-fixAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 2 commands, including `Grep for `—` to list formatting issues` and 1 more.
SKILL.md
1.9 KB, 372 tokens by cl100k_base, as published. Nobody here has run it
Prose Fix
Scan the target file(s) for formatting issues, typos, and weak prose. Fix in place without changing the author's voice or intent.
What to Fix
Formatting
| Issue | Replace with |
|---|---|
Em dash — (with spaces) | Period, comma, colon, or parentheses depending on context |
Em dash — (no spaces) | Split into two sentences or use comma |
| Double spaces | Single space |
Typos
- Misspelled words
- Wrong word form (e.g. "teh" → "the", "dont" → "don't")
- Missing apostrophes in contractions
Sentence Clarity
- Remove filler words ("very", "just", "really", "basically", "actually")
- Split run-on sentences into two
- Flatten weak constructions ("is able to" → "can", "in order to" → "to")
Rules
- Read the file before editing
- Never change the author's voice, tone, or meaning
- Never rewrite a sentence that is already clear and direct
- Preserve technical terms, code references, and proper nouns exactly
- Do not add words — only remove or substitute
- One pass: formatting first, then typos, then clarity
Workflow
- Read the file
- Grep for
—to list formatting issues - Edit all issues in one pass per category
- Grep again for
—to confirm none remain - Report a summary of what was changed by category
Scope
- Works on any
.mdor.txtfile - If no file is specified, ask the user which file to fix
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most docs writing skills give in 372 tokens
Counted across 1,951 of the 3,904 authors here whose files we hold, read 2026-09-06
- Use third-person for skill descriptionsin 54 of 1951, across 35 files
- Start descriptions with Use whenin 43 of 1951, across 29 files
- Run baseline scenarios before writing any skillin 40 of 1951, across 26 files
- Use active voicein 40 of 1951, across 36 files
- Map file responsibilities before defining tasksin 36 of 1951, across 29 files
- Use checkbox syntax for tracking stepsin 35 of 1951, across 27 files
- Ask one question at a timein 35 of 1951
- Offer execution options after saving the planin 33 of 1951, across 24 files
- Include complete code in every stepin 33 of 1951, across 27 files
- Design units with clear boundaries and interfacesin 31 of 1951, across 23 files
- Announce the skill usage at the startin 30 of 1951
- Verify agent compliance after adding the skillin 29 of 1951, across 17 files
Said here and by no other author read
- Fix formatting issues first
- Correct typos and missing apostrophes
- Split run-on sentences
- Flatten weak constructions
- Edit all issues in one pass
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.