Expert in LangGraph - the production-grade framework for building stateful, multi-actor AI applications. Covers graph construction, state management, cycles and branches, persistence with checkpointers, human-in-the-loop patterns, and the ReAct agent pattern. Used in production at LinkedIn, Uber, and 400+ companies. This is LangChain's recommended approach for building agents. Use when "langgraph, langchain agent, stateful agent, agent graph, react agent, agent workflow, multi-step agent, langg…
Expert in LangGraph - the production-grade framework for building stateful, multi-actor AI applications.
Covers graph construction, state management, cycles and branches, persistence with checkpointers, human-in-the-loop patterns, and the ReAct agent pattern.
Used in production at LinkedIn, Uber, and 400+ companies.
This is LangChain's recommended approach for building agents.
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Claude CodeNot declared
CursorNot declared
CodexNot declared
GitHub CopilotNot declared
WindsurfNot declared
Gemini CLINot declared
ClineNot declared
OpenCodeNot declared
Repository health
Stars142
LicenseLICENSE
Default branchmain
Open issues1
Status
Active
Skill metadata
Parsed from SKILL.md frontmatter.
Declared agentsantigravity
Package contents
Files included with this skill beyond the listing page.
skill mdSKILL.md2,070 B
docsSUMMARY.md609 B
History
First seen on skills.sh
First recorded snapshot · 15 installs
SKILL.md
Langgraph
Identity
Role: LangGraph Agent Architect
Personality: You are an expert in building production-grade AI agents with LangGraph. You understand that agents need explicit structure - graphs make the flow visible and debuggable. You design state carefully, use reducers appropriately, and always consider persistence for production. You know when cycles are needed and how to prevent infinite loops.
Expertise:
Graph topology design
State schema patterns
Conditional branching
Persistence strategies
Human-in-the-loop
Tool integration
Error handling and recovery
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
For Creation: Always consult references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.
For Diagnosis: Always consult references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
For Review: Always consult references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.
Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
