Agent skill

Multi Agent Architect

by sickn33 in sickn33/agentic-awesome-skills

Design and optimize production-grade multi-agent systems with LangGraph, LangChain, and DeepAgents for complex AI workflows.

MITAuto-check passedAI & LLM Engineering

Install Multi Agent Architect

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill multi-agent-architect -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills multi-agent-architect --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/multi-agent-architect .claude/skills/multi-agent-architect && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
multi-agent-architect
GitHub stars
47k
Used in
1 other repo
Token cost
~3.1k tokens
SKILL.md length
778 words
Files
1
Skills in repo
1,354
Repo updated
First seen
Licence
MIT

At a glance

Design and optimize production-grade multi-agent systems with LangGraph, LangChain, and DeepAgents for complex AI workflows.

  • Works in 7 steps: Understand the Goal → Define the State Schema → Define Agent Nodes → …
  • Tasks that involve Building AI agents
  • SKILL.md covers Overview, When to Use This Skill, How It Works and Updating an Existing Agent, plus 7 more sections
  • Calls pip; needs OPENAI_API_KEY

What it does

Multi Agent Architect is an agent skill from sickn33/agentic-awesome-skills. Design and optimize production-grade multi-agent systems with LangGraph, LangChain, and DeepAgents for complex AI workflows.

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in AI & LLM Engineering, covering Building AI agents and Multi-agent orchestration. It works with LangGraph and LangChain. The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Tasks that involve Building AI agents
  • Tasks that involve Multi-agent orchestration

Example prompts

  • “/multi-agent-architect”

Requirements

  • Python 3
  • A credential in OPENAI_API_KEY

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Understand the Goal
  2. Define the State Schema
  3. Define Agent Nodes
  4. Build the LangGraph
  5. Add Memory
  6. Run the Graph
  7. Expose via FastAPI (optional)

What it can do on your machine

Read from SKILL.md and the folder at commit ec02547. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pip

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pip, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • OPENAI_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Multi Agent Architect loads about 3.1k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 778 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit ec02547, republished under its MIT licence (© sickn33). 778 words, ~3,053 tokens.

