Agent Designer logo

Agent Designer

Community
borghei
agent-designer

Designs multi-agent system architectures with orchestration patterns, tool schemas, and performance evaluation. Use when building AI agent systems, designing agent workflows, creating tool schemas, or evaluating agent performance.

Overview

Publisherborghei
RepositoryClaude-Skills
Skill nameagent-designer
Stars
856
Forks
154
Bundled files
14
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 14 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by borghei on GitHub. Read the source before you install it.

Installation

Install the Agent Designer AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/borghei/Claude-Skills/tree/main/engineering/agent-designer
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/borghei/Claude-Skills.git /tmp/Claude-Skills
mkdir -p .claude/skills
cp -r /tmp/Claude-Skills/engineering/agent-designer .claude/skills/agent-designer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Agent Designer in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Agent Designer on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Agent Designer is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Agent Designer - Multi-Agent System Architecture

A toolkit for designing, architecting, and evaluating multi-agent systems. It provides structured approaches to agent architecture patterns, tool design principles, communication strategies, and performance evaluation frameworks for building robust, scalable AI agent systems.

Core Capabilities

  • Architecture pattern selection — single agent, supervisor, swarm, hierarchical, and pipeline patterns with use-case fit and trade-offs.
  • Agent role definition — identity, responsibilities, capabilities, interfaces, and constraints; common archetypes (coordinator, specialist, interface, monitor).
  • Tool design — schema design, error handling, idempotency requirements, and validation rules.
  • Communication & orchestration — message passing, shared state, event-driven architecture; centralized, decentralized, and hybrid orchestration.
  • Guardrails & safety — input validation, output filtering, and human-in-the-loop checkpoints.
  • Evaluation frameworks — task completion, quality, cost, and latency metrics with bottleneck analysis.
  • Memory, scaling & failure handling — short/long/shared memory, horizontal/vertical scaling, retries, fallbacks, and circuit breakers.

When to Use

  • Building AI agent systems or designing multi-agent workflows.
  • Creating tool schemas for OpenAI function calling or Anthropic tool use.
  • Selecting an architecture pattern for a new system.
  • Evaluating agent performance from execution logs.

Clarify First

Before designing the system, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • System goal & scale — the task the agents perform and expected load (drives which architecture pattern: single, supervisor, swarm, hierarchical, or pipeline)
  • Tool protocol target — OpenAI function calling vs Anthropic tool use (sets the schema format tool_schema_generator.py emits)
  • Optimization priority — cost, latency, or quality (determines agent roles, model tiers, and which metrics the evaluator weights)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Tools

ToolPurposeCommand
agent_planner.pyDesign architecture from requirements (pattern, roles, topology, Mermaid diagram, roadmap)python agent_planner.py requirements.json -o my_system --format both
agent_evaluator.pyEvaluate performance from execution logs (success, cost, latency, bottlenecks)python agent_evaluator.py execution_logs.json -o perf_report --format both --detailed
tool_schema_generator.pyGenerate OpenAI/Anthropic tool schemas with validationpython tool_schema_generator.py tools.json -o my_tools --format both --validate

References

Load the reference that matches the task — keep this file lean and pull detail on demand:

  • references/core-capabilities.md — the full Core Capabilities catalog (architecture patterns, role definition, tool design, communication, guardrails, evaluation, orchestration, memory, scaling, failure handling) plus Implementation Guidelines. Read when designing any part of a system.
  • references/agent_architecture_patterns.md — deep catalog of architecture patterns with structure diagrams, characteristics, use cases, and implementation considerations. Read when selecting or comparing patterns.
  • references/tool_design_best_practices.md — best practices for designing tools in multi-agent systems (single responsibility, idempotency, composability, schemas, error handling). Read when designing tools or schemas.
  • references/evaluation_methodology.md — full evaluation methodology across performance, reliability, cost, and satisfaction dimensions. Read when planning evaluation or interpreting reports.
  • references/troubleshooting-and-tool-reference.md — troubleshooting table, success criteria, and the complete CLI parameter reference for all three scripts. Read when a tool misbehaves or you need full command options.

Scope & Limitations

Covers:

  • Multi-agent architecture pattern selection (single agent, supervisor, swarm, hierarchical, pipeline)
  • Agent role definition with responsibilities, capabilities, tools, and communication interfaces
  • Tool schema generation in OpenAI and Anthropic formats with validation rules and error handling
  • Performance evaluation from execution logs including bottleneck analysis and optimization recommendations

Does NOT cover:

  • Runtime agent orchestration or execution engines (see engineering/agent-workflow-designer for workflow execution)
  • LLM prompt engineering or system prompt design (see engineering/prompt-engineer-toolkit)
  • MCP server implementation or protocol details (see engineering/mcp-server-builder)
  • Self-improving agent feedback loops or autonomous learning (see engineering/self-improving-agent)

Integration Points

SkillIntegrationData Flow
engineering/agent-workflow-designerWorkflow definitions consume architecture designs from Agent DesignerAgent roles and communication topology feed into workflow step definitions
engineering/prompt-engineer-toolkitSystem prompts are crafted per agent role defined by Agent DesignerAgent role specifications and responsibilities inform prompt structure and constraints
engineering/mcp-server-builderTool schemas generated here map to MCP server tool implementationstool_schema_generator.py output provides the schema contract that MCP servers implement
engineering/self-improving-agentEvaluation reports feed into self-improvement loopsagent_evaluator.py bottleneck analysis drives autonomous optimization decisions
engineering/observability-designerMonitoring architecture aligns with agent topology and communication linksAgent definitions and communication patterns define what to instrument and alert on
engineering/agent-protocolProtocol standards govern inter-agent message formats designed hereCommunication topology patterns must comply with agent protocol specifications

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Agent Designer AI skill do?

Designs multi-agent system architectures with orchestration patterns, tool schemas, and performance evaluation. Use when building AI agent systems, designing agent workflows, creating tool schemas, or evaluating agent performance.

Why use Agent Designer on TypingMind?

Because you install it once and use it with any model. Agent Designer is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Agent Designer in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/borghei/Claude-Skills/tree/main/engineering/agent-designer. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Agent Designer?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Agent Designer?

As many as you like. As long as a model supports skills, you can use Agent Designer with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Agent Designer AI skill free?

It is published on GitHub by borghei. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