Agent Designer
Design multi-agent system architectures, choose an orchestration pattern, generate tool schemas, and analyze agent logs for cost, latency, and failure bottlenecks.
Before & after
Same prompt, same agent — the only difference is the skill.
Building a multi-agent system requires thinking about how different agents will coordinate work. You might have some agents gathering data while others process it. Communication patterns are important - you could use a central controller to orchestrate tasks or have agents pass messages directly. There are different orchestration approaches like supervisor patterns or pipeline architectures. You'd also need to think about error handling and what happens if one agent fails. Tool definitions are important so agents know what capabilities they have available. Performance and cost can be concerns depending on how many agents you need.
RESEARCH AGENT SYSTEM ARCHITECTURE:
ORCHESTRATION PATTERN: SUPERVISOR + SPECIALIZED AGENTS
Supervisor Agent (Claude 3.5 Sonnet)
- Receives research goal from user
- Decomposes into sub-tasks
- Delegates to specialist agents
- Aggregates results into final report
Data Gathering Agent (Claude 3.5 Haiku, optimized for speed)
- Tools: web_search, fetch_url, read_pdf, query_database
- Responsibility: Find primary sources, extract structured facts
- Output: Annotated findings with source citations
Synthesis Agent (Claude 3.5 Sonnet)
- Receives gathered facts
- Identifies patterns, contradictions, consensus
- Ranks claim credibility
- Output: Narrative synthesis + uncertainty labels
Report Agent (Claude 3.5 Haiku, cost-optimized for formatting)
- Templates: executive summary, detailed findings, appendix
- Tool: generate_markdown, render_charts
- Output: Ready-to-share research report
TOOL SCHEMA DEFINITIONS
web_search: { query, max_results, date_range }
fetch_url: { url, extract_section }
query_database: { table, filters, limit }
COST/LATENCY BREAKDOWN
• Total per research task: ~15-25 tokens (Sonnet) + 8K tokens (Haiku)
• Latency: parallel agent execution = ~45 seconds
• Bottleneck: data gathering (network I/O), not inference
FAILURE HANDLING
- If data agent timeout: skip source, note in final report
- If synthesis fails: supervisor retries with subset
- If report gen fails: return raw markdown output
About this skill
name: agent-designer description: Use when 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, latenc...
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).
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the agent-designer skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Agent Designer; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: agent-designer
description: Design multi-agent system architectures, choose an orchestration pattern, generate tool schemas, and analyze agent logs for cost, latency, and failure bottlenecks.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Agent Designer
Design multi-agent system architectures, choose an orchestration pattern, generate tool schemas, and analyze agent logs for cost, latency, and failure bottlenecks.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.