Description 960 -> 244 chars, body 470 -> 452 words, Gotchas 36% -> 22%. Both composition notes move to README.md, which already carried them. Four of five Gotchas were paraphrases of the step below them and were deleted with their force folded back into that step. A clean-context audit overturned the fifth deletion: the provider-file prohibition was strictly broader than Step 4, so it was never a paraphrase, and Step 4's 'don't rewrite it yourself' is attached to the if-duplicates branch. With Write and Edit granted, a provider file that was merely stale had nothing forbidding an edit. Restored as an unconditional Gotcha, read before any step writes. Also restores a concrete indirect trigger. The retrofit had replaced two with the meta-statement 'even when they don't name the file', which claims an indirect trigger exists rather than being one -- and users asking to document a repo for AI tools have no reason to know the filename. Refs #99
agentsmd-author
Create or update a target repo's AGENTS.md file(s) by exploring the repo for real conventions.
What it does
Explores a target repo (package manager scripts, Makefile/task runner, CI config, linter config, existing docs) and writes or updates AGENTS.md with only verified commands and conventions — never invented ones. Supports nested monorepo placement, following the agents.md standard's nearest-file-wins precedence. Closes every run by invoking agentsmd-audit inline, and hands off to provider-adapter-author when an existing provider-specific file (CLAUDE.md, etc.) now duplicates content AGENTS.md owns.
Before you start
The agentsmd-audit skill must be available (co-installed in the core plugin) — this skill invokes it as a mandatory closeout step.
Usage
/agentsmd-author
Provide the target repo root (defaults to the current directory) and, if relevant, which subdirectory should get a nested AGENTS.md.
Files
| File | Purpose |
|---|---|
SKILL.md |
Skill instructions for agents |
references/content-guide.md |
Section-by-section AGENTS.md content guidance, a worked example, and monorepo/nested-file precedence rules |
references/sources.md |
Provenance record — sources that informed this skill and which files each contributed to |