agentleFS
abduallahJamalabduallahJamal/humanizer-skills/AGENTS.md

humanizer-skills

AGENTS.md0 starsChanged 10 days agoMITView on GitHub

skills/ is the single canonical source of truth for all five Agent Skills (humanize, humanize-text, ai-writing-detector, anti-slop-coder, academic-humanizer).

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Flat depth-1 discovery: Every skill directory must remain directly under <root>/<skill-name>/SKILL.md so @deepseek-ai/dsh-skill-filesystem …

    line 8
  2. Very specific:

    Strict frontmatter: Keep description in YAML frontmatter as a single-line double-quoted string so strict parsers in OpenCode and DeepSeek …

    line 9
  3. Very specific:

    Zero external dependencies: All scripts under skills/*/scripts/ must use Python 3.9+ standard library only.

    line 10
  4. Very specific:

    Pre-commit check: Always run ./scripts/sync-platforms.sh --check && python3 scripts/validate.py before committing.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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

Repository Contract (AGENTS.md)

skills/ is the single canonical source of truth for all five Agent Skills (humanize, humanize-text, ai-writing-detector, anti-slop-coder, academic-humanizer).

Invariants

  1. Edit only inside skills/<skill-name>/ and then run ./scripts/sync-platforms.sh to mirror changes identically into .opencode/skills/, .claude/skills/, .agents/skills/, and .dsh/skills/.
  2. Flat depth-1 discovery: Every skill directory must remain directly under <root>/<skill-name>/SKILL.md so @deepseek-ai/dsh-skill-filesystem (DeepSeek Harness) discovers all skills without silent category-folder skipping.
  3. Strict frontmatter: Keep description in YAML frontmatter as a single-line double-quoted string so strict parsers in OpenCode and DeepSeek Harness never skip a skill on unquoted colons.
  4. Zero external dependencies: All scripts under skills/*/scripts/ must use Python 3.9+ standard library only.
  5. Pre-commit check: Always run ./scripts/sync-platforms.sh --check && python3 scripts/validate.py before committing.

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.