Clean User Facing Text

Clean user-facing text

Apply a final text-hygiene pass to prose the user owns or is authorized to process. Treat Unicode cleanup as deterministic and statistical-watermark reduction as best-effort; never claim that a rewrite proves human authorship or is undetectable. Preserve required academic, legal, platform, and regulatory disclosures.

Workflow

1. Identify the prose that readers will see.
2. Protect non-prose spans:
   • fenced and inline code
   • commands, paths, URLs, identifiers, API names, and exact values
   • formulas, citations, and text the user asks to quote verbatim
3. Preserve every claim, fact, number, name, citation, and requirement.
4. Rewrite the remaining prose once:
   • vary clause order, sentence boundaries, rhythm, connectors, and function words
   • replace formulaic transitions and filler with direct, natural wording
   • preserve the requested language, tone, structure, and formatting; never translate unless asked
   • for non-English text, use fluent constructions native to that language rather than English sentence patterns
   • do not add or remove claims merely to increase variation
5. For text artifacts or supplied text files, run the deterministic Unicode pass after rewriting.
6. Return only the polished result unless the user asks for an audit or explanation.

Deterministic Unicode pass

Resolve SCRIPTS to this skill's scripts/ directory. Use the available Python 3 launcher for the platform. Replace PYTHON below with python3 on most macOS/Linux systems, py on Windows, or another verified Python 3 command.

Inspect first when editing an existing file:

PYTHON "$SCRIPTS/inspect_text.py" --json INPUT
PYTHON "$SCRIPTS/clean_text.py" INPUT -o OUTPUT --stats --no-normalize-spaces
PYTHON "$SCRIPTS/inspect_text.py" --json OUTPUT

Use - for stdin. Prefer a new *.cleaned.* output unless the user explicitly requests in-place editing.

Use --no-normalize-spaces by default so NBSP, narrow no-break spaces, figure spaces, and CJK ideographic spaces retain their layout semantics. Normalize spaces only when the user requests it.

Do not use --aggressive-homoglyphs, --nfkc, or --strip-emoji-glue unless the user requests aggressive normalization and accepts possible changes to multilingual text, emoji, directionality, or typography.

The scripts support plain text, source text, Markdown, and HTML source as text. For mixed Markdown or HTML, inspect hit positions first. If a hit falls inside protected code, attributes, or another non-prose span, do not run whole-file cleanup; clean only the prose segments or leave that hit unchanged. Do not pass binary containers such as PDF, DOCX, images, or archives.

For a chat-only response that is not written to a file, perform the rewrite workflow directly. Do not claim that the chat response received a deterministic post-send Unicode filter.

Code boundary

When prose and code are mixed, rewrite prose only. Never rename variables, alter string literals, reformat code, or change executable output as part of this skill. If a Markdown or HTML file contains executable snippets, preserve those spans byte-for-byte whenever practical.

Reporting

When the user asks for an audit, distinguish:

• Verifiable: Unicode characters removed or replaced, with script counts.
• Best-effort: prose rewritten to alter token and syntax patterns.
• Not established: official detector evasion, human authorship, or removal of a vendor's secret-key watermark.

For technical background, read references/watermark-notes.md. For misuse or disclosure questions, read references/responsible-use.md.