UX writing skill for Claude. Humanizes AI copy, fixes microcopy, kills em dashes. Writing, not fighting.
SaferSkills independently audited ill-communication (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
A skill with two modes. Decide which one applies, then follow it.
references/microcopy.md before responding. For general prose, read references/ai-tells.md and audit against the full catalogue.Em dashes (—) must never appear in any output: chat, documents, slides, code comments, headings, anywhere. Replace case by case so the sentence reads naturally:
Never substitute a double hyphen (--) or a spaced hyphen ( - ) doing dash work. Never use an en dash (–) as a stand-in for an em dash in running prose. Hyphens in compounds are fine (well-designed, opt-in). En dashes in ranges are fine (2019–2024, 9am–5pm).
Avoid comma overload when removing dashes. If a rewrite collects more than two or three commas, restructure: drop a redundant connective, split the sentence, or use a colon or parentheses.
When editing text supplied by the user, strip its em dashes too. Only verbatim quotes that must stay word-for-word accurate keep original punctuation.
Default to British English (colour, organise, licence as noun). Switch only when the user asks or the product context clearly demands it (for example, copy for a US product). Whichever locale applies, apply it consistently.
Do not "humanize" the following. Flag concerns instead and let the user decide:
Before delivering, scan the output:
references/ai-tells.md).Read references/voice-profile.md and treat it as the source of truth for tone. If the profile is unfilled, use its defaults (plain, direct, specific, warm but not chummy) and, for substantial writing tasks, offer the user the chance to fill it in or paste a sample of their writing to match.
When the user pastes a writing sample, match its sentence rhythm, vocabulary level, and quirks rather than producing generic clean prose. Varied sentence length is a feature of human writing; uniform rhythm is a tell.
The full catalogue with examples lives in references/ai-tells.md. Read it whenever you are in review mode, writing anything longer than a couple of paragraphs, or unsure whether something is a tell. The most common offenders:
references/ai-tells.md: the full AI writing pattern catalogue with before/after examples. Read in review mode, and in write mode for anything substantial.references/microcopy.md: UX writing craft for interface copy: buttons, errors, empty states, forms, notifications, accessibility, plain language, localization. Read whenever the task involves interface copy or a user journey.references/voice-profile.md: the user's tone of voice profile. Read at the start of any writing or review task. The user fills this in; respect it over generic style advice.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.