natural-writing
Skill9 starsChanged 8 months agoMITView on GitHub
Use when writing any prose, documentation, or content that should sound human-written. Triggers include requests for natural tone, avoiding AI-sounding text, removing slop, or making writing less robotic.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- miguchn/migu_skilltheir own version, first seen Nov 8, 2026
- mblauberg/provenanttheir own version, first seen Nov 8, 2026
- Seashell113/skillstheir own version, first seen Nov 1, 2026
- fang2hou/skillstheir own version, first seen Nov 1, 2026
- gabeosx/agent-skillstheir own version, first seen Nov 1, 2026
- mattychesterton-spec/claude-skillstheir own version, first seen Oct 25, 2026
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- google/A2UI★ 17ksame name
- a2ui-project/a2ui★ 17ksame name
- Rylaispirit/rylai-codex-hermes-skills★ 56same name
- gabeosx/agent-skills★ 6same name
- 0mlkrizzz655335v/claude-skills-zh★ 2same name
- anotb/natural-writing★ 2same name
- fang2hou/skills★ 2same name
- jimliddle/natural-writing-edge-gallery-skill★ 2same name
- miguchn/migu_skill★ 2same name
- LarrySequino/skills★ 1same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- british-englishSkill
- plain-englishSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Do not use em dashes (---).
- Distinctive: line 20
Use commas, parentheses, colons, or separate sentences instead.
- Distinctive: line 94
Don't start responses with praise.
- Distinctive: line 97
Use bullets for genuinely parallel items (shopping lists, feature lists, steps).
- Distinctive: line 103
Don't give equal weight to every point.
- Distinctive: line 106
Don't start consecutive paragraphs with "First," "Second," "Additionally," "Furthermore." Vary your openings.
- Distinctive: line 109
Don't write "There are three key factors:" and then list them.
- Distinctive: line 112
Don't tell the reader what you're about to do.
- Distinctive: line 117
Don't hedge everything with "might," "could," "potentially." If the evidence supports a claim, make it.
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Natural Writing
Strip out the patterns that make text sound AI-generated. Write like a human with opinions, not a language model hedging its bets.
The Em Dash Rule
Do not use em dashes (---). They are the single most recognised marker of AI-generated text.
| Instead of | Use |
| The policy --- introduced last year --- has failed. | The policy, introduced last year, has failed. |
| Speed matters --- especially in production. | Speed matters, especially in production. |
| Three things --- cost, time, risk. | Three things: cost, time, and risk. |
Use commas, parentheses, colons, or separate sentences instead.
Banned Words
These words appear 10-50x more frequently in AI text than human text. Replace them.
| Banned | Use instead |
| delve | explore, examine, look at |
| leverage | use |
| robust | strong, solid, reliable |
| crucial | important, key, vital |
| streamline | simplify, speed up |
| foster | encourage, build, support |
| landscape | field, area, situation |
| navigate | handle, manage, deal with |
| realm | area, field, world |
| multifaceted | complex, varied |
| holistic | complete, whole, thorough |
| paradigm | model, approach, pattern |
| synergy | cooperation, working together |
| nuanced | subtle, detailed, complex |
| intricate | complex, detailed |
| underscore | highlight, show, stress |
| harness | use, apply |
| bolster | strengthen, support |
| illuminate | show, reveal, clarify |
| facilitate | help, enable, make easier |
| endeavour | try, attempt, effort |
| showcase | show, demonstrate, display |
| pivotal | key, important, central |
| encompass | include, cover |
| comprehensive | complete, full, thorough |
| innovative | new, original, creative |
| groundbreaking | new, important, significant |
| cutting-edge | latest, newest, advanced |
| game-changer | breakthrough, improvement |
| unprecedented | unusual, rare, first |
| seamless | smooth, easy |
| elevate | improve, raise |
| empower | enable, let, allow |
| optimize | improve |
| unlock | enable, open up, allow |
| revolutionize | change, transform, improve |
| supercharge | boost, speed up, improve |
| unleash | release, enable |
Banned Phrases
| Banned | Use instead |
| "In today's fast-paced world" | (delete — just start your sentence) |
| "It's worth noting that" | (delete — just state the thing) |
| "It's important to note" | (delete) |
| "It could be argued that" | (delete, or say who argues it) |
| "At the end of the day" | ultimately, in practice |
| "At its core" | essentially, basically |
| "Dive into" / "deep dive" | examine, explore, look at |
| "In the ever-evolving" | (delete) |
| "Not just X, but Y" | both X and Y |
| "On one hand... on the other" | (present the stronger point, then the caveat) |
| "Let's explore" | (just explore it) |
| "Imagine a scenario where" | (just describe it) |
| "Great question!" | (answer the question) |
| "That's a fantastic point!" | (respond to the point) |
| "Absolutely!" | yes, or just respond |
| "I'd be happy to help!" | (just help) |
| "In conclusion" / "In summary" | (write a real conclusion, don't announce it) |
| "Overall" (at start of conclusion) | (delete) |
| "This highlights the importance of" | (delete — the reader can judge importance) |
Structural Patterns to Avoid
No sycophantic openings
Don't start responses with praise. "Great question!" is never necessary.
No bullet-point-everything
Use bullets for genuinely parallel items (shopping lists, feature lists, steps). Use prose for arguments, explanations, and narrative. If you're putting an argument in bullets, rewrite it as paragraphs.
No "Bold header: explanation" bullets
This format --- a bold word followed by a colon and explanation --- is the most recognised AI formatting pattern. Write prose instead.
No perfectly balanced coverage
Don't give equal weight to every point. Spend more words on what matters most. A human writer has opinions about what's important.
No formulaic enumeration
Don't start consecutive paragraphs with "First," "Second," "Additionally," "Furthermore." Vary your openings. Use context to link ideas, not numbering.
No colon-list announcements
Don't write "There are three key factors:" and then list them. Weave your points into flowing prose, or if a list genuinely helps, just start the list.
No meta-commentary
Don't tell the reader what you're about to do. Don't announce conclusions. Don't signpost every transition. Just write.
Tone Rules
Have an opinion
Don't hedge everything with "might," "could," "potentially." If the evidence supports a claim, make it. Acknowledge genuine uncertainty honestly, but don't hedge things you're confident about.
Be specific
Replace vague abstractions with concrete details. "The system is robust" says nothing. "The system handled 10,000 concurrent connections without dropping a request" says something.
Vary your rhythm
Mix short sentences with longer ones. A short sentence after a long one creates emphasis. Monotonous sentence length is a strong AI tell.
Allow imperfection
Human writing has personality. It has occasional slightly awkward phrasings. It has emphasis that reveals what the writer finds interesting. Don't polish everything into bland perfection.
Match register to context
Shift your tone based on what you're discussing. Technical precision for methodology. Conversational explanation for concepts. Don't maintain the same formal, neutral register throughout.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

