humanize-copy
Skill0 starsChanged 9 days agoMITView on GitHub
Rewrite AI-sounding prose (emails, docs, web copy) into plain human English. Use when copy "sounds like AI", "too corporate", "make it plain English", "de-AI this". Mechanics only. Never run on LLM-facing files (skills, runbooks), where precision beats rhythm.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- KyaniteLabs/tastechecktheir own version, first seen Nov 10, 2026
- millwright-labs/humanize-copy-skilltheir own version, first seen Aug 24, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- KyaniteLabs/tastecheck★ 12same name
- millwright-labs/humanize-copy-skill★ 0same 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 repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- call-debriefSkill
- company-contextSkill
- crm-recordsSkill
- meeting-prepSkill
- pipeline-analysisSkill
- product-contextSkill
- sales-call-scorerSkill
- sales-intakeSkill
- sales-playbookSkill
- setupSkill
- weekly-exec-updateSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Use the buyer's own words where you have them (clients/<slug>/intelligence.md).
- Distinctive: line 29
Do not invent claims while rewriting.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Humanize copy
Kill list
- Em dashes in outgoing copy. Use a comma, a period or parentheses.
- "Not X, but Y" constructions and "it's not just X" openers. Say what it is.
- "Happy to", "I hope this finds you well", "just circling back", "leverage", "unlock", "seamless", "robust", "game-changer", "in today's fast-paced world".
- A punchy one-line tagline at the end of a paragraph.
- Triplets by reflex ("fast, simple, and powerful").
- Hedging stacks ("may potentially help to").
Rhythm
- Vary sentence length. One short sentence after two long ones.
- One idea per sentence.
- Use the buyer's own words where you have them (
clients/<slug>/intelligence.md).
Rule
Do not invent claims while rewriting. Restructure, cut, and reorder the words you were given.
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.

