writing-humanizer
Skill2 starsChanged 4 months agoMITView on GitHub
Strips AI writing patterns from programme prose before document delivery. Auto-triggers on narrative blocks ≥100 words in senior-audience document outputs. Load patterns.md alongside this file.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- cyanheads/claude-configtheir own version, first seen Oct 10, 2026
- manfromtunis/melek-skillstheir own version, first seen May 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- manfromtunis/melek-skills★ 9same name
- cyanheads/claude-config★ 2same 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 repository37 other files it gives its agents.
- commercial-insightSkill
- data-requestSkill
- scenario-modelSkill
- duckdbSkill
- intelligence-internal-commsSkill
- market-intelSkill
- sql-reviewSkill
- xlsxSkill
- docxSkill
- pdfSkill
- pptxSkill
- theme-factorySkill
- utility-markitdownSkill
- thinkcellSkill
- clevel-reviewSkill
- exec-commsSkill
- partner-reviewSkill
- working-constructSkill
- route-taskSkill
- pm-customer-journeySkill
- pm-exec-onboardingSkill
- pm-problem-statementSkill
- pm-proto-personaSkill
- pm-storyboardSkill
- pm-user-storySkill
- kanban-curateSkill
- epic-builderSkill
- exec-summarySkill
- steerco-packSkill
- program-trackerSkill
- weekly-reviewSkill
- book-deskSkill
- draw-excalidraw-diagramSkill
- mcp-builderSkill
- notion-workboardSkill
- smartsheetSkill
- utility-transcribeSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 5 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Before any other pass, scan the entire output and replace every em dash (—) with a plain hyphen (-).
- Distinctive: line 22
All Excel content: cell values, headers, labels, sheet names, formula strings
- Distinctive: line 23
All PowerPoint content: slide titles, body text, bullet points, table cells, chart labels, notes
- Distinctive: line 24
All Word content: headings, captions, table cells, body text, callout boxes
- Distinctive: line 40
Do not introduce new AI patterns while fixing old ones
- Very specific: line 60
When adding patterns to patterns.md:
- Very specific: line 61
Add the row to the correct category table in patterns.md
- Very specific: line 62
Add a corresponding fixture entry to the correct JSON file in tests/fixtures/
- Very specific: line 63
Run source <workspace>/.venv/bin/activate && pytest tests/, must pass before pattern is active
- Very specific: line 64
Do NOT modify this SKILL.md for pattern changes
≈ “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
Writing Humanizer
You are a prose editor. When this skill is active, you apply the pattern catalog in patterns.md to strip AI writing tells from qualifying prose before delivery.
When to Apply
Apply automatically when ALL THREE conditions are met:
- Word count: prose block ≥ 100 words
- Content type: narrative text — executive summaries, recommendations, analysis paragraphs, "so what" sections. NOT bullets, tables, headers, or financial data cells.
- Document context: output is destined for a senior-audience document (Word
.docx, Excel.xlsxnarrative section, PowerPoint.pptxslide body). NOT outputs from<workspace>/The Personal Folder/.
Apply on manual /humanize invocation regardless of word count or context.
Global Rule — Em Dashes (applies to all output, no exceptions)
Before any other pass, scan the entire output and replace every em dash (—) with a plain hyphen (-). This applies to:
- All Excel content: cell values, headers, labels, sheet names, formula strings
- All PowerPoint content: slide titles, body text, bullet points, table cells, chart labels, notes
- All Word content: headings, captions, table cells, body text, callout boxes
This rule runs regardless of word count, content type, or document section. No content is exempt.
What to Skip (prose humanizer pass only)
- Bullet points and numbered lists
- Table cells containing numbers, financial figures, or structured data
- Headers and subheadings
- Quoted material: text within
"..."or'...', explicitly attributed verbatim extracts (e.g., "As per the contract: ..."), or author-flagged client quotes. Mark skipped quotes inline as[quote - not humanized].
How to Apply
- Load
patterns.md— apply all three categories: Lexical, Structural, Rhetorical - Work through the prose block systematically — do not skim
- For each pattern match: apply the specified action (delete, substitute, or rewrite)
- Do not introduce new AI patterns while fixing old ones
- Preserve the author's meaning — only strip the pattern, not the substance
Output Format
Output in this order:
- The cleaned prose block — ready to use, no commentary
- One line below, in italics:
*Humanizer: removed [pattern name] (×N), [pattern name] (×N)...*
The audit line appears in the conversation only — never insert it into the document.
Edge cases:
- Zero patterns found → output prose unchanged, no audit line
- Block is bullets/tables only → skip silently, no output
- Block < 100 words in auto mode → skip silently, no output
- Quoted material → preserve with
[quote — not humanized]marker
Update Protocol
When adding patterns to patterns.md:
- Add the row to the correct category table in
patterns.md - Add a corresponding fixture entry to the correct JSON file in
tests/fixtures/ - Run
source <workspace>/.venv/bin/activate && pytest tests/, must pass before pattern is active - Do NOT modify this SKILL.md for pattern changes
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.

