Preservation Verifier checks that a rewrite or file edit kept what the Avoid AI Writing rulebook says to protect. It needs both versions and runs a bundled Node validator with a residual-pattern policy that keeps mechanical errors blocking and reports pattern growth as a warning.
It adds a separate semantic review for meaning, attribution, quantities, negation, conditions and uncertainty, and returns PASS, REVIEW or FAIL with the repair owner. It never rewrites content itself.
What You Get
- A PASS, REVIEW or FAIL result for a rewrite
- Blocking preservation errors and warnings from the validator
- A separate semantic review of meaning, attribution, numbers, negation, conditions and uncertainty
- The right repair owner on failure: the rewriter for returned text, the file editor for a named file
- A statement of whether the single allowed repair has already been used
Common Use Cases
- Checking that a rewritten article kept its code blocks, quotes and links
- Confirming a file edit did not change numbers, headings or frontmatter
- Reviewing a rewrite for growth in AI patterns after cleanup
- Validating a rewrite of a prompt that describes people, so identity details survive
- Stopping a workflow when a second check still fails
What Makes It Unique
It keeps mechanical checks and semantic judgment apart and says which one produced each result, so a model-only review is never presented as validator output. The repair loop is capped at one re-entry, and a failure counts as a blocking result: a rewrite is not complete just because text was produced.
Under The Hood
The skill loads one instruction file and bundles a Node validator with its pattern engine. The agent runs the validator in the shell on two text files, which only reads them and prints results; it can also be called as a JavaScript function. The result is reported by the agent and nothing is written to the files. It makes no network calls, and falls back to a manual comparison when Node cannot run.