Agent skill · writing content · sickn33
agents-md
Create, revise, or audit AGENTS.md files from repository evidence, verified commands, and correctly scoped instructions without overwriting maintainer intent.
Why this skill is useful
Provides specific guidelines for creating concise agent documentation that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Maintain AGENTS.md from repository evidence Overview Create or improve agent instructions that help a coding agent change the repository correctly without rediscovering its workflow. Base every repository-specific command, path, and rule on evidence in the current checkout. Prefer a focused diff over a wholesale rewrite. There is no universal line limit, required section list, symlink layout, or commit-attribution policy; follow the repository's own needs and maintainer intent. When to Use The user asks to create, update, shorten, or audit AGENTS.md. A monorepo needs root instructions plus narrower package-level overrides. Existing agent instructions contain stale commands, duplicated policy, or unsupported claims. The user wants to reconcile AGENTS.md with CLAUDE.md, .github/copilot-instructions.md, or other repository instruction files. Use @agents-generator instead when the task specifically calls for its packaged generation modes, assets, or backup workflow. Use this skill when a maintainer-readable, evidence-first edit is the primary goal. How It Works 1. Preserve existing intent Before writing, read every instruction file that applies to the target path, including existing AGENTS.md files and relevant tool-specific files such as CLAUDE.md, GEMINI.md, .github/copilot-instructions.md, and .github/instructions/.instructions.md. Improve an existing AGENTS.md in place when possible. Preserve accurate maintainer-authored rules and repository-specific policy. Do not replace another tool's instruction file with a symlink unless the user requests it and repository evidence shows identical content is desired. Do not silently choose between conflicting instructions. Follow the higher-priority applicable rule, or ask when the intended policy cannot be established from the repository. 2. Build a bounded evidence map Inspect only enough of the repository to establish how work is actually done: 1. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/agents-md