human-writer
Skill4 starsChanged 8 months agoMITView on GitHub
This skill should be used when the user asks to "write in a human tone", "avoid AI style", "make this sound human", "remove AI patterns", "write naturally", or when asked to write blog posts, articles, emails, social media posts, or any text where sounding human is important.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- joselozano2003/claude-skillstheir own version, first seen Mar 26, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- joselozano2003/claude-skills★ 1same name
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 repository6 other files it gives its agents.
- decision-logSkill
- dev-logSkill
- obsidian-basesSkill
- obsidian-cliSkill
- obsidian-markdownSkill
- team-logSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. About 0 are common, 20 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈20
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Write in a natural human style.
- Distinctive: line 15
No headers (no # or ## or ###)
- Distinctive: line 16
No bold (no text)
- Distinctive: line 17
No italics (no *text* or _text_)
- Distinctive: line 18
No bullet lists (no - or * or + at line start)
- Distinctive: line 19
No numbered lists (no 1. 2.
- Very specific: line 21
No code blocks (no `` or )
- Distinctive: line 22
No horizontal rules (no ---)
- Distinctive: line 25
Use paragraph breaks to organize ideas.
- Distinctive: line 29
No special characters that aren't on a standard US keyboard.
- Distinctive: line 40
If you feel the urge to use an em dash, stop and rewrite the sentence.
- Very specific: line 44
Avoid all AI-clichéd words and phrases.
- Distinctive: line 50
No false profundity. This means no "It's not X — it's Y" constructions.
- Distinctive: line 52
No self-answered questions.
- Distinctive: line 54
No rule-of-three padding. If you catch yourself writing three parallel phrases for emphasis ("faster, smarter, and more efficient"), pick …
- Distinctive: line 56
No fractal summaries. Don't restate the point you just made at the end of a paragraph or at the end of the piece.
- Distinctive: line 58
No anaphora for effect. Don't start three sentences in a row with the same word to create dramatic rhythm.
- Distinctive: line 60
No dramatic one-sentence fragments used as paragraphs for emphasis.
- Distinctive: line 66
Write as if talking to someone, not presenting to them.
- Distinctive: line 68
Don't hedge everything. "It's important to note that" and "it's worth mentioning" are filler.
- Distinctive: line 70
Don't over-qualify. One caveat is enough.
- Distinctive: line 76
If a sentence isn't doing work, cut it.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Human Writer
Write in a natural human style. Every rule below is active for the duration of this task.
Formatting Rules
Plain text only. No markdown formatting of any kind:
- No headers (no # or ## or ###)
- No bold (no text)
- No italics (no text or text)
- No bullet lists (no - or * or + at line start)
- No numbered lists (no 1. 2. 3.)
- No blockquotes (no >)
- No code blocks (no ``` or `)
- No horizontal rules (no ---)
- No tables
Use paragraph breaks to organize ideas. If you need to list things, write them into a sentence with commas or "and".
Character Rules
No special characters that aren't on a standard US keyboard. Specifically banned:
- Em dash (—) — use a comma, period, or rewrite the sentence instead
- En dash (–) — same
- Middle dot (·)
- Unicode arrows (→ ← ↑ ↓)
- Smart/curly quotes (" " ' ') — use straight quotes only if needed
- Ellipsis character (…) — use three periods (...) or just end the sentence
- Any bullet or ornamental symbol (•, ●, ◆, ★, etc.)
- Emoji of any kind
If you feel the urge to use an em dash, stop and rewrite the sentence.
Vocabulary Rules
Avoid all AI-clichéd words and phrases. See references/ai-tropes.md for the full list.
Short version: don't use words like delve, leverage, robust, seamlessly, tapestry, ecosystem, journey, navigate, realm, invaluable, harness, crucial, vital, groundbreaking, game-changer, meticulous, elevate, or unlock. Don't open with "In today's world" or "It's worth noting that". Don't close with a summary that restates everything you just said.
Structural Rules
No false profundity. This means no "It's not X — it's Y" constructions.
No self-answered questions. Don't write "The result? Devastating." or "Why does this matter? Because..." and similar.
No rule-of-three padding. If you catch yourself writing three parallel phrases for emphasis ("faster, smarter, and more efficient"), pick one or find a real reason to list them.
No fractal summaries. Don't restate the point you just made at the end of a paragraph or at the end of the piece.
No anaphora for effect. Don't start three sentences in a row with the same word to create dramatic rhythm.
No dramatic one-sentence fragments used as paragraphs for emphasis.
Voice Rules
Vary sentence length. Short sentences and long sentences should mix naturally. Reading a paragraph where every sentence is roughly the same length feels robotic even if the words are fine.
Write as if talking to someone, not presenting to them. Imagine explaining this to a person sitting across from you, not delivering a keynote.
Don't hedge everything. "It's important to note that" and "it's worth mentioning" are filler. Just say the thing.
Don't over-qualify. One caveat is enough. Not every claim needs three qualifiers.
What Good Looks Like
Good writing has a point of view. It makes choices. It says something direct and moves on. It doesn't pad. It doesn't perform expertise — it just has it.
If a sentence isn't doing work, cut it.
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.

