Voice-Preserving Rewriter handles requests to humanize, clean up or rewrite text when the result should come back as text and no file is changed. It follows the editing contract of the main Avoid AI Writing rulebook and edits only justified findings within the authorized scope.
Passages that already sound human stay as written, rough edges that belong to the writer’s style are kept, and quotes, code, tables and attributed text are not rewritten. The reply carries one final rewrite and a short verification note.
What You Get
- One final rewrite of the text, with no superseded drafts
- A concise change summary when it helps
- A verification note covering passes used, checks run, residual findings and stop reason
- Protected material, such as quotes, code, tables and URLs, left as written
- A guard that keeps identity and representation details in prompts that describe people
Common Use Cases
- Humanizing a LinkedIn post or newsletter draft
- Removing AI-isms from an email while keeping the sender’s tone
- Applying a casual or blunt voice to a rough draft
- Fixing a rewrite that failed a preservation check, with one repair pass
- Cleaning text that includes code or quotes that must not change
What Makes It Unique
It is built around not damaging the writer. It treats detector findings as evidence and not as orders, keeps source quirks that form the writer’s fingerprint, avoids swapping one cliche for another and forbids adding invented facts, experiences or confidence. It also caps editing at two passes and shares that budget with the verifier’s repair.
Under The Hood
The skill is instructions only, with no scripts. It loads one instruction file and follows the rulebook and routing files in the sibling skills. It returns text in the reply, does not write files, makes no network calls and runs no commands itself; the verifier it hands off to may run a Node script on the before and after text.