What problem does it solve? AGENTS.md files often become bloated with redundant documentation, task history, and rules that belong in code or configuration. This Skill provides a structured methodology for deciding what belongs in an AGENTS.md file, where each rule should live, and how to keep agent-facing instructions concise and behavior-changing. ## Core Features & Use Cases - Scope Classification: Distinguishes brownfield roots, nested subtrees, greenfield guidance, and personal/global policy files, each with different register and length expectations. - Rule Placement Logic: Routes each rule to its nearest durable home, preferring executable checks and configuration over prose, and reserving AGENTS.md for non-obvious intent, constraints, and hazards. - Length and Content Guardrails: Targets roughly 20 lines for brownfield roots and 1-10 lines for nested files, flagging anything over 40 lines as suspicious. - Use Case: When auditing a repository's AGENTS.md that has grown to 150 lines of directory tours and task history, use this Skill to strip it down to durable, behavior-changing rules and move enforceable checks into configuration. ## Quick Start Review the AGENTS.md file in this repository and revise it according to the agents-md guidance.