damslethdamsleth/SKILLS/AGENTS.md

SKILLS

AGENTS.md1 starsChanged 32 days agoMITView on GitHub

Public, reusable agent skills (Claude Code, Codex, Copilot). One folder per skill: <skill>/SKILL.md plus optional references/, assets/, agents/ and a bundled CLI. See README.md for the skill table and installer usage. CI (.github/workflows/ci.yml) runs the same two scripts.

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,439 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 repository19 other files it gives its agents.
- cj-abSkill
- cj-ambitionSkill
- cj-automateSkill
- cj-cloudflare-workerSkill
- cj-code-reviewSkill
- cj-dailySkill
- cj-meetingsSkill
- cj-notesSkill
- cj-nowSkill
- cj-owa-toolsSkill
- cj-thingsSkill
- cj-todoSkill
- cj-uxloopSkill
- cj-video-visionSkill
- cj-voice-dnaSkill
- repo-deepSkill
- repo-depsSkill
- repo-groomSkill
- repo-healthSkill

The file

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

2 rules. About 0 are common, 0 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
No hardcoded user paths (/Users/<name>, /home/<name>) in SKILL.md.
line 19
Very specific:
No agent-specific tool names (ask_user_input, web_search, str_replace, …) in SKILL.md prose.
line 20

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

Public, reusable agent skills (Claude Code, Codex, Copilot). One folder per skill: <skill>/SKILL.md plus optional references/, assets/, agents/ and a bundled CLI. See README.md for the skill table and installer usage.

Check

scripts/lint.sh   # SKILL.md frontmatter, paths, tool names, shellcheck, README table, agent YAML
scripts/test.sh   # cj-todo + install-skill.sh behaviour
git config core.hooksPath scripts/hooks   # run lint.sh on every commit

CI (.github/workflows/ci.yml) runs the same two scripts.

Ground rules

No hardcoded user paths (/Users/<name>, /home/<name>) in SKILL.md; lint fails on them.
No agent-specific tool names (ask_user_input, web_search, str_replace, …) in SKILL.md prose; skills must port across agents.
Adding or renaming a skill means updating the README skill table; lint checks it.
Personal or machine-specific skills go in the private SKILLS-private repo, not here.

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