agentleFS
Sign inStart free
aurokinaurokin/skills-manager/skills/humanizer/AGENTS.md

skills-manager / humanizer

AGENTS.md3 starsChanged 6 months agoMITView on GitHub

This file explains how to change Humanizer without breaking its package or prompt. Humanizer is an agent skill written in Markdown. SKILL.md is the prompt that agents read. The repo has no build step. Keep the skill portable. Do not write instructions that limit it to one or two agent tools. Keep SKILL.md and README.md in sync. Use Plain Language in code comments, prompts, documentation, descriptions, validation messages, and progress reports.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 4

    1. danieleteti/delphimvcframework★ 1.4k100% same
    2. Fischer1120/agent-workflows★ 2100% same
    3. AI-Degen-69/issue-to-pr-skills★ 0100% same
    4. Ricardo-kui/claude-skills★ 0100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    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.

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository8 other files it gives its agents.

The file

Show its rules and text

We split this AGENTS.md into the rules it gives an agent

18 rules. About 0 are common, 14 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep the skill portable. Do not write instructions that limit it to one or two agent tools.

    line 9
  2. Very specific:

    Keep SKILL.md and README.md in sync.

    line 21
  3. Very specific:

    Version: Keep the same version in SKILL.md under metadata.version, the first README version entry, and .claude-plugin/plugin.json.

    line 24
  4. Distinctive:

    Compatibility: Keep install and use instructions neutral across agents.

    line 25
  5. Distinctive:

    History: Add a short README version note for any behavior change or non-obvious fix.

    line 26
  6. Very specific:

    Checks: Before publishing, run python3 scripts/validate-package.py, npx skills add .

    line 27
  7. Distinctive:

    Use Plain Language in code comments, prompts, documentation, descriptions, validation messages, and progress reports.

    line 31
  8. Distinctive:

    Use common words and active voice.

    line 34
  9. Distinctive:

    Keep sentences and paragraphs short.

    line 35
  10. Distinctive:

    Use one term for the same item.

    line 36
  11. Very specific:

    Use must for requirements.

    line 37
  12. Distinctive:

    Use headings, lists, and tables when they help the reader.

    line 38
  13. Distinctive:

    Remove repeated or unnecessary words.

    line 39
  14. Distinctive:

    Keep exact identifiers, commands, paths, schema fields, quotations, watched phrases, and behavior-bearing examples.

    line 42
  15. Distinctive:

    Keep the full technical meaning.

    line 43
  16. Distinctive:

    Keep the YAML metadata valid.

    line 47
  17. Distinctive:

    Treat the prompt below the metadata as the product.

    line 48
  18. Distinctive:

    Prefer a short, clear instruction over another exception or repeated explanation.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

Guide for agents

This file explains how to change Humanizer without breaking its package or prompt.

What this repo contains

Humanizer is an agent skill written in Markdown. SKILL.md is the prompt that agents read. The repo has no build step.

Keep the skill portable. Do not write instructions that limit it to one or two agent tools.

Key files

  • SKILL.md is the source of truth and the repo's only skill file. It contains portable YAML metadata, 35 numbered patterns, and their examples.
  • README.md explains installation, use, patterns, and version history.
  • .claude-plugin/plugin.json describes the Claude plugin and points its skill loader at the root SKILL.md.
  • .claude-plugin/marketplace.json lets users add this repo as a Claude marketplace.
  • scripts/validate-package.py checks package files and shared values.

Rules for changes

Keep SKILL.md and README.md in sync.

  • Patterns: The skill has 35 numbered patterns. If you add, remove, or renumber a pattern, update the README table, heading, validator, and every pattern reference.
  • Version: Keep the same version in SKILL.md under metadata.version, the first README version entry, and .claude-plugin/plugin.json. Do not add a top-level version field to the skill.
  • Compatibility: Keep install and use instructions neutral across agents. Names such as Claude Code, OpenCode, and Codex are examples, not limits.
  • History: Add a short README version note for any behavior change or non-obvious fix.
  • Checks: Before publishing, run python3 scripts/validate-package.py, npx skills add . --list, and claude plugin validate ..

Writing style

Use Plain Language in code comments, prompts, documentation, descriptions, validation messages, and progress reports.

  • Lead with the main point.
  • Use common words and active voice.
  • Keep sentences and paragraphs short.
  • Use one term for the same item.
  • Use must for requirements.
  • Use headings, lists, and tables when they help the reader.
  • Remove repeated or unnecessary words.
  • Limit acronyms and explain technical terms.
  • Avoid double negatives.
  • Keep exact identifiers, commands, paths, schema fields, quotations, watched phrases, and behavior-bearing examples.
  • Keep the full technical meaning.

Editing the skill

  • Keep the YAML metadata valid.
  • Treat the prompt below the metadata as the product.
  • Prefer a short, clear instruction over another exception or repeated explanation.

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.

Check your setup, free