langgraph-master
Use when specifying or implementing LangGraph applications - from architecture planning and specification writing to actual code implementation. Also use for designing agent workflows or learning LangGraph patterns. This is a comprehensive guide for building AI agents with LangGraph, covering core concepts, architecture patterns, memory management, tool integration, and advanced features.
What this skill does
# LangGraph Agent Construction Skill
A comprehensive guide for building AI agents using LangGraph.
## ๐ Learning Content
### [01. Core Concepts](01_core_concepts_overview.md)
Understanding the three core elements of LangGraph
- [State](01_core_concepts_state.md)
- [Node](01_core_concepts_node.md)
- [Edge](01_core_concepts_edge.md)
- Advantages of the graph-based approach
### [02. Graph Architecture](02_graph_architecture_overview.md)
Six major graph patterns and agent design
- [Workflow vs Agent Differences](02_graph_architecture_workflow_vs_agent.md)
- [Prompt Chaining (Sequential Processing)](02_graph_architecture_prompt_chaining.md)
- [Parallelization](02_graph_architecture_parallelization.md)
- [Routing (Branching)](02_graph_architecture_routing.md)
- [Orchestrator-Worker](02_graph_architecture_orchestrator_worker.md)
- [Evaluator-Optimizer](02_graph_architecture_evaluator_optimizer.md)
- [Agent (Autonomous Tool Usage)](02_graph_architecture_agent.md)
- [Subgraph](02_graph_architecture_subgraph.md)
### [03. Memory Management](03_memory_management_overview.md)
Persistence and checkpoint functionality
- [Checkpointer](03_memory_management_checkpointer.md)
- [Store (Long-term Memory)](03_memory_management_store.md)
- [Persistence](03_memory_management_persistence.md)
### [04. Tool Integration](04_tool_integration_overview.md)
External tool integration and execution control
- [Tool Definition](04_tool_integration_tool_definition.md)
- [Command API (Control API)](04_tool_integration_command_api.md)
- [Tool Node](04_tool_integration_tool_node.md)
### [05. Advanced Features](05_advanced_features_overview.md)
Advanced functionality and implementation patterns
- [Human-in-the-Loop (Approval Flow)](05_advanced_features_human_in_the_loop.md)
- [Streaming](05_advanced_features_streaming.md)
- [Map-Reduce Pattern](05_advanced_features_map_reduce.md)
### [06. LLM Model IDs](06_llm_model_ids.md)
Model ID reference for major LLM providers. Always refer to this document when selecting model IDs. Do not use models not listed in this document.
- Google Gemini model list
- Anthropic Claude model list
- OpenAI GPT model list
- Usage examples and best practices with LangGraph
### Implementation Examples
Practical agent implementation examples
- [Basic Chatbot](example_basic_chatbot.md)
- [RAG Agent](example_rag_agent.md)
## ๐ How to Use
Each section can be read independently, but reading them in order is recommended:
1. First understand LangGraph fundamentals in "Core Concepts"
2. Learn design patterns in "Graph Architecture"
3. Grasp implementation details in "Memory Management" and "Tool Integration"
4. Master advanced features in "Advanced Features"
5. Check practical usage in "Implementation Examples"
Each file is kept short and concise, allowing you to reference only the sections you need.
## ๐ค Efficient Implementation: Utilizing Subagents
To accelerate LangGraph application development, utilize the dedicated subagent `langgraph-master-plugin:langgraph-engineer`.
### Subagent Characteristics
**langgraph-master-plugin:langgraph-engineer** is an agent specialized in implementing functional modules:
- **Functional Unit Scope**: Implements complete functionality with multiple nodes, edges, and state definitions as a set
- **Parallel Execution Optimization**: Designed for multiple agents to develop different functional modules simultaneously
- **Skill-Driven**: Always references the langgraph-master skill before implementation
- **Complete Implementation**: Generates fully functional modules (no TODOs or placeholders)
- **Appropriate Size**: Functional units of about 2-5 nodes (subgraphs, workflow patterns, tool integrations, etc.)
### When to Use
Use langgraph-master-plugin:langgraph-engineer in the following cases:
1. **When functional module implementation is needed**
- Decompose the application into functional units
- Efficiently develop each function through parallel execution
2. **Subgraph and pattern implementation**
- RAG search functionality (retrieve โ rerank โ generate)
- Human-in-the-Loop approval flow (propose โ wait_approval โ execute)
- Intent analysis functionality (analyze โ classify โ route)
3. **Tool integration and memory setup**
- Complete tool integration module (definition โ execution โ processing โ error handling)
- Memory management module (checkpoint setup โ persistence โ restoration)
### Practical Example
**Task**: Build a chatbot with intent analysis and RAG search
**Parallel Execution Pattern**:
```
Planner โ Decompose into functional units
โโ langgraph-master-plugin:langgraph-engineer 1: Intent analysis module (parallel)
โ โโ analyze + classify + route nodes + conditional edges
โโ langgraph-master-plugin:langgraph-engineer 2: RAG search module (parallel)
โโ retrieve + rerank + generate nodes + state management
Orchestrator โ Integrate modules to assemble graph
```
### Usage Method
1. **Decompose into functional modules**
- Decompose large LangGraph applications into functional units
- Verify that each module can be implemented and tested independently
- Verify that module size is appropriate (about 2-5 nodes)
2. **Implement common parts first**
- State used across the entire graph
- Common tool definitions and common nodes used throughout
3. **Parallel Execution**
Assign one functional module implementation to each langgraph-master-plugin:langgraph-engineer agent and execute in parallel
- Implement independent functional modules simultaneously
4. **Integration**
- Incorporate completed modules into the graph
- Verify operation through integration testing
### Testing Method
- Perform unit testing for each functional module
- Verify overall operation after integration. In many cases, there's an API key in .env, so load it and run at least one successful test case
- If the successful case doesn't work well, code review is important, but roughly pinpoint the location, add appropriate logs to identify the cause, think carefully, and then fix.
### Functional Module Examples
**Appropriate Size (langgraph-master-plugin:langgraph-engineer scope)**:
- RAG search functionality: retrieve + rerank + generate (3 nodes)
- Intent analysis: analyze + classify + route (2-3 nodes)
- Approval workflow: propose + wait_approval + execute (3 nodes)
- Tool integration: tool_call + execute + process + error_handling (3-4 nodes)
**Too Small (individual implementation is sufficient)**:
- Single node only
- Single edge only
- State field definition only
**Too Large (further decomposition needed)**:
- Complete chatbot application
- Entire system containing multiple independent functions
### Notes
- **Appropriate Scope Setting**: Verify that each task is limited to one functional module
- **Functional Independence**: Minimize dependencies between modules
- **Interface Design**: Clearly document state contracts between modules
- **Integration Plan**: Plan the integration method after module implementation in advance
## ๐ Reference Links
- [LangGraph Official Documentation](https://docs.langchain.com/oss/python/langgraph/overview)
- [LangGraph GitHub](https://github.com/langchain-ai/langgraph)
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts โ single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score โฅ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.