agentleFS
magnus919magnus919/agent-skills/langgraph/SKILL.md

langgraph

Skill172 starsChanged 4 months agoMITView on GitHub

Build multi-agent AI systems with LangGraph — the low-level orchestration framework for stateful, graph-based agent workflows. Covers supervisor, swarm, and hierarchical multi-agent patterns; subgraph composition; state management (checkpointers/stores); persistence; evals; and production debugging. Reach for this when designing agent architectures that need cycles, conditional branching, parallel execution, or human-in-the-loop patterns. Do not use this skill for unrelated requests; route to the nearest named specialist.

  • Installs packages

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use gcp-cloud-run, mcp-builder and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • xfstudioSkill

    gcp-cloud-run

    Specialized skill for building production-ready serverless applications on GCP. Covers Cloud Run services (containerized), Cloud Run Functions (event-driven), cold start optimization, and event-driven architecture with Pub/Sub.

    Also in 3 projects that use this

  • MicrosoftSkill

    mcp-builder

    Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create your first LangGraph agent in under 10 lines:

    line 31
  2. Distinctive:

    Use the Pattern Selection Guide below to choose supervisor, swarm, or hierarchical architecture — each pattern links to its recommended …

    line 49
  3. Distinctive:

    Use the Choosing Your Starting Point table below to pick scaffold, template, or reference based on your task

    line 51

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

LangGraph

LangGraph is LangChain's low-level orchestration framework for building stateful, long-running, multi-agent AI workflows using directed graph architectures (inspired by Pregel/Beam and NetworkX). It models agents as nodes in a graph, with edges controlling flow — enabling cycles, conditional branching, parallel execution, human-in-the-loop, and subgraph composition that linear chains cannot express.

This skill covers all major patterns for building and deploying LangGraph systems: core graph architecture, the three canonical multi-agent patterns (supervisor, swarm, hierarchical), persistence and state management, production debugging, and evaluation methodology.

Before you begin: Install dependencies:

pip install langgraph langchain langchain-openai langsmith

Quick Start

Create your first LangGraph agent in under 10 lines:

from langgraph.graph import StateGraph, MessagesState, START, END

def hello_agent(state: MessagesState):
    return {"messages": [{"role": "ai", "content": "Hello, world!"}]}

graph = StateGraph(MessagesState)
graph.add_node("agent", hello_agent)
graph.add_edge(START, "agent")
graph.add_edge("agent", END)
graph = graph.compile()

graph.invoke({"messages": [{"role": "user", "content": "hi!"}]})

Next steps:

  1. Use the Pattern Selection Guide below to choose supervisor, swarm, or hierarchical architecture — each pattern links to its recommended template
  2. Load the corresponding reference file for the deep pattern walkthrough
  3. Use the Choosing Your Starting Point table below to pick scaffold, template, or reference based on your task
  4. For a complete runnable example matching your pattern, use the linked template in assets/templates/

Design Principles — These Govern Every Graph Decision

  1. State is the source of truth — all inter-node communication happens through state, not through side channels or global variables.
  2. Nodes are pure-ish — a node receives state, does work, returns updates. It should not depend on state that isn't passed to it.
  3. Reducers prevent conflicts — any state key written by multiple nodes in parallel MUST have a reducer.
  4. Start simple — a single agent with good prompts beats a multi-agent system with bad routing. Add agents only when a single prompt or toolset becomes unwieldy.
  5. Use Send() for dynamic fan-out — when you don't know how many workers you'll need at compile time, spawn them dynamically from the orchestrator node.
  6. Subgraph state isolation — subgraphs with different state schemas need a wrapper function to transform state at the boundary. Shared-schema subgraphs can be added directly as nodes.

When to Reach For This

ContextWhat to load
Building a new LangGraph workflow from scratchreferences/architecture.md — core concepts first
Designing a multi-agent routing systemreferences/multi-agent-supervisor.md or references/multi-agent-swarm.md — compare patterns
Composing nested agent teamsreferences/multi-agent-hierarchical.md — subgraph composition
Adding persistence, interrupts, or long-term memoryreferences/persistence.md — checkpointers and stores
Deploying to production or debugging failuresreferences/production.md — deployment, observability, failure modes
Setting up eval pipelines for routing accuracyreferences/evals.md — evaluation methodology
Diagnosing a specific failure (loop, context loss, crash)references/troubleshooting.md — known failure modes
Placing a typed System One judgment in a graphreferences/architecture.md; decision contract and calibration in System One, workflow authority and whole-task evidence in harness-engineering

Pattern Selection Guide

Your constraintPreferWhy
Routing accuracy > latencySupervisorCentralized routing node, focused prompt: ~94% accuracyassets/templates/supervisor-graph.py
Latency is primary constraintSwarmDirect agent-to-agent handoffs, ~40% fewer LLM callsassets/templates/swarm-graph.py
Clear domain boundariesSwarmAgents rarely misroute, handoffs are crispassets/templates/swarm-graph.py
Ambiguous domain boundariesSupervisorOverlapping concerns resolved by dedicated routerassets/templates/supervisor-graph.py
< 3 distinct domainsSkip multi-agentA specialized single agent is simplerreferences/architecture.md
Multi-domain requests commonSwarmLatency savings compound across handoffsassets/templates/swarm-graph.py
Need centralized audit trailSupervisorEvery routing decision visible in tracesassets/templates/supervisor-graph.py
Nested team structuresHierarchicalSubgraphs as nodes, each team self-containedassets/templates/subgraph-agent.py

