agent-md-creator

Generate root and scoped AGENTS.md files from repository structure.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/aleister1102/skills --skill agent-md-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-md-creator
Source: https://github.com/aleister1102/skills/tree/main/agent-md-creator
Command: npx skills add https://github.com/aleister1102/skills --skill agent-md-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, bash.

What problem does it solve?

This skill automates the generation and maintenance of AGENTS.md files following the public agents.md convention, reducing manual toil and keeping documentation in sync with code.

Core Features & Use Cases

  • Generate root AGENTS.md with precedence rules and scoped indices.
  • Create scoped AGENTS.md files for backend, frontend, and other dirs based on project structure.
  • Update and verify AGENTS.md to reflect repository changes, ensuring consistency across teams.

Quick Start

Run the tool on your project directory to generate the root and all scoped AGENTS.md files.

Frequently Asked Questions about agent-md-creator

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

FAQPage Schema
How do I automate AGENTS.md creation for a multi-language repository?

Automating AGENTS.md creation involves parsing the repository structure to extract patterns and commands, then rendering agent-optimized templates for root and scoped directories.

What is the agents.md convention and when do I need scoped files?

The agents.md convention standardizes AI agent documentation in code repositories. Scoped files are needed when organizing specific instructions for backend, frontend, or other distinct directory structures.

How to keep AGENTS.md files synced with repository changes across teams?

Keeping AGENTS.md files synced involves running update and verification scripts against repository changes, ensuring consistency across root and scoped directories without manual toil.

Do I need bash and jq to generate root AGENTS.md templates?

Yes, bash and jq are required dependencies to parse repository structures and render agent-optimized templates when generating root and scoped AGENTS.md files.

What's the best way to structure AGENTS.md precedence rules for multi-language projects?

The best way to structure precedence rules is by generating a root AGENTS.md with defined hierarchy and scoped indices, applying templates based on the parsed project structure.

Are there limitations when using bash scripts for repo-management documentation generation?

Limitations of using bash scripts include dependency on jq for parsing and potential constraints with complex multi-language repository structures during automated template generation.