agentleFS
JipletJiplet/transformation-os/skills/utility/utility-writing-humanizer/SKILL.md

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

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
  1. Distinctive:

    Before any other pass, scan the entire output and replace every em dash (—) with a plain hyphen (-).

    line 21
  2. Distinctive:

    All Excel content: cell values, headers, labels, sheet names, formula strings

    line 22
  3. Distinctive:

    All PowerPoint content: slide titles, body text, bullet points, table cells, chart labels, notes

    line 23
  4. Distinctive:

    All Word content: headings, captions, table cells, body text, callout boxes

    line 24
  5. Distinctive:

    Do not introduce new AI patterns while fixing old ones

    line 40
  6. Very specific:

    When adding patterns to patterns.md:

    line 60
  7. Very specific:

    Add the row to the correct category table in patterns.md

    line 61
  8. Very specific:

    Add a corresponding fixture entry to the correct JSON file in tests/fixtures/

    line 62
  9. Very specific:

    Run source <workspace>/.venv/bin/activate && pytest tests/, must pass before pattern is active

    line 63
  10. Very specific:

    Do NOT modify this SKILL.md for pattern changes

    line 64

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. Word count: prose block ≥ 100 words
  2. Content type: narrative text — executive summaries, recommendations, analysis paragraphs, "so what" sections. NOT bullets, tables, headers, or financial data cells.
  3. Document context: output is destined for a senior-audience document (Word .docx, Excel .xlsx narrative section, PowerPoint .pptx slide 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

  1. Load patterns.md — apply all three categories: Lexical, Structural, Rhetorical
  2. Work through the prose block systematically — do not skim
  3. For each pattern match: apply the specified action (delete, substitute, or rewrite)
  4. Do not introduce new AI patterns while fixing old ones
  5. Preserve the author's meaning — only strip the pattern, not the substance

Output Format

Output in this order:

  1. The cleaned prose block — ready to use, no commentary
  2. 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:

  1. Add the row to the correct category table in patterns.md
  2. Add a corresponding fixture entry to the correct JSON file in tests/fixtures/
  3. Run source <workspace>/.venv/bin/activate && pytest tests/, must pass before pattern is active
  4. Do NOT modify this SKILL.md for pattern changes

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.