natnew

Regenerate the Field Map (Mermaid diagram) and Reading Paths sections of README.md so they stay consistent with the current section taxonomy and entries. Use whenever sections are added, renamed, merged, or removed, or when reading-path entries change.

Validate one or more proposed awesome-list entries against every rule in CONTRIBUTING.md and output a pass/fail checklist with a corrected entry where fixable. Use before adding entries to README.md or when reviewing a contribution PR.

Sweep arXiv, OpenReview, and official lab blogs for new resources on recursive self-improvement in AI, dedupe against README.md, and produce candidate entries in the exact CONTRIBUTING.md format with section placement rationale.

Audit the awesome list for link rot, superseded preprints, abandoned projects, and entries that no longer meet the quality bar, and output an audit report with recommended actions. Use periodically or before a release of the list.

Create a README.md file for the project

End-to-end procedure for adding one resource to the list — duplicate search, source verification, canonical formatting, section placement, and validation. Use whenever a new entry is being added to README.md.

Run and interpret the awesome-list compliance linter for README.md. Use before opening or reviewing any pull request that touches the README.

Measure how comprehensive and current the list is — entries per section and per year, with thin and stale sections flagged. Use before planning content expansion or periodically as a health check.

Validate that every link in the curated list resolves and points at the intended resource. Use before opening or reviewing a pull request that adds or edits entries.

Add a new resource to the Awesome Multi-Agent AI Safety list with full verification. Use when asked to add a paper, tool, benchmark, testbed, or organisation to the list.

Triage the monthly resource-radar issue - sweep the listed sources for new multi-agent AI safety resources, evaluate candidates, and add accepted ones to the list. Use when asked to run a curation sweep, process the radar issue, or find new resources for the list.

Maintains CHANGELOG.md in the project root using git commit history. Use when the user invokes /changelog, asks to "update the changelog", "generate a changelog", or wants to record what changed before merging a branch. Creates the file from scratch if it doesn't exist (all commits grouped by date); otherwise appends only commits newer than the last recorded date.

Maintains CHANGELOG.md in the project root using git commit history. Use when the user invokes /changelog, asks to "update the changelog", "generate a changelog", or wants to record what changed before merging a branch. Creates the file from scratch if it doesn't exist (all commits grouped by date); otherwise appends only commits newer than the last recorded date.