Choosing Your Starting Point

Your goalStart withWhy
Build a project from scratch, need generated codescripts/lg-supervisor-scaffold.py or scripts/lg-swarm-scaffold.pyScaffolds generate complete project structure (state.py, agents.py, graph.py) with placeholders to fill in
Understand a complete, working exampleassets/templates/ matching your chosen patternTemplates are self-contained runnable files with all patterns wired — best for learning by reading
Deep dive into a pattern's internalsCorresponding reference in references/References explain tradeoffs, failure modes, and design rationale — best for customization
Debug or optimize an existing systemreferences/production.md or references/troubleshooting.mdProduction reference covers deployment + observability; troubleshooting reference covers symptom→fix tables

Core Primitives

LangGraph uses two APIs:

APIWhen to usePattern
Graph API (StateGraph)Full control over graph structure, conditional edges, subgraphsadd_node() + add_edge()/add_conditional_edges()
Functional API (@task + @entrypoint)Simpler linear workflows, less boilerplateDecorator-based, Pythonic

Both APIs produce the same compiled graph — choose based on how much control you need.

Key Gotchas

  • Subgraph persistence defaults to per-invocation — each subgraph call starts fresh. Set checkpointer=True for per-thread memory, checkpointer=False for fully stateless.
  • Per-thread subgraphs cannot run in parallel — same-namespace checkpoint conflicts. Use ToolCallLimitMiddleware or disable parallel tool calls.
  • The supervisor bottleneck — every interaction requires a routing LLM call, even for obvious intents. Add a fast-path classifier (keyword matching or small model) for unambiguous requests.
  • Swarm ping-pong — no natural recursion guard. Track handoff_count in state and hard-limit at 3, then escalate to human or fallback agent.
  • Lost messages on handoff — Command.update must include paired messages from the specialist's tool-calling loop, or the next agent sees malformed history.
  • State access from parent to subgraph — subgraphs manage their own checkpoint namespace. Use Store for cross-graph-boundary data.
  • Checkpoint bloat — long conversations accumulate checkpoints. Prune periodically or set retention policies on DB-backed checkpointers.
  • No auto-load-on-install — skills aren't auto-discovered at session start by name mention. The agent must explicitly call skill_view(name='langgraph') to load this skill.

Reference Files

FileLoad when
references/architecture.mdYou need to understand LangGraph core concepts: graph structure, nodes, edges, state, the two APIs, and basic agent loop construction. Read this first if you're new to LangGraph.
references/multi-agent-supervisor.mdYou're designing a supervisor-based multi-agent system with a central routing node. Contains architecture, structured output routing, specialist wrappers, and full code examples.
references/multi-agent-swarm.mdYou're designing a swarm-based multi-agent system with direct agent-to-agent handoffs. Contains handoff tool patterns, Command-based routing, and comparative metrics vs supervisor.
references/multi-agent-hierarchical.mdYou're composing nested agent teams using subgraphs. Covers subgraph wiring (shared vs different state schemas), persistence modes, namespace isolation, and hierarchical team structures.
references/persistence.mdYou're adding checkpointer-based short-term memory or store-based long-term memory. Covers per-invocation vs per-thread vs stateless modes, checkpoint backends, and cross-thread memory patterns.
references/production.mdYou're deploying a LangGraph system to production. Covers Agent Server deployment, LangSmith observability, streaming patterns, and common production failure modes with fixes.
references/evals.mdYou're setting up evaluation pipelines for multi-agent systems. Covers routing accuracy, resolution coverage, LangSmith eval datasets, and LLM-as-judge evaluators.
references/troubleshooting.mdYou're debugging a specific LangGraph failure. Covers routing loops, context loss, checkpointer conflicts, token waste, and state inspection techniques.
assets/templates/supervisor-graph.pyRunnable supervisor example with billing, tech support, and account specialists — fast-path classifier, structured output routing, audit trail, and recursion guard.
assets/templates/swarm-graph.pyRunnable swarm example with triage agent plus 3 specialists — direct agent-to-agent handoffs via Command, recursion guard, and full traceability.
assets/templates/subgraph-agent.pyRunnable subgraph composition examples — all 3 wiring patterns (different state schemas, shared state keys, per-thread with namespace isolation).

Scripts

ScriptWhat it does
scripts/lg-supervisor-scaffold.pyGenerates a complete supervisor pattern project with state schema, routing agent, specialist nodes, and graph assembly
scripts/lg-swarm-scaffold.pyGenerates a complete swarm pattern project with handoff tools, triage agent, specialist agents, and conditional routing
scripts/lg-eval-generator.pyGenerates evaluation datasets and runs LangSmith evaluators for routing accuracy and resolution coverage

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.