Defame1297
1c3af75642
Both branches of the flag reduced to the same expression, so the option was inert: a caller who asked for the no-import form got the import-form check anyway and a passing result that meant nothing. Two further defects in the same validator: --max-lines failed silently when given a value it could not use, and the Fix text told the agent to edit AGENTS.md when the offending content is the provider adapter's. The boundary clauses now name the operation being routed rather than the file type, which was ambiguous where both skills touch the same file. Addresses #115.
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 |