meta-auditlisted

# meta-audit ## When to Use This Skill | Use this skill when... | Use custom-agent-definitions instead when... | |---|---| | Reviewing existing `.claude/agents/*.md` files for missing frontmatter, overprivileged tools, or wrong models | Authoring a new agent definition file from scratch | | Validating read-only vs write-enabled agent privilege boundaries before committing | Configuring a single agent's `model`, `allowed-tools`, or `context: fork` | | Auditing agents across an entire project for naming and security consistency | Copying or generalising another project's agents (use meta-assimilate) | ## Context - Agent definitions: !`find .claude/agents -name "*.md" -not -name "settings*"` - Settings file: !`find .claude/agents -maxdepth 1 -name "settings.local.json" -type f` ## Your task ### 1. Discovery Phase - Use **Glob** to find all agent definition files in `.claude/agents/` - Read each agent file to extract frontmatter and configuration - Identify the settings.local.json for permission overrides ### 2. Frontmatter Validation For each agent, verify required fields are present: - ✅ **name**: Agent identifier (must match filename) - ✅ **model**: Claude model to use (e.g., "claude-opus-4-7") - ✅ **color**: Hex color code for UI (e.g., "#E53E3E") - ✅ **description**: Clear usage guidance with "Use proactively when..." - ✅ **tools**: Tool list or "All" for full access **Flag issues:** - Missing required fields - Mismatched name vs filename - Invalid model names -