mcpbeat Sign in

Wikipedia Human Style Writing Agent Skill

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.

4k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
60 d ago
last touched
this folder, not the whole repository

Install

one command, takes just this skill from the repository
npx skills add https://github.com/microsoft/cat-agent-skills --skill wikipedia-human-style-writing

What comes with it

10 124 bytes besides the instruction
README.md
metadata.json
references/ai-writing-tells.md

The instruction itself

6 sections, as written by the author

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

Signs of AI writing.

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.

Operating principles

  • Signs, not sins. Every pattern below can appear in good human writing. The

giveaway is density and mechanical repetition, not a single instance. Target

clusters, not isolated words.

  • Fix the cause, not the symptom. Most tells are surface markers of a deeper

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.

  • Preserve the truth and the voice. Never invent or drop facts, figures,

quotes, dates, or sources. Keep the author's meaning, stance, and legitimate

emphasis. Do not "de-AI" a draft into corporate blandness.

  • Descriptive, not prescriptive. These words and shapes are overused, not

banned. Use judgment over find-and-replace.

Workflow

  • Read the whole draft first; note the core message, key facts, and the intended

voice and audience.

  • Sweep the draft against the tell categories in references/ai-writing-tells.md,

looking for clusters.

  • Revise each cluster by fixing the underlying issue:
  • Replace generic praise with the specific, concrete fact

(regression-to-the-mean: "a revolutionary titan of industry" → the actual

achievement).

  • Cut empty significance/legacy flourishes and trailing "-ing" analysis clauses.
  • Restore plain is/are/has in place of "serves as / stands as / boasts /

features".

  • Name a real source or delete a vague attribution ("experts argue", "observers

have noted").

  • Break up mechanical rule-of-three lists, "not just X but Y" parallelisms, and

templated "Challenges / Future prospects" wrap-ups.

  • Remove promotional/travel-brochure tone ("vibrant", "nestled", "rich tapestry",

"seamless").

  • Thin out an over-dense cluster of era-specific "AI vocabulary" words.
  • Clean the formatting tells: sentence-case headings (not Title Case), sparing

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.

  • Re-read against the original to confirm no meaning, fact, or nuance drifted.

Guardrails

  • Do not add, remove, or alter facts, numbers, quotes, or citations to make text

"sound less AI".

  • Do not strip emphasis or specificity that the source genuinely supports.
  • Do not flatten a distinctive human voice into neutral mush — the goal is natural,

specific, human prose, not blandness.

  • One or two flagged words are usually fine; don't over-correct isolated hits.

Output

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.

Reference

  • references/ai-writing-tells.md — the full field guide: every tell category with

words-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.

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

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.

4k tokens
Changelog Generator
by frostant
×9

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.

774 tokens
Test Driven Development
by w95
×7

Use when implementing any feature or bugfix, before writing implementation code

2k tokens
Writing Plans
by ZhanlinCui
×4

Use when you have a spec or requirements for a multi-step task, before touching code

816 tokens
Writing Skills
by ZhanlinCui
×4

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts
Crafting Effective Readmes
by softaworks
×3

Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.

15k tokens
Humanizer
by softaworks
×3

| 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.

6k tokens
Opentrons Integration
by christophacham
×3

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.

9k tokens scripts

How to use it

Copy the folder

Take microsoft/wikipedia-human-style-writing from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.