review-agents-md

Generate and maintain a minimal root AGENTS.md with progressive disclosure.

69|11|Updated Dec 30, 2025

Search Tags:#documentation #progressive-disclosure #documentation-standards #agents-md #root-docs #agile-docs

Ready to run

npx skills add https://github.com/richtabor/agent-skills --skill review-agents-md

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-agents-md
Source: https://github.com/richtabor/agent-skills/tree/main/skills/review-agents-md
Command: npx skills add https://github.com/richtabor/agent-skills --skill review-agents-md

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates and refactors AGENTS.md files following progressive disclosure principles. Keeps files minimal and focused—avoiding the "ball of mud" that hurts agent performance.

Core Features & Use Cases

Generates a lean root AGENTS.md that anchors decision-making for any project.
Encourages progressive disclosure by routing domain-specific rules and guidance to separate docs rather than bloating the root file.
Supports monorepos with per-package AGENTS.md files that reference root conventions.

Quick Start

Create a minimal AGENTS.md at the project root and reference additional docs for progressive disclosure.

Frequently Asked Questions about review-agents-md

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is progressive disclosure for AGENTS.md documentation?▼

Progressive disclosure keeps the root AGENTS.md minimal by anchoring only essential project context, routing domain-specific rules and workflow guidance to separate linked docs to avoid bloated files.

How do I generate a minimal AGENTS.md for my project root?▼

Generate a lean AGENTS.md by including only critical project context like the description, package manager, and non-standard commands, then link to focused docs for deeper policies.

Can I use multiple AGENTS.md files in a monorepo?▼

Yes, monorepos support per-package AGENTS.md files. These individual files can reference and inherit root conventions, keeping domain-specific rules organized without duplicating project-wide context.

What should I include in an AGENTS.md file to anchor agent decisions?▼

Include only essential project context such as the project description, package manager details, and non-standard commands. Reference structured documentation for deeper policies rather than cluttering the root file.

Why does my AGENTS.md file hurt agent performance?▼

A bloated AGENTS.md file creates a 'ball of mud' that hurts agent performance. Applying progressive disclosure separates rules and guidance into focused docs, keeping the root file lean and effective.

When should I separate documentation from the root AGENTS.md?▼

Separate documentation when domain-specific rules, detailed workflows, or specialized guidance threaten to bloat the root file. Keep the root concise and link to structured docs for deeper policies.