Use this skill whenever the user asks to write, rewrite, humanise, de-AI, or polish prose so it doesn't read as AI-generated — or to review a draft for signs of AI writing. Apply it before returning any substantial prose the user will publish.
npx skills add https://github.com/microsoft/cat-agent-skills --skill wikipedia-human-style-writing
Write and revise prose so it does not carry the tell-tale signs of AI-generated
text, using the patterns catalogued in Wikipedia's
The full pattern catalogue lives in references/ai-writing-tells.md — consult it
whenever you need the specific words-to-watch lists, examples, or the era-by-era
"AI vocabulary" breakdown.
giveaway is density and mechanical repetition, not a single instance. Target
clusters, not isolated words.
problem: vagueness, puffery, or unsupported claims. Restore the specific fact or
cut the empty claim — don't just swap the flagged word and leave hollow content.
quotes, dates, or sources. Keep the author's meaning, stance, and legitimate
emphasis. Do not "de-AI" a draft into corporate blandness.
banned. Use judgment over find-and-replace.
voice and audience.
references/ai-writing-tells.md,looking for clusters.
(regression-to-the-mean: "a revolutionary titan of industry" → the actual
achievement).
is/are/has in place of "serves as / stands as / boasts /features".
have noted").
templated "Challenges / Future prospects" wrap-ups.
"seamless").
boldface (not bold lead-in: on every list item), varied punctuation instead
of space-surrounded em-dash overuse, no emoji-as-bullets, no stray markdown or
copy-pasted smart-quote residue, and no "In conclusion / In summary" filler.
"sound less AI".
specific, human prose, not blandness.
Return the revised prose first, copy-ready. When a review was requested, or when
useful, follow it with a short bulleted list of the notable tells you found and how
you addressed them.
references/ai-writing-tells.md — the full field guide: every tell category withwords-to-watch, examples, the era-by-era AI-vocabulary breakdown, and formatting
tells. Read the relevant section whenever you need detail beyond the summary above.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
Take microsoft/wikipedia-human-style-writing from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.