agentleFS
Sign inStart free
agentstationagentstation/skills/AGENTS.md

skills

AGENTS.md1 starsChanged 2 months agoMITView on GitHub

Canonical reusable skills live under <name>/SKILL.md. - Follow the current Agent Skills specification at https://agentskills.io. - Keep global skills product-agnostic. - Put project-specific profiles in the owning project's skills repository. - Keep SKILL.md concise and move conditional reference material behind direct pointers. - Prefer executable enforcement for security and model-selection boundaries. - Record derivative skill provenance and upstream commit IDs. - Validate all skills with scripts/validate-skills after each skill change. - Run each changed skill's own tests. Use GLOSSARY.md for…

  • 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,843 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 repository9 other files it gives its agents.

The file

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

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

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

    Follow the current Agent Skills specification at https://agentskills.io.

    line 5
  2. Very specific:

    Keep global skills product-agnostic.

    line 6
  3. Very specific:

    Put project-specific profiles in the owning project's skills repository.

    line 7
  4. Very specific:

    Keep SKILL.md concise and move conditional reference material behind direct pointers.

    line 8
  5. Distinctive:

    Prefer executable enforcement for security and model-selection boundaries.

    line 10
  6. Distinctive:

    Run each changed skill's own tests.

    line 13
  7. Very specific:

    Use GLOSSARY.md for developer-facing prose.

    line 17

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

AgentStation Skills

Canonical reusable skills live under <name>/SKILL.md.

  • Follow the current Agent Skills specification at https://agentskills.io.
  • Keep global skills product-agnostic.
  • Put project-specific profiles in the owning project's skills repository.
  • Keep SKILL.md concise and move conditional reference material behind direct pointers.
  • Prefer executable enforcement for security and model-selection boundaries.
  • Record derivative skill provenance and upstream commit IDs.
  • Validate all skills with scripts/validate-skills after each skill change.
  • Run each changed skill's own tests.

Technical writing

Use GLOSSARY.md for developer-facing prose. Run the installed technical-writing linter on durable technical text.

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