agentleFS
Sign inStart free
liorhai5liorhai5/ai-skills/AGENTS.md

ai-skills

AGENTS.md0 starsChanged 2 months agoMITView on GitHub

This repo hosts SKILL.md skills under skills/<name>/. For the human-facing overview and skill list, see README.md. Each skill is a folder at skills/<name>/ containing: - One skill per folder; folder name matches frontmatter name. - description should state when to invoke the skill, not just what it does. - Keep SKILL.md body terse — push details into references/. - No bundled libraries. A skill's scripts use only language built-ins; anything more is served by tools detected on the user's machine…

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

The file

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

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep SKILL.md body terse — push details into references/.

    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

ai-skills — agent guide

This repo hosts SKILL.md skills under skills/<name>/. For the human-facing overview and skill list, see README.md.

Skill format (agentskills)

Each skill is a folder at skills/<name>/ containing:

  • SKILL.md with frontmatter: name, description, optional argument-hint
  • Optional references/, scripts/, assets/

Authoring conventions

  • One skill per folder; folder name matches frontmatter name.
  • description should state when to invoke the skill, not just what it does.
  • Keep SKILL.md body terse — push details into references/.
  • No bundled libraries. A skill's scripts use only language built-ins; anything more is served by tools detected on the user's machine (any capable tool, not one hard-wired library), with an install suggestion when none is found — never a silent install, never a package.json/node_modules inside a skill.
  • Verification corpora live under tests/<skill>/ at the repo root — they are for maintaining this repo and never ship with a skill.

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