Agent skill · writing content · callicrate
agents-md
Use when the requested deliverable includes creating, reviewing, moving, splitting, or updating a repository AGENTS.md; produces scoped repo guidance. Do not trigger for standalone skills, prompts, non-AGENTS instruction files, READMEs, changelogs, or architecture docs.
Why this skill is useful
Adds specific workflows and scripts for creating and validating AGENTS.md files that the AI wouldn't reliably generate on its own.
What it needs
Requires python installed locally. About 3k tokens when loaded. Last updated 2026-06-24.
What this skill does
Manage AGENTS.md AGENTS.md gives coding agents scoped, current, repo-specific instructions. It is not a README, runbook, architecture doc, changelog, tutorial, or evidence log. Good guidance is evidence-backed, concise, scoped to the file's directory tree, and behavioral: it tells agents what to do differently in this repository. When to Use Create, update, review, split, move, or repair a repository AGENTS.md. Capture verified local commands, repo contracts, path ownership, or recurring agent mistakes. Convert repo evidence into rules that future agents can follow. When NOT to Use Standalone skills, prompts, global instructions, READMEs, architecture docs, changelogs, or runbooks. Broad documentation rewrites where AGENTS.md is not an explicit deliverable. Aspirational process guidance that is not supported by current repo evidence. Modes patch: small text fix, typo, stale path, or narrow rule change. Inspect the affected section and evidence only. create: no suitable AGENTS.md exists. Run the analyzer, sample source/config/docs, then draft the smallest useful file. update: existing file needs new or corrected guidance. Preserve valid rules, remove stale or duplicated material, and add only evidenced changes. split/move: scope boundaries are changing. Inspect existing root and nested files, then use references/topology-and-handoff-guidance.md. review: do not edit unless asked. Return findings by severity with evidence and residual risk. exhaustive: monorepos, contract-heavy repos, safety-sensitive guidance, operational handoffs, major topology changes, or unclear evidence. Workflow 1. Pick the mode and target scope. Read the nearest existing AGENTS.md, nested AGENTS.md files that may overlap, and git status --short when available. 2. For create, update, split/move, or exhaustive modes, run python <skill-root>/scripts/analyzeproject.py --repo-root <target-repo> --format json. Treat it as a sampling guide, not authority. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills callicrate/agents-md