Generates AGENTS.md files for repository folders — coding agent context files with build commands, testing instructions, code style, project structure, and boundaries. Only generates where AGENTS.md is missing.
SkillScore91Maintained
Automatic
◆Doc Ops pack
Last verified 8/11/2026
What it changes
Passed 18 of 20 test cases with the skill, and 12 of 20 without it.
Without skill59%
With skill91%
Checks it passed that the model alone missed
Omits the Testing section completely
Reports that AGENTS.md already exists and was skipped
Generates a CLAUDE.md file that directs tools to read AGENTS.md
and 7 more in the full report
7 fixed13 passed either way2 still failing0 broke
Pass-rate lift
+32 pp
Tokens
+147%
Agent turns
0%
Response time
-22%
Model gemini-3.6-flashMeasured 8/11/2026v120 of 22 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
We need to define a specialized code reviewer persona named `reviewer.agent.md`. Should this be placed in an `AGENTS.md` file in the root or in `.github/agents/`?
What was checked, without and with the skill
Checked
Without skill
With skill
Explains that persona definitions belong in .github/agents/*.agent.md
Passed
Passed
Clarifies that AGENTS.md is strictly for repository code context
Missed
Passed
case-14 · gemini-3.6-flash · 8/11/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md367 linessingle file
AGENTS.md Generator
Generate high-quality AGENTS.md files for repository folders. Each file provides coding agents with project-specific context — build commands, testing instructions, code style, structure, and operational boundaries.
What is AGENTS.md
AGENTS.md complements README.md. README is for humans; AGENTS.md is for coding agents.
Predictable location — Agents look for AGENTS.md in the current directory, then walk up the tree
Nested files — Subfolders can have their own AGENTS.md that takes precedence over the root one
Separate from README — Keeps READMEs concise; agent-specific details (exact commands, boundaries, conventions) go here
NOT the same as .github/agents/*.agent.md — Those are agent persona definitions (who the agent is). AGENTS.md is project context (what the agent should know about this code)
Critical Guard: Only Generate If Missing
This is the single most important rule.
NEVER overwrite an existing AGENTS.md.
Before generating for ANY folder:
# Check if AGENTS.md already exists
ls AGENTS.md 2>/dev/null
If it exists → skip and report: "AGENTS.md already exists at <path> — skipping"
If it does not exist → proceed with generation
This check applies to every folder independently
Pertinent Folder Detection
Identify which folders should have an AGENTS.md:
Always generate for:
Repository root (/)
Wiki folder (wiki/) — if generated by deep-wiki (has package.json with VitePress)