agent-skills-archive
AGENTS.md1 starsChanged 5 months agoMITView on GitHub
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 repository14 other files it gives its agents.
- agent-skills-archive-orchestratorSkill
- call-r-lib-in-pythonSkill
- code-commenterSkill
- code-reviewerSkill
- end-user-xp-improverSkill
- fp-developerSkill
- lesson-documenterSkill
- plan-designerSkill
- preferred-workflowSkill
- release-preparerSkill
- scientific-prose-editorSkill
- simple-code-writerSkill
- spec-driven-developerSkill
- wayback-link-fallbackSkill
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
- Very specific: line 23
When necessary CLI tools (e.g., uv, gh, hf) are not found, to address path config issues, try which <tool> to figure out right paths.
≈ “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.
Files
Repository Agents Guide
What
- This repo is an archive and development workspace for reusable coding-agent skills.
- Deployable skills live only under
skills/<skill-name>/; each skill must includeSKILL.mdwithnameanddescriptionYAML frontmatter. - The project harness lives under
.agents/,docs/harness/, and_workspace/; it guides work on this repo and is not deployable archive content.
Why
- Keeping archive skills separate from repo-local harness guidance prevents accidental deployment of project-only workflows.
- The deploy CLI depends on stable skill directory names and frontmatter metadata.
How
- List skills:
uv run deploy-skills --list-skills - Preview deployment:
uv run deploy-skills --dry-run --skill <skill-name> - Run tests:
uv run python -m unittest discover -s tests - For skill creation or maintenance workflow, use
.agents/skills/agent-skills-archive-orchestrator/SKILL.mdanddocs/harness/agent-skills-archive/team-spec.md.
Etc.
- When necessary CLI tools (e.g.,
uv,gh,hf) are not found, to address path config issues, trywhich <tool>to figure out right paths.
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
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.