agent-skills
AGENTS.md6 starsChanged 4 months agoMITView on GitHub
Compatibility shim pointing to CLAUDE.md. Source of truth for multi-agent skill conventions.
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,700 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 repository27 other files it gives its agents.
- agent-skills-claudeCLAUDE.md
- agent-log-forensicsSkill
- changelog-writerSkill
- chezmoi-driftSkill
- contacts-unifySkill
- decision-logSkill
- dependency-pinningSkill
- django-smoke-alarmSkill
- empathy-auditSkill
- first-contactSkill
- handle-prSkill
- launch-sequenceSkill
- parallel-isolated-app-testingSkill
- post-mortemSkill
- pre-mortemSkill
- profile-meSkill
- ralph-loopSkill
- release-operatorSkill
- remote-host-verifierSkill
- research-personSkill
- scope-hammerSkill
- second-opinionsSkill
- status-copy-trust-auditSkill
- support-stormSkill
- trust-auditSkill
- visual-qa-loopSkill
- wide-open-brainstormSkill
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Every skill and script must work across agents, not just Claude:
- Distinctive: line 19
Skill instructions: must be written in plain language, not Claude-specific syntax
- Very specific: line 20
Scripts: must be standalone (PEP 723 headers, try/except ImportError fallbacks) — no agent-specific tooling required to run them
- Very specific: line 22
Run python3 scripts/sync_codex_packaging.py after any skill changes to keep Codex packaging current
- Very specific: line 38
Use ${CLAUDE_SKILL_DIR} (or the agent-equivalent env var) to reference bundled files at runtime
≈ “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
AGENTS.md
Source of truth: CLAUDE.md This file is a thin compatibility shim. All conventions, structure, and requirements live in CLAUDE.md. Read that first.
What This Repo Is
A shared skill collection designed to work across multiple AI coding agents — Claude Code, Codex, Copilot, Gemini CLI, and any agent that follows the Agent Skills open standard. Skills are agent-agnostic by design.
Multi-Agent Support Is Required
Every skill and script must work across agents, not just Claude:
- Skill instructions must be written in plain language, not Claude-specific syntax
- Scripts must be standalone (PEP 723 headers,
try/except ImportErrorfallbacks) — no agent-specific tooling required to run them - Distribution uses both Claude Code marketplace (
.claude-plugin/) and Codex plugin packaging (.agents/,plugins/) — both must stay in sync - Run
python3 scripts/sync_codex_packaging.pyafter any skill changes to keep Codex packaging current
Tool Name Mapping
Skills use Claude Code tool names in their instructions. Other agents should consult their platform's mapping:
- Codex:
references/codex-tools.md - Copilot CLI:
references/copilot-tools.md - Gemini CLI: tool mapping is loaded automatically via GEMINI.md
Creating or Modifying Skills
See CLAUDE.md for full conventions. Short version:
- Skill lives in
skills/<name>/SKILL.mdwith YAML frontmatter (name,descriptionrequired) - Scripts go in
skills/<name>/scripts/— standalone, PEP 723, works without any agent - Register in
.claude-plugin/marketplace.jsonfor Claude, then run the sync script for Codex - Use
${CLAUDE_SKILL_DIR}(or the agent-equivalent env var) to reference bundled files at runtime
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.

