langgraph-docs
Skill0 starsChanged 9 months agoMITView on GitHub
Access up-to-date LangGraph Python documentation to provide accurate implementation guidance. Use when requests involve LangGraph concepts, APIs, or implementation questions including (1) building agents with LangGraph, (2) creating state graphs and workflows, (3) using LangGraph checkpointing and persistence, (4) implementing human-in-the-loop patterns, (5) deploying LangGraph applications, or (6) any LangGraph-specific questions requiring current documentation.
4 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- langchain-ai/docstheir own version, first seen Oct 13, 2026
- langchain-ai/deepagentsjsedited, first seen Oct 13, 2026
- langchain-ai/deepagentstheir own version, first seen Oct 13, 2026
- workatustadarshajay/CareLoop-AItheir own version, first seen Oct 9, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- langchain-ai/deepagentsjs★ 1.6k25% same
Wrote their own version · 3
- langchain-ai/deepagents★ 31ksame name
- langchain-ai/docs★ 445same name
- workatustadarshajay/CareLoop-AI★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
7
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
- Distinctive: line 16
Use the WebFetch tool to read the documentation index:
- Distinctive: line 35
Use the WebFetch tool to read each selected documentation URL:
- Distinctive: line 41
Read 2-4 documentation pages to gather comprehensive context.
- Distinctive: line 45
After reading the documentation:
- Distinctive: line 54
Multiple topics: If the question spans multiple topics (e.g., "agents with persistence"), fetch documentation for each topic
- Distinctive: line 55
Code examples: Always include working code examples from the documentation
- Distinctive: line 56
Version compatibility: Check if the documentation mentions version-specific behavior
“Common” is measured: kept by at least 6 in 10 of the 4 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.
Files
LangGraph Documentation
Overview
This skill provides access to the official LangGraph Python documentation to answer questions and guide implementation with accurate, up-to-date information.
Workflow
1. Fetch the Documentation Index
Use the WebFetch tool to read the documentation index:
WebFetch with url="https://docs.langchain.com/llms.txt" and prompt="Extract the full list of documentation URLs with their descriptions"This index provides a structured list of all available LangGraph documentation with descriptions.
2. Select Relevant Documentation
Based on the user's question, identify 2-4 most relevant documentation URLs from the index. Prioritize:
- How-to guides for implementation questions (e.g., "How do I create a checkpointer?")
- Concept pages for understanding questions (e.g., "What is a state graph?")
- Tutorials for end-to-end examples (e.g., "Build a chatbot with LangGraph")
- API reference for detailed API information (e.g., "StateGraph parameters")
3. Fetch Selected Documentation
Use the WebFetch tool to read each selected documentation URL:
WebFetch with url="[selected-doc-url]" and prompt="Extract all content including code examples, explanations, and API details"Read 2-4 documentation pages to gather comprehensive context.
4. Provide Accurate Guidance
After reading the documentation:
- Answer the user's question with information directly from the documentation
- Include code examples from the documentation when relevant
- Cite specific documentation URLs for reference
- Recommend additional documentation pages if the user needs more context
Tips
- Multiple topics: If the question spans multiple topics (e.g., "agents with persistence"), fetch documentation for each topic
- Code examples: Always include working code examples from the documentation
- Version compatibility: Check if the documentation mentions version-specific behavior
- Related concepts: Suggest related documentation that might be helpful for the user's broader goals
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
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.

