Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
alirezarezvani avatar

Agent Designer

  • 614 installs
  • 23.5k repo stars
  • Updated July 17, 2026
  • alirezarezvani/claude-skills

agent-designer is an AI skill that analyzes multi-agent execution logs and returns success rates, cost breakdowns, latency distributions, and concrete optimization recommendations for developers operating agent systems.

About

agent-designer is a Python-based Agent Evaluator skill that ingests JSON execution logs containing tasks, actions, results, elapsed time, and token usage. It computes task success rate, average cost per task, latency distributions, error patterns, and tool usage efficiency, then surfaces bottlenecks and improvement opportunities. Developers reach for agent-designer when multi-agent pipelines are running but performance is opaque—high spend, slow steps, or recurring failures need quantified diagnosis. Output is a structured performance report with bottleneck analysis and optimization recommendations suitable for the next engineering iteration.

  • Analyzes JSON execution logs from agent runs
  • Calculates success rate, average cost per task, latency percentiles, and tool efficiency
  • Identifies recurring error patterns and performance bottlenecks
  • Generates prioritized optimization recommendations
  • Outputs structured performance report with bottleneck analysis

Agent Designer by the numbers

  • 614 all-time installs (skills.sh)
  • Ranked #1,549 of 16,565 AI & Agent Building skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/alirezarezvani/claude-skills --skill agent-designer

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs614
repo stars23.5k
Security audit3 / 3 scanners passed
Last updatedJuly 17, 2026
Repositoryalirezarezvani/claude-skills

How do you analyze multi-agent execution log performance?

Automatically analyze multi-agent execution logs and receive success rates, cost breakdowns, latency distributions, and concrete optimization recommendations.

Who is it for?

Engineers operating multi-agent systems who already capture execution logs and need quantitative bottleneck analysis before changing orchestration.

Skip if: Teams still designing prompts from scratch or lacking structured JSON logs with tasks, actions, timing, and token counts.

When should I use this skill?

Multi-agent execution logs exist and the task is measuring success rate, cost, latency, or identifying inefficient tool usage.

What you get

Performance report with success rate, cost breakdown, latency distribution, error patterns, and prioritized optimization recommendations.

  • performance report
  • bottleneck analysis
  • optimization recommendations

Files

SKILL.mdMarkdownGitHub ↗

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

ChooseWhenWatch out for
Single agentOne bounded task, < ~5 toolsDon't add agents you don't need
SupervisorCentral decomposition, specialists report backSupervisor becomes the bottleneck
PipelineStrictly sequential stages with handoffsRigid order; slowest stage gates throughput
HierarchicalMultiple org layers, > ~8 agentsCommunication overhead per level
SwarmParallel peers, fault tolerance over predictabilityHard to debug; needs consensus rules

The planner applies this scoring deterministically — run it rather than picking by feel.

Workflow

All paths relative to this skill folder. Each step's JSON output is the next step's design input.

1. Design the architecture

Write a requirements JSON (copy assets/sample_system_requirements.json — keys: goal, tasks[], constraints{max_response_time, budget_per_task, concurrent_tasks}, team_size):

python3 agent_planner.py requirements.json --format json -o arch

Emits arch.json with architecture_design (pattern, agents, communication links), mermaid_diagram, and implementation_roadmap. Read architecture_design.pattern and the per-agent role list; present the mermaid diagram to the user.

2. Generate tool schemas

Describe each agent's tools in plain JSON (copy assets/sample_tool_descriptions.json), then:

python3 tool_schema_generator.py tool_descriptions.json --validate -o tools

Emits tools.json (tool_schemas, validation_summary) plus provider-specific tools_anthropic.json / tools_openai.json. Gate: every tool must print `✓ Valid`. Fix any invalid schema before proceeding — never hand an agent an unvalidated schema.

3. Evaluate execution logs

Once the system runs (or against assets/sample_execution_logs.json for a dry run):

python3 agent_evaluator.py execution_logs.json --detailed -o eval

Emits eval.json with summary, agent_metrics, bottleneck_analysis, error_analysis, cost_breakdown, sla_compliance, and optimization_recommendations, plus split files (eval_errors.json, eval_recommendations.json).

4. Verification loop

The design is not done until:

1. tool_schema_generator.py --validate reports 0 invalid schemas. 2. agent_evaluator.py on a pilot run reports 0 critical issues (the tool prints CRITICAL: N critical issues when found). If N > 0, apply the top item in eval_recommendations.json, re-run the pilot, and re-evaluate. 3. Compare your outputs against expected_outputs/ to confirm the schema shape you're consuming hasn't drifted.

References

  • references/agent_architecture_patterns.md — pattern trade-offs in depth
  • references/tool_design_best_practices.md — schema, idempotency, error-handling rules
  • references/evaluation_methodology.md — metric definitions the evaluator implements

Related skills

How it compares

Use agent-designer to quantify runtime agent performance from logs; use prompt-engineering when outputs are wrong but telemetry is not yet collected.

FAQ

What input does agent-designer require?

agent-designer expects JSON execution logs listing tasks, actions taken, results, elapsed time, and tokens used. The Python evaluator aggregates those fields into success, cost, and latency metrics.

What does agent-designer output?

agent-designer returns a performance report with task success rate, average cost per task, latency distribution, error patterns, tool efficiency notes, and prioritized optimization recommendations.

Is Agent Designer safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

AI & Agent Buildingagentsautomation

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.