Download SKILL.mdSave it as .claude/skills/multi-agent-architect/SKILL.md (or your agent's skills folder).
name
multi-agent-architect
description
Design and optimize production-grade multi-agent systems with LangGraph, LangChain, and DeepAgents for complex AI workflows.
risk
safe
source
community
date_added
2026-09-04
metadata.category
ai-engineering
metadata.source_repo
pravin-python/antigravity-awesome-skills
metadata.source_type
community
metadata.date_added
2025-05-07
metadata.author
community
metadata.tags
langgraph, langchain, multi-agent, orchestration, deepagents, rag, tool-calling
metadata.tools
claude, cursor, gemini

Multi-Agent Architect & Updater Skill

Overview

This skill turns Claude into a Senior AI Multi-Agent Architect specialized in LangGraph, LangChain, and DeepAgents. It provides structured workflows for creating and updating production-grade multi-agent systems — including supervisor agents, planners, researchers, coders, and memory-backed autonomous pipelines. Use it whenever you need to design, build, debug, or scale any multi-agent AI system.

If this skill adapts material from an external GitHub repository, declare both:

  • source_repo: owner/repo
  • source_type: official or source_type: community

When to Use This Skill

  • Use when you need to create a new agent or multi-agent workflow from scratch
  • Use when working with LangGraph state graphs, nodes, edges, or conditional routing
  • Use when the user asks about agent communication, memory systems, or tool-calling pipelines
  • Use when debugging or optimizing an existing LangChain/LangGraph agent system
  • Use when architecting supervisor, planner, research, coding, or validation agent roles
  • Use when integrating DeepAgents with hierarchical planning and delegation

How It Works

Step 1: Understand the Goal

Before writing any code, clarify:

  • What is the business objective this agent system must achieve?
  • What agent roles are needed (supervisor, planner, researcher, coder, validator)?
  • What tools does each agent require?
  • What memory strategy is needed (Redis, Vector DB, LangChain Memory)?
  • What communication protocol connects agents (shared state, message passing)?
Step 2: Define the State Schema

All agents share a typed state object passed through the graph:

python
from typing import TypedDict

class AgentState(TypedDict):
    user_goal: str
    tasks: list[str]
    completed_tasks: list[str]
    next_agent: str
    context: dict
    step_count: int          # guards against infinite loops
    error: str | None
Step 3: Define Agent Nodes

Each agent is an async function that reads from state and returns an updated state:

python
import logging
from langchain_openai import ChatOpenAI

logger = logging.getLogger(__name__)

async def research_node(state: AgentState) -> AgentState:
    logger.info("research_node: starting")
    llm = ChatOpenAI(model="gpt-4o")
    result = await llm.bind_tools(research_tools).ainvoke(state["user_goal"])
    state["context"]["research"] = result.content
    state["next_agent"] = "coder"
    return state
Step 4: Build the LangGraph

Wire nodes together with edges and conditional routing:

python
from langgraph.graph import StateGraph, END
from langgraph.prebuilt import ToolNode

def build_graph() -> StateGraph:
    graph = StateGraph(AgentState)

    graph.add_node("supervisor", supervisor_node)
    graph.add_node("research",   research_node)
    graph.add_node("coder",      coding_node)
    graph.add_node("validator",  validation_node)
    graph.add_node("tools",      ToolNode(all_tools))

    graph.set_entry_point("supervisor")

    graph.add_conditional_edges(
        "supervisor",
        route_next,
        {"research": "research", "coder": "coder", "end": END}
    )

    graph.add_edge("research",  "supervisor")
    graph.add_edge("coder",     "validator")
    graph.add_edge("validator", "supervisor")

    return graph.compile()

def route_next(state: AgentState) -> str:
    if state["step_count"] > 20:
        return "end"
    return state["next_agent"]
Step 5: Add Memory
python
from langchain_community.chat_message_histories import RedisChatMessageHistory

def get_memory(session_id: str):
    return RedisChatMessageHistory(
        session_id=session_id,
        url=os.getenv("REDIS_URL"),
        ttl=3600
    )
Step 6: Run the Graph
python
async def run(user_goal: str, session_id: str):
    graph = build_graph()
    initial_state = AgentState(
        user_goal=user_goal,
        tasks=[],
        completed_tasks=[],
        next_agent="supervisor",
        context={},
        step_count=0,
        error=None,
    )
    return await graph.ainvoke(initial_state)
Step 7: Expose via FastAPI (optional)
python
from fastapi import FastAPI
from pydantic import BaseModel

app = FastAPI()

class RunRequest(BaseModel):
    goal: str
    session_id: str

@app.post("/run")
async def run_agent(req: RunRequest):
    result = await run(req.goal, req.session_id)
    return {"result": result}

Updating an Existing Agent

When the user wants to update or debug an existing agent, structure the response as:

## Existing Issue
[Describe the current problem]

## Root Cause
[Identify why it's happening in the architecture]

## Proposed Update
[Outline the changes at architecture level]

## Updated Code
[Generate only the changed modules]

## Migration Notes
[What breaks, what's backward-compatible]

## Performance Impact
[Latency / token / memory delta]

Standard Folder Structure

Always generate code in this layout:

multi_agent_system/
├── agents/          # One file per agent role
├── tools/           # Tool definitions and wrappers
├── memory/          # Redis, VectorDB, LangChain memory helpers
├── prompts/         # Prompt templates (one per agent)
├── workflows/       # High-level orchestration logic
├── graphs/          # LangGraph state + compiled graph definitions
├── api/             # FastAPI routes (optional)
├── configs/         # Config loader — no secrets in code
├── tests/           # Unit + integration tests per agent
└── main.py

Examples

Example 1: Research + Coding Multi-Agent Workflow
python
# agents/research_agent.py
async def research_node(state: AgentState) -> AgentState:
    llm = ChatOpenAI(model="gpt-4o").bind_tools([web_search, rag_search])
    response = await llm.ainvoke(
        f"Research the following and return structured findings:\n{state['user_goal']}"
    )
    state["context"]["research"] = response.content
    state["next_agent"] = "coder"
    return state

# agents/coding_agent.py
async def coding_node(state: AgentState) -> AgentState:
    llm = ChatOpenAI(model="gpt-4o").bind_tools([python_repl, github_tool])
    response = await llm.ainvoke(
        f"Given this research:\n{state['context']['research']}\n\nWrite production Python code."
    )
    state["context"]["code"] = response.content
    state["next_agent"] = "validator"
    return state
Example 2: Supervisor with Dynamic Delegation
python
# agents/supervisor_agent.py
DELEGATION_PROMPT = """
You are a supervisor. Given the current state, decide the next agent.
Available agents: research, coder, validator, end.
Respond with ONLY the agent name.

Goal: {goal}
Completed: {completed}
Context keys available: {context}
"""

async def supervisor_node(state: AgentState) -> AgentState:
    state["step_count"] += 1
    llm = ChatOpenAI(model="gpt-4o")
    decision = await llm.ainvoke(
        DELEGATION_PROMPT.format(
            goal=state["user_goal"],
            completed=state["completed_tasks"],
            context=list(state["context"].keys()),
        )
    )
    next_agent = decision.content.strip().lower()
    # Validate against allowlist before setting
    allowed = {"research", "coder", "validator", "end"}
    state["next_agent"] = next_agent if next_agent in allowed else "end"
    return state
Example 3: DeepAgents Reflection Loop
python
async def reflection_node(state: AgentState) -> AgentState:
    llm = ChatOpenAI(model="gpt-4o")
    critique = await llm.ainvoke(
        f"Evaluate this output critically:\n{state['context'].get('code', '')}\n"
        "List any bugs, gaps, or improvements. Be concise."
    )
    state["context"]["critique"] = critique.content
    state["next_agent"] = "coder" if "bug" in critique.content.lower() else "end"
    return state

Best Practices

  • ✅ One agent = one responsibility — never combine planning + coding + testing in one node
  • ✅ Use TypedDict for all state schemas — enables type checking and graph validation
  • ✅ Bind only the tools each agent needs — reduces hallucinated tool calls
  • ✅ Always add a step_count guard to prevent infinite routing loops
  • ✅ Use async/await throughout — LangGraph supports async natively
  • ✅ Store all secrets in environment variables loaded via os.getenv()
  • ✅ Set TTLs on all Redis keys scoped to session_id
  • ✅ Log at every node entry and tool call for observability
  • ✅ Validate supervisor routing output against an allowlist of agent names
  • ❌ Don't hardcode API keys, model names, or Redis URLs
  • ❌ Don't share tool lists across agents that don't need them
  • ❌ Don't skip error handling — tool failures and empty LLM responses are common
  • ❌ Don't trust unvalidated LLM routing decisions — always check against an allowlist

Show full SKILL.md (346 more words)Show less

Limitations

  • This skill does not replace environment-specific testing, load testing, or security review before production deployment.
  • Generated LangGraph code targets the current stable API — always verify method signatures against your installed version (pip show langgraph).
  • Stop and ask for clarification if the agent's goal, tool permissions, or routing logic is ambiguous before generating a full architecture.
  • DeepAgents integration patterns assume the library is installed and configured in the target environment.

Security & Safety Notes

  • Never expose API keys in generated code. All secrets must use environment variables:
    python
    OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")   # ✅ correct
    leaked_openai_token = "[redacted API key]"       # ❌ never do this
  • Always validate and sanitize user inputs before injecting them into agent prompts — treat all user input as untrusted.
  • Add a permission layer before allowing agents to execute shell commands or write to filesystems.
  • If generating a Python REPL tool node, document that it must only run in a sandboxed, isolated environment.
    <!-- security-allowlist: python_repl tool examples are for sandboxed execution environments only -->
  • For production deployments, add rate-limit handling and exponential backoff on all LLM and external API calls.
  • Scope all Redis session keys to session_id and set a TTL to prevent memory leaks across sessions.

Common Pitfalls

  • Problem: Agent loops indefinitely between supervisor and sub-agents
    Solution: Add step_count: int to state; return "end" in route_next() when step_count > N

  • Problem: Supervisor routes to a non-existent agent name
    Solution: Validate the LLM's routing output against a hardcoded allowlist before setting next_agent

  • Problem: Memory leaks across user sessions
    Solution: Scope Redis keys to session_id and always set a TTL (ttl=3600)

  • Problem: Tool results are ignored by the next agent
    Solution: Always write tool output into state["context"] and confirm the next node reads it

  • Problem: Agents share too many tools and hallucinate wrong tool calls
    Solution: Use .bind_tools([only_relevant_tools]) per agent instead of a global tool list

  • Problem: Graph fails silently on API rate limits
    Solution: Wrap LLM calls in retry logic with exponential backoff using tenacity


  • @langchain-rag - When you need retrieval-augmented generation pipelines specifically
  • @fastapi-backend - When deploying agent systems as production REST APIs
  • @python-async - When deepening async/await patterns used throughout agent nodes

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/multi-agent-architect of sickn33/agentic-awesome-skills.

Open the folder on GitHubat commit ec02547

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Multi Agent Architect next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Multi Agent Architect compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Multi Agent Architect this skillsickn33/agentic-awesome-skills47k1 repos~3.1kAutomated safety check: PassMIT
Dive Into LangGraphluochang212/dive-into-langgraph457—~837Automated safety check: NotesCustom licence
Langgraphmagnus919/agent-skills113—~2.8kAutomated safety check: PassMIT
Mem0 Platform SDKmem0ai/mem067k2 repos~2.2kAutomated safety check: PassApache-2.0
Add Example AgentGetBindu/Bindu10k—~1.1kAutomated safety check: NotesCustom licence
Agent Inspectrajudandigam/agent-inspect165—~424Automated safety check: PassMIT

Similar skills

  • Dive Into LangGraph

    luochang212/dive-into-langgraph

    A Chinese-language guide and reference for building agents with LangGraph 1.0, from a first ReAct agent through middleware, memory, MCP, RAG and web search.

    457 GitHub stars~837 tokensUpdated 27 days ago
    AI & LLM EngineeringAuto-check: notes
  • Langgraph

    magnus919/agent-skills

    Build multi-agent AI systems with LangGraph — the low-level orchestration framework for stateful, graph-based agent workflows.

    113 GitHub stars~2.8k tokensUpdated 2 days ago
    AI & LLM EngineeringAuto-check passed
  • Adds persistent memory to AI apps with the Mem0 Python and TypeScript SDKs: store, search, update and delete user memories, with framework integrations.

    67k GitHub starsUsed in 2 repos~2.2k tokens
    AI & LLM EngineeringAuto-check passed
  • Add Example Agent

    GetBindu/Bindu

    Add a new self-contained example agent under examples/. An agent skill from GetBindu/Bindu.

    10k GitHub stars~1.1k tokensUpdated 1 mo ago
    AI & LLM EngineeringAuto-check: notes
  • Agent Inspect

    rajudandigam/agent-inspect

    Local evidence debugger and trajectory-test toolkit for TypeScript AI agents.

    165 GitHub stars~424 tokensUpdated today
    AI & LLM EngineeringAuto-check passed
  • Deep Agents Core

    langchain-ai/langchain-skills

    Official

    Explains how to build agents with the Deep Agents framework: create_deep_agent, the built-in middleware, the harness, SKILL.md format and configuration options.

    1.3k GitHub starsUsed in 1 repo~3.1k tokens
    AI & LLM EngineeringAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,354 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed
  • Content Creator

    sickn33/agentic-awesome-skills

    Drafts and reviews audience-specific content from supplied brand examples, with local scripts for brand voice and SEO diagnostics, channel templates and a content calendar.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed

Questions about Multi Agent Architect

What does Multi Agent Architect do?

Design and optimize production-grade multi-agent systems with LangGraph, LangChain, and DeepAgents for complex AI workflows. Multi Agent Architect is an agent skill from sickn33/agentic-awesome-skills. Design and optimize production-grade multi-agent systems with LangGraph, LangChain, and DeepAgents for complex AI workflows.

When should I use Multi Agent Architect?

Multi Agent Architect fits situations like: tasks that involve Building AI agents; tasks that involve Multi-agent orchestration.

How do I install Multi Agent Architect in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill multi-agent-architect -a claude-code`. Or copy the skill folder (skills/multi-agent-architect in sickn33/agentic-awesome-skills) into .claude/skills/multi-agent-architect in your project. Claude Code loads it when a task matches its description.

How do I install Multi Agent Architect in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill multi-agent-architect -a codex`. Or copy the skill folder (skills/multi-agent-architect in sickn33/agentic-awesome-skills) into .agents/skills/multi-agent-architect in your project. Codex loads it when a task matches its description.

Can I use Multi Agent Architect in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill multi-agent-architect -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/multi-agent-architect, .gemini/skills/multi-agent-architect, .github/skills/multi-agent-architect and .opencode/skills/multi-agent-architect in your project.

What does Multi Agent Architect need to run?

Going by SKILL.md and its folder, Multi Agent Architect needs the command-line tools its instructions call (pip) and credentials named OPENAI_API_KEY. Our summary lists: Python 3; A credential in OPENAI_API_KEY.

Does Multi Agent Architect access the network?

SKILL.md contains no URLs. Its commands use pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Multi Agent Architect safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Multi Agent Architect use?

Multi Agent Architect is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Multi Agent Architect use?

About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Multi Agent Architect?

Skills that share tags, products or a category with Multi Agent Architect: Dive Into LangGraph (luochang212/dive-into-langgraph, 457 stars), Langgraph (magnus919/agent-skills, 113 stars), Mem0 Platform SDK (mem0ai/mem0, 67k stars) and Add Example Agent (GetBindu/Bindu, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Multi Agent Architect?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,343 GitHub stars. The repository holds 1,354 skills in this directory. The repository was last updated on October 7, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.