agents-md-generator
Skill68 starsChanged 7 months agoApache-2.0View on GitHub
Create, audit, or compact repository instructions in AGENTS.md, scoped overrides, and requested tool compatibility files. Use to preserve non-obvious project rules while removing stale, duplicated, or generic guidance.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- realRoc/skillstheir own version, first seen Nov 15, 2026
- n-n-code/n-n-code-skillstheir own version, first seen Nov 1, 2026
- zhengwenxuan1991/skillstheir own version, first seen Sep 19, 2026
- Eriemon/agents-md-generatortheir own version, first seen Aug 26, 2026
- slogsdon/skills-workflowstheir own version, first seen Aug 4, 2026
- MADTeacher/mad-agents-skillstheir own version, first seen May 1, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- MADTeacher/mad-agents-skills★ 106same name
- Eriemon/agents-md-generator★ 14same name
- n-n-code/n-n-code-skills★ 4same name
- jleivo/skills★ 1same name
- realRoc/skills★ 1same name
- zhengwenxuan1991/skills★ 1same name
- slogsdon/skills-workflows★ 0same name
- uts58/my-random-skills★ 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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brainstorm-firstSkill
- debugging-workflowSkill
- design-system-generatorSkill
- docker-local-devSkill
- documentation-guidelinesSkill
- laravel-11-12-app-guidelinesSkill
- laravel-13-app-guidelinesSkill
- office-web-ui-systemSkill
- performance-optimizationSkill
- project-development-mindsetSkill
- run-reviewable-subtask-loopSkill
- testing-verificationSkill
- ui-ux-concept-implementationSkill
- vps-docker-traefik-deploySkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Run in the main conversation by default.
- Distinctive: line 28
Read discovery.md for detector details or tool-compatibility.md when loading order and supported tool behavior affect the output.
- Distinctive: line 32
Keep a rule when it is non-obvious, supported by project evidence, useful across tasks, and concrete enough to follow.
- Distinctive: line 34
Remove or rewrite generic advice, personas, duplicated rules, obsolete commands, exhaustive inventories, mandatory questionnaires, …
- Distinctive: line 36
Keep detailed design, API, testing, and deployment guidance in their existing owners, linked with a clear read condition.
- Distinctive: line 42
Use output-template.md as a menu.
- Distinctive: line 46
Use tracked diffs for recovery.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AGENTS.md Generator
Produce a small instruction layer containing verified project facts that materially change agent behavior. General engineering knowledge belongs outside always-loaded instructions.
Delegation
Run in the main conversation by default. Delegation can increase usage: obtain explicit approval for the proposed agent count and scope before using subagents. Reuse that approval within its bounds; ask again before expanding the approved count or scope.
Discover the instruction chain
Inspect existing instructions, their ownership, scopes, and symlinks before editing. Preserve a working shared source such as AGENTS.md pointing to CLAUDE.md; do not replace it solely to impose a preferred filename. Add compatibility files only when the requested tool support needs them. Keep global user configuration outside a repository-instruction task.
For an unfamiliar or multi-tool repository, the bundled detector can locate instruction paths and declared framework/tool signals:
"<skill-directory>/scripts/detect-agent-context" --root "<repository-root>" --format jsonOn Windows use scripts/detect-agent-context.cmd with the same arguments. Python provides JSON; native Bash/PowerShell fallbacks emit a smaller text report. Resolve scripts relative to this skill, not the target project. Direct file inspection is sufficient for a known, narrow edit.
The detector indexes selected public manifests and instruction/config paths without reading credentials, environment files, or instruction contents. Treat it as an index: read the applicable instructions and verify commands in their source before persisting them. Include global paths only when that investigation is authorized and relevant.
Read discovery.md for detector details or tool-compatibility.md when loading order and supported tool behavior affect the output.
Select durable rules
Keep a rule when it is non-obvious, supported by project evidence, useful across tasks, and concrete enough to follow. Good candidates include exact command runners, generated-file ownership, unusual business boundaries, required checks, and repository-specific deployment or approval constraints.
Remove or rewrite generic advice, personas, duplicated rules, obsolete commands, exhaustive inventories, mandatory questionnaires, unsupported scores, and procedures that conflict with current project intent. Describe actual authorization boundaries; do not invent new approval gates or weaken explicit ones.
Keep detailed design, API, testing, and deployment guidance in their existing owners, linked with a clear read condition. Exclude secrets, home-directory paths, prompt transcripts, task logs, and global tool inventories.
Write or reconcile
Default to one compact shared instruction source. Use nested files for meaningful scope differences supported by the target tools, without repeating parent rules. For Codex, check same-directory AGENTS.override.md precedence before proposing a layout. For requested Claude compatibility, an import or existing symlink can avoid duplicate rules.
Use output-template.md as a menu. Classify existing content as keep, update, move, remove, or unresolved; resolve facts from source, and ask only about conflicts that require the user's decision. Read merge-and-verify.md for an existing file consolidation.
Prefer roughly 80–150 lines for a root file and shorter scoped files, without padding to a target. Review a root above 200 lines or 16 KiB for duplication and misplaced detail; preserve justified requirements while respecting the target tool's actual loading limit. Do not raise a global context limit just to avoid editing.
Use tracked diffs for recovery. Preserve untracked content that would otherwise be lost. Do not create routine backup copies, alter history, or ignore entire tool-configuration directories merely as part of generating instructions.
Verify
Check cited paths and commands, scope/precedence, symlinks, duplicate rules, and unresolved placeholders. Measure line/byte size and ensure the relevant instruction chain fits the target tool. Run repository validators when applicable. Static inspection of a command does not mean it was executed; do not run a destructive command to verify its spelling.
Report material rules kept, changed, moved, or removed, the evidence used, and unresolved conflicts. Avoid a separate discovery report unless the user requested it.
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.

