create-agents-md
Skill12 starsChanged 4 months agoMITView on GitHub
Create concise, repository-specific AGENTS.md files with operational contract, precedence rules, and drift-control guidance.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- crbnos/carbontheir own version, first seen Nov 7, 2026
- AlessioScarfone/skillstheir own version, first seen Nov 6, 2026
- pahlevikun/levistacktheir own version, first seen Oct 25, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- crbnos/carbon★ 2.8ksame name
- AlessioScarfone/skills★ 0same name
- pahlevikun/levistack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- create-checkpointSkill
- create-project-instructionsSkill
- create-skillSkill
- create-usercontext-instructionsSkill
- repository-drift-controlSkill
- restore-checkpointSkill
- validate-agents-mdSkill
- validate-project-instructionsSkill
- validate-skillSkill
- validate-usercontext-instructionsSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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
- Distinctive: line 17
Use this skill when adding or refreshing repository AGENTS.md.
- Distinctive: line 18
Use this skill when repository map, precedence, and session controls must be documented concisely.
- Distinctive: line 19
Do not use this skill for project/user instruction file generation.
- Very specific: line 28
Run seven-phase discovery using references/discovery-phases.md.
- Distinctive: line 33
Ensure links/paths remain relative and repository-accurate.
- Distinctive: line 51
Do not duplicate full normative specs in AGENTS.
- Distinctive: line 53
Keep guidance deterministic and testable.
- Distinctive: line 54
Use relative path references only.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
Create AGENTS.md
Purpose
Generate a complete root AGENTS.md file that acts as an operational entrypoint while preserving source-of-truth and repository governance rules.
When To Use
- Use this skill when adding or refreshing repository
AGENTS.md. - Use this skill when repository map, precedence, and session controls must be documented concisely.
- Do not use this skill for project/user instruction file generation.
Required Inputs
- Repository purpose and canonical paths.
- Source precedence and key references.
- Session-state defaults and command namespace rules.
- Drift-control requirements.
Workflow
- Run seven-phase discovery using
references/discovery-phases.md. - Apply required element contract from
references/required-elements.md. - Generate artifact using
references/output-format.md. - Stamp
<!-- spec_version: 1.5.0 -->as an HTML comment at the top of the generatedAGENTS.md. - Validate result against
references/quality-checklist.md. - Ensure links/paths remain relative and repository-accurate.
Output Expectations
- One complete root
AGENTS.mdfile. - Includes purpose, precedence, repo map, command policy, and drift-control.
- Uses provider-neutral wording and valid relative links.
- Remains scannable and operationally actionable.
- Output contract and summary format follow
references/output-format.md.
Resources
- Discovery workflow:
references/discovery-phases.md - Required element contract:
references/required-elements.md - Output contract:
references/output-format.md - Quality checklist:
references/quality-checklist.md - Canonical template:
../../templates/AGENTS_template.md - Repository example:
../../AGENTS.md
Constraints And Safety
- Do not duplicate full normative specs in AGENTS.
- Preserve canonical path stability.
- Keep guidance deterministic and testable.
- Use relative path references only.
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.