klh-agents-md

Creates and maintains concise AGENTS.md files that reference local agent skills.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/klh/skills --skill klh-agents-md-klh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: klh-agents-md
Source: https://github.com/klh/skills/tree/main/.well-known/agent-skills/klh-agents-md
Command: npx skills add https://github.com/klh/skills --skill klh-agents-md-klh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agent-facing documentation like AGENTS.md and CLAUDE.md often becomes bloated with prose, duplicated instructions, and filler, making it hard for coding agents to find the rules that matter. This Skill enforces a minimal, structured writing style so agent instructions stay concise and reference local skills instead of duplicating them. ## Core Features & Use Cases - Structured AGENTS.md authoring: Defines required sections (package manager, commit attribution, key conventions, local skills) and optional sections with strict formatting rules. - Local skill discovery: Runs find and ls commands to locate SKILL.md files so AGENTS.md can reference them by path instead of duplicating content. - CLAUDE.md symlink setup: Creates AGENTS.md as the canonical file and symlinks CLAUDE.md to it for cross-agent compatibility. - Use Case: When setting up a new repository, ask the agent to create an AGENTS.md that documents the pnpm workflow, commit attribution rules, and links to existing testing and database skills. ## Quick Start Create a concise AGENTS.md for this project that references the skills in .claude/skills and symlinks CLAUDE.md to it.

Frequently Asked Questions about klh-agents-md

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

FAQPage Schema
How do I create an AGENTS.md file for my project?

Create AGENTS.md at the project root with required sections for package manager, commit attribution, key conventions, and local skills. Use headers, bullets, and code blocks only, and reference skills by path instead of duplicating their content.

How do I keep CLAUDE.md and AGENTS.md in sync?

Treat AGENTS.md as the canonical file and create a symlink with ln -s AGENTS.md CLAUDE.md. This keeps a single source of truth while remaining compatible with agents that read CLAUDE.md.

What sections should an AGENTS.md file include?

Required sections are package manager commands, commit attribution with a Co-Authored-By trailer, key project conventions, and references to local skills. Optional sections cover API route templates, CLI command tables, and file naming conventions.

How do I reference local agent skills in AGENTS.md?

Discover skills with find .claude/skills -name SKILL.md or ls plugins/*/skills/*/SKILL.md, then read each frontmatter. Reference them by name and path, for example: use the db-migrate skill, see .claude/skills/db-migrate/SKILL.md.

What content should be left out of agent instruction files?

Omit welcome text, explanations of why, obvious instructions like run tests, and content already covered by skills. Agents are capable, so documentation should state what to do in bullets rather than long prose paragraphs.