agent-designer
Use when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer).
Profile →npx skills add alirezarezvani/claude-skills --skill agent-designer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Agent Designer — Multi-Agent System Architecture Design, schema-generate, and evaluate multi-agent systems with three deterministic tools. The scripts are the workflow — do not freehand an architecture when the planner can score one from requirements. ## When to use - Designing a new multi-agent system from requirements (pattern choice, roles, comms) - Generating provider-ready tool schemas (Anthropic + OpenAI formats) from plain tool descriptions - Evaluating execution logs: success rate, latency distribution, cost, bottlenecks **When NOT to use:** Claude Code Workflow-tool automations → `workflow-builder`; single-agent workflow scaffolds → `agent-workflow-designer`; multi-agent fan-out at runtime → `agenthub`. ## Pattern decision table | Choose | When | Watch out for | |---|---|---| | Single agent | One bounded task, < ~5 tools | Don't add agents you don't need | | Supervisor | Central decomposition, specialists report back | Supervisor becomes the bottleneck | | Pipeline | Strictly sequential stages with handoffs | Rigid order; slowest stage gates throughput | | Hierarchical | Multiple org layers, > ~8 agents | Communication overhead per level | | Swarm | Parallel peers, fault
- When to use
- Pattern decision table
- Workflow
- 1. Design the architecture
- 2. Generate tool schemas
- 3. Evaluate execution logs
- 4. Verification loop
- References
python3 agent_planner.py requirements.json --format json -o arch python3 tool_schema_generator.py tool_descriptions.json --validate -o tools python3 agent_evaluator.py execution_logs.json --detailed -o eval
What does the agent-designer skill do?
Use when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer).
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill agent-designer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.