agent-designer

Designs multi-agent architectures, generates tool schemas, and evaluates agent execution logs.

2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/BryanPinheiro77/FinanceBot-BackEnd --skill agent-designer-bryanpinheiro77
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-designer
Source: https://github.com/BryanPinheiro77/FinanceBot-BackEnd/tree/main/.agents/skills/agent-designer
Command: npx skills add https://github.com/BryanPinheiro77/FinanceBot-BackEnd --skill agent-designer-bryanpinheiro77

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Designing multi-agent systems by intuition leads to wrong orchestration patterns, invalid tool schemas, and undetected performance bottlenecks. This Skill replaces guesswork with three deterministic Python tools that score architecture patterns from requirements, generate provider-ready tool schemas, and analyze execution logs for cost, latency, and failure issues. ## Core Features & Use Cases - Architecture Planning: agent_planner.py scores and selects among single-agent, supervisor, swarm, hierarchical, and pipeline patterns from a requirements JSON, emitting agent role definitions, communication topology, a Mermaid diagram, and an implementation roadmap. - Tool Schema Generation: tool_schema_generator.py converts plain tool descriptions into validated OpenAI function-calling and Anthropic tool-use schemas with validation rules, error responses, rate limits, and usage examples. - Execution Log Evaluation: agent_evaluator.py computes success rates, latency percentiles, token costs, error patterns, and bottleneck analysis, then outputs prioritized optimization recommendations. - Use Case: Given requirements for a research automation platform, run the planner to get a supervisor architecture with a Mermaid diagram, generate validated Anthropic schemas for each agent's tools, then evaluate pilot run logs until zero critical issues remain. ## Quick Start Ask the agent to design a multi-agent architecture from your system requirements JSON and generate the corresponding validated tool schemas.

Frequently Asked Questions about agent-designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between supervisor, swarm, and pipeline agent architectures?▼

Use supervisor for hierarchical task decomposition with 2-8 agents, swarm for parallel peer collaboration with fault tolerance across 3-20 agents, and pipeline for strictly sequential processing stages. The agent_planner.py script scores these patterns deterministically from your requirements JSON rather than relying on intuition.

How do I generate Anthropic and OpenAI tool schemas from tool descriptions?▼

Write a JSON file describing each tool's name, purpose, inputs, outputs, and error conditions, then run tool_schema_generator.py with the --validate flag. It emits both provider formats plus validation rules, rate limits, and usage examples, and every schema must pass validation before use.

How do I analyze agent execution logs for bottlenecks and cost?▼

Pass execution logs containing task_id, agent_id, duration_ms, status, tokens_used, and cost_usd to agent_evaluator.py with the --detailed flag. It reports success rates, latency percentiles, error patterns, bottleneck severity, and prioritized optimization recommendations.

What input format does the multi-agent architecture planner require?▼

The planner expects a JSON file with goal, description, tasks list, constraints (max_response_time, budget_per_task), team_size, performance_requirements, and safety_requirements. A sample file is provided in the assets directory to copy as a starting point.

When should I not use a multi-agent architecture?▼

Avoid multi-agent designs for single bounded tasks with few tools, where one agent suffices. The planner's scoring explicitly favors single-agent patterns for low-complexity requirements, since unnecessary agents add coordination overhead and debugging difficulty.