humanizer
Skill58 starsChanged 2 months agoMITView on GitHub
Edit and rewrite SKILL.md prose to reduce signs of AI-generation and improve clarity, tone, and inclusivity. Useful for polishing skill descriptions and prompts.
187 other projects use a version of this.
Adopted by
Most recently taken up by
- vgteam/vgtheir own version, first seen Nov 16, 2026
- fluxmailai/fluxmailtheir own version, first seen Nov 16, 2026
- pantheon-org/tekhnetheir own version, first seen Nov 15, 2026
- nodetool-ai/nodetooltheir own version, first seen Nov 15, 2026
- oberemokis/skillstheir own version, first seen Nov 15, 2026
- alexandreeberhardt/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use economy-mode, personal-voice and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Microsoft AzureSkilleconomy-mode
Shifts Layer 3 model selection to cost-optimized alternatives when economy mode is active.
Also in 5 projects that use this
petermuirurithuoSkillpersonal-voice
Captures the user's personality, communication style, and values. Use this skill whenever responding to the user, drafting anything on their behalf (emails, CVs, messages, opinions, explanations), or whenever tone, word choice, or how an opinion is delivered matters. Apply it by default for any prompt, not only when the user explicitly asks for "my style" or "my voice.
Also in 3 projects that use this
Microsoft AzureSkillarchitectural-proposals
How to write comprehensive architectural proposals that drive alignment before code is written
Also in 3 projects that use this
- +9 more from Azure
Other versions187 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 187
- NousResearch/hermes-agent★ 264ksame name
- blader/humanizer★ 69ksame name
- The-Vibe-Company/quivr★ 40ksame name
- QuivrHQ/quivr★ 40ksame name
- rommapp/romm★ 14ksame name
- github/gh-aw★ 5.6ksame name
- latitude-dev/latitude-llm★ 4.8ksame name
- github/squad★ 3.4ksame name
- compozy/compozy★ 2.9ksame name
- memohai/Memoh★ 2.8ksame name
177 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 repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- biomeSkill
- bunSkill
- changesetSkill
- clackSkill
- dry-refactoringSkill
- github-awesome-copilot-git-commitSkill
- hr-root-router-maintainingSkill
- hr-skills-maintainingSkill
- jscpdSkill
- markdownSkill
- pdfSkill
- skill-vetterSkill
- turboSkill
- typescriptSkill
- valibotSkill
- hr-skillsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 174 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Ensure blank lines before lists and headings per repo rules
- Very specific: line 47
Always run bun run lint:md after rewrites to enforce markdown rules
- Very specific: line 48
Keep example prompts short and use [placeholders] consistently
- Very specific: line 50
Use this skill as a final pass before opening PRs to dev
“Common” is measured: kept by at least 6 in 10 of the 174 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
Humanizer
Supported tasks
- Rewrite SKILL.md sections to sound natural and human-authored
- Fix grammar, inclusive language, and remove AI artifacts
- Shorten long descriptions to fit trigger thresholds
- Ensure blank lines before lists and headings per repo rules
- Normalize phrasing for trigger phrases and placeholders
- Provide multiple tone variants (formal, friendly, concise)
- Generate reviewer-friendly diffs highlighting changes
- Produce suggestions for improving prompt clarity
Key prompts
Rewrite tasks
- "Rewrite this SKILL.md description to sound natural and clear: [text]."
- "Shorten and sharpen the description while keeping every trigger phrase and staying above the 50-character minimum — real descriptions in this repo run 250-700+ characters, so don't over-trim."
- "Convert this list of prompts into a consistent style and tone."
- "Generate three tone variants for the Tips section: formal, friendly, concise."
Quality enforcement
- "Check this file for missing blank lines between headings and lists per repo rules."
- "Flag inclusive language issues and suggest neutral replacements."
- "Provide a one-paragraph summary of changes suitable for a PR body."
- "Highlight any placeholders that don't follow
[placeholders]convention."
Tone and examples
- "Provide short example rewrites for this Tips section in a friendly tone: [text]."
- "Convert these technical examples into beginner-friendly language while preserving accuracy."
- "Generate three alternative opening lines for the SKILL description with different formality levels."
- "Suggest 4 sample prompt phrasings that follow the repo's
[placeholders]pattern."
Tips
- Always run
bun run lint:mdafter rewrites to enforce markdown rules - Keep example prompts short and use
[placeholders]consistently - Preserve technical accuracy when simplifying prose for non-technical readers
- Use this skill as a final pass before opening PRs to
dev
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.

