agents-md

Generate and maintain hierarchical AGENTS.md documentation for multi-package repositories.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ShadowAUS/chez-king-portal --skill agents-md-shadowaus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agents-md
Source: https://github.com/ShadowAUS/chez-king-portal/tree/main/.tessl/tiles/pantheon-ai/agents-md
Command: npx skills add https://github.com/ShadowAUS/chez-king-portal --skill agents-md-shadowaus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Create and maintain AGENTS.md documentation for simple projects and complex monorepos with deterministic discovery, scoped instruction files, and low-token navigation patterns; use when generating AGENTS.md, updating agent docs, or standardizing AI-facing project guidance.

Core Features & Use Cases

  • Deterministic discovery and hierarchical AGENTS.md guidance to route knowledge efficiently.
  • Scoped instruction files and index references to minimize duplication and token load.
  • Actionable AGENTS.md generation workflows for root and package-specific docs.

Quick Start

Run the discovery workflow to generate an AGENTS.md for your project and then validate and refine with the referenced templates.

Frequently Asked Questions about agents-md

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

FAQPage Schema
What is an AGENTS.md file and when do I need one for my project?

An AGENTS.md file provides deterministic, AI-facing project guidance for your repository. You need hierarchical AGENTS.md files when standardizing agent docs across simple projects or complex monorepos to ensure scoped instructions and low-token navigation.

How do I generate AGENTS.md documentation for a monorepo?

To generate AGENTS.md documentation for a monorepo, run the deterministic discovery workflow to identify package boundaries, then apply hierarchical layouts with root and package-specific files using the provided templates to tailor guidance to each package.

What's the best way to structure AGENTS.md files across multiple packages?

The best way to structure AGENTS.md files across multiple packages is using a hierarchical layout with a root AGENTS.md plus scoped instruction files for each package, minimizing duplication through index references and local skill references.

Can I maintain AGENTS.md docs without duplicating instructions across packages?

Yes, you can maintain AGENTS.md docs without duplication by using scoped instruction files, index references, and local skill references that enforce minimal duplication and copy-safe command templates to ensure consistent, low-token guidance.

Does AGENTS.md generation work for simple projects or is it only for monorepos?

AGENTS.md generation works for both simple projects and complex monorepos. The deterministic discovery workflow applies hierarchical layouts and scoped instruction patterns to route knowledge efficiently regardless of repository scale.