agents-analyze

# /agents:analyze Analyze the plugin collection to identify where sub-agents would improve workflows by isolating verbose output, enforcing constraints, or specializing behavior. ## When to Use This Skill | Use this skill when... | Use a sibling skill instead when... | |---|---| | Auditing the whole plugin collection for sub-agent opportunities (verbose-output skills, model mismatches, tool over-permissions) | Auditing a single agent's frontmatter, tool list, and prompt completeness — use `agent-patterns-plugin:meta-audit` | | Mapping delegation gaps and producing a list of proposed new agents | Authoring the new agent file from that proposal — use `agent-patterns-plugin:custom-agent-definitions` | | Confirming every agent runs on Opus (the always-Opus standard) | Configuring an agent's hooks, permissions, or settings.json wiring — use `hooks-plugin:hooks-configuration` | | Focusing the analysis on a single plugin's skills (`--focus <plugin>`) | Coordinating multiple agents at runtime — use `agent-patterns-plugin:agent-teams` or `parallel-agent-dispatch` | ## Agentic Optimizations | Context | Command | |---------|---------| | List all plugins | `find . -maxdepth 1 -type d -name '*-plugin'` | | Count skills per plugin | `find <plugin>/skills -name 'SKILL.md' -o -name 'skill.md' \| wc -l` | | List existing agents | `find agents-plugin/agents -maxdepth 1 -name '*.md'` | | Check agent model field | `grep -r '^model:' agents-plugin/agents/` | | Check agent allowed-tools | `gr...