Use this agent when the user needs to create, design, or refine system architecture diagrams, network topology diagrams, flowcharts, sequence diagrams, or any visual representation of technical systems. This includes generating Excalidraw-compatible files, reviewing existing diagrams for clarity and effectiveness…
Use this agent when you need a thorough code review — line-by-line analysis of code quality, naming, safety, and TypeScript correctness. Reviews as a Staff Engineer at a FAANG company would. Critics report; they don't fix. Context: You've finished implementing a new provider module. user: "Review this code before I…
Use this agent when you need design guidance for TypeScript, Python, or Rust — interface design, type system patterns, project structure, error handling, or naming conventions. Auto-detects the project language and applies the matching battle-tested style guide. Context: You're designing a TTS abstraction layer. user…
Use this agent when you need documentation that makes people actually want to use a project. Triggers include "improve the README", "rewrite descriptions", "make this appealing", or "better branding". Context: A new plugin was just shipped with a minimal placeholder README. user: Make this README appealing to…
Use this agent when you need to maintain or update repository infrastructure. Triggers include "update CLAUDE.md", "fix CI workflows", "update contributor docs", or "sync the registry". Context: Three new agents were added to the plugin and CLAUDE.md still lists only the original five. user: Update CLAUDE.md to…
Use this agent when you need to research an API or service and produce a structured reference document — endpoints, auth, schemas, pricing, rate limits, and code examples. Context: You're adding ElevenLabs TTS support to the plugin. user: "Research the ElevenLabs API for text-to-speech." assistant: "I'll use the scout…
Use this agent when you need comprehensive validation before shipping or merging. Triggers include "validate everything", "run all tests", "verify the changes", or "check if this is ready". Context: Three agents have finished their work on a new plugin release. user: Validate everything before we tag the release.…
Use this agent when you need to fix, validate, or modify Claude Code plugin structure — manifests, hooks, command frontmatter, paths, or version bumps. Context: You added a new hook and the plugin is rejected on load. user: "Fix the plugin structure — the hooks aren't being recognized." assistant: "I'll use the smith…
Use this agent when you need a security review — injection surfaces, secret and credential leakage, dependency and supply-chain risk, and plugin permission surfaces (hooks, tool allowlists, MCP configs). Wardens report; they don't fix. Context: A new feature added an endpoint that shells out based on user input. user…
Use this agent when you need to integrate new abstractions into existing code without breaking anything. Triggers include phrases like "refactor to use the new", "integrate with", "wire up", or "connect these modules". Context: guido has created a new ProviderProtocol and smith has updated the manifest. user: Wire up…
Use this agent when you need a plugin-aware review of one or more agent definitions — the .md files under a plugin's agents/ directory. Adapts the plugin-dev agent-development skill methodology and reports findings in the fakoli-plugin-critic severity rubric (MUST FIX / SHOULD FIX / CONSIDER / NIT). Agent-critics…
Use this agent when you need a thorough review of a plugin's hook layer — hooks/hooks.json plus every shell script it dispatches to. Reviews as a Staff Engineer would review event-driven infrastructure: portability of shebang and paths, correctness of stdin handling, performance on hot events, idempotency, matcher…
Use this agent when you need a thorough review of .mcp.json configuration files and the MCP server implementation source they reference. Reviews schema validity, portable path resolution via ${CLAUDEPLUGINROOT}, @mcp.tool() decoration discipline, typed parameter annotations, structured error returns, secret-leak…
Use this agent when you need a rigorous review of a plugin skill — line-by-line analysis of a skills/ /SKILL.md file against the canonical skill-development methodology. Checks frontmatter validity, one-question-at-a-time discipline, hard-gate presence on irreversible actions, decision-flow clarity, lazy-loading…
Use this agent when you need a cross-plugin structural review — plugin.json manifest, marketplace.json entry, registry index entry, README surface tables, CHANGELOG Keep-a-Changelog discipline, and version-string sync across every source of truth (plugin.json, pyproject.toml, init.py, marketplace, registry). Adapts…