Copy editing
Curated, auditable, benchmark-ready Agent Skills library for Claude Code, Codex, OpenCode, Cursor, and more.
npx -y skills add shinzoxD/knackbox --skill copy-editingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 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.
What its author says it does
Copied from the file, not written here
Edit prose for clarity, correctness, flow, consistency, and concision while preserving the author's meaning and voice. Use whenever the user asks to edit, proofread, polish, tighten, simplify, or improve writing, shares a draft with minimal instructions, or wants grammar and style issues fixed.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.6 KB, as published. Nobody here has run it
Copy Editing
Improve the text without replacing the author's voice or changing factual meaning. Match the depth of editing to the request.
Editing levels
- Proofread: spelling, grammar, punctuation, formatting, and obvious typos.
- Copy edit: clarity, concision, consistency, transitions, and sentence flow.
- Line edit: rhythm, emphasis, structure, tone, and repeated ideas.
If the user does not specify a level, perform a copy edit and avoid unnecessary rewriting.
Workflow
- Identify audience, purpose, voice, dialect, and required style guide.
- Read once for meaning before changing sentences.
- Fix correctness and ambiguity first.
- Remove repetition, filler, weak openings, and buried actions.
- Normalize terminology, capitalization, numbers, headings, and citations.
- Re-read for meaning changes and continuity.
Output format
For short text, return the edited version followed by a brief note on substantive changes. For long text, use:
## Edited draft
<clean text>
## Editorial notes
- Meaning-changing questions or unresolved inconsistencies
- Major structural changes
- Facts or citations that need verification
Provide tracked before/after examples only when the user asks or when a change could alter meaning.
Rules
- Preserve claims, numbers, names, citations, and technical terms unless clearly incorrect; flag uncertainty instead of silently correcting facts.
- Prefer concrete verbs and direct syntax, but retain deliberate style.
- Do not flatten cultural voice, dialect, humor, or purposeful fragments.
- Keep terminology consistent without introducing jargon.
- Do not expand the draft with new claims unless requested.
- Respect the requested dialect, such as US or UK English.
Edge cases
- For legal, medical, or regulated text, edit language but flag that substantive review requires a qualified professional.
- For translated prose, improve naturalness without guessing at ambiguous source meaning.
- For highly personal writing, avoid making the voice sound corporate or generic.