deep-agents-orchestration
Skill1 starsChanged 51 days agoMITView on GitHub
INVOKE THIS SKILL when using subagents, task planning, or human approval in Deep Agents. Covers SubAgentMiddleware, TodoList for planning, and HITL interrupts.
8 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- langchain-ai/design-agentword for word, first seen Oct 25, 2026
- langchain-ai/langchain-skillsword for word, first seen Oct 13, 2026
- willlee1995/skillsedited, first seen Oct 13, 2026
- gerald-donkor/poli-intelword for word, first seen Oct 11, 2026
- zoujindouGithub/agent-skillsedited, first seen Sep 2, 2026
- buduan/soul-graphword for word, first seen Jun 7, 2026
Used with
Projects with it also use managed-deep-agents and langgraph-cli.
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.
LangChainSkillmanaged-deep-agents
INVOKE THIS SKILL when building, testing, or deploying Managed Deep Agents in LangSmith. Walks a user through their first agent end to end — interviewing them about what they want to build, mapping it onto what MDA can actually do, then scaffolding and deploying it with the mda CLI. Routes to the official docs page for each capability: instructions, skills, tools, MCP, connections, middleware, sandboxes, browser use, memory, identity, subagents, schedules, channels, runtime, Context Hub, deploy, and evals.
Also in 4 projects that use this
LangChainSkilllanggraph-cli
INVOKE THIS SKILL when using the langgraph CLI to scaffold, develop, build, or deploy LangGraph applications. Covers langgraph new, dev, build, up, deploy, and langgraph.json configuration.
Also in 3 projects that use this
Other versions8 projects use a version of this.
Word for word · 5
- langchain-ai/langchain-skills★ 1.3k100% same
- langchain-ai/design-agent★ 619100% same
- buduan/soul-graph★ 2100% same
- gerald-donkor/poli-intel★ 1100% same
- danielvogler/ai-skills-library★ 0100% same
Edited · 3
- langchain-ai/skills-benchmarks★ 11695% same
- willlee1995/skills★ 1100% same
- zoujindouGithub/agent-skills★ 146% same
Wrote their own version · 0
None found.
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.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- claude-apiSkill
- deep-agents-coreSkill
- deep-agents-memorySkill
- deepagents-typescript-quickstartSkill
- langchain-dependenciesSkill
- langchain-typescript-quickstartSkill
- langgraph-typescript-quickstartSkill
- swarmSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
All three are automatically included in create_deep_agent().
- Distinctive: line 38
Create a custom "researcher" subagent with specialized tools for academic paper search.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<overview>
Deep Agents include three orchestration capabilities:- SubAgentMiddleware: Delegate work via
tasktool to specialized agents - TodoListMiddleware: Plan and track tasks via
write_todostool - HumanInTheLoopMiddleware: Require approval before sensitive operations
All three are automatically included in create_deep_agent().
</overview>
Subagents (Task Delegation)
<when-to-use-subagents>| Use Subagents When | Use Main Agent When |
| Task needs specialized tools | General-purpose tools sufficient |
| Want to isolate complex work | Single-step operation |
| Need clean context for main agent | Context bloat acceptable |
</when-to-use-subagents><how-subagents-work>
Main agent has `task` tool -> creates fresh subagent -> subagent executes autonomously -> returns final report.Default subagent: "general-purpose" - automatically available with same tools/config as main agent.
</how-subagents-work>
<ex-custom-subagents>
<python>
Create a custom "researcher" subagent with specialized tools for academic paper search.from deepagents import create_deep_agent
from langchain.tools import tool
@tool
def search_papers(query: str) -> str:
"""Search academic papers."""
return f"Found 10 papers about {query}"
agent = create_deep_agent(
subagents=[
{
"name": "researcher",
"description": "Conduct web research and compile findings",
"system_prompt": "Search thoroughly, return concise summary",
"tools": [search_papers],
}
]
)
# Main agent delegates: task(agent="researcher", instruction="Research AI trends")</python>
<typescript>
Create a custom "researcher" subagent with specialized tools for academic paper search.import { createDeepAgent } from "deepagents";
import { tool } from "@langchain/core/tools";
import { z } from "zod";
const searchPapers = tool(
async ({ query }) => `Found 10 papers about ${query}`,
{ name: "search_papers", description: "Search papers", schema: z.object({ query: z.string() }) }
);
const agent = await createDeepAgent({
subagents: [
{
name: "researcher",
description: "Conduct web research and compile findings",
systemPrompt: "Search thoroughly, return concise summary",
tools: [searchPapers],
}
]
});
// Main agent delegates: task(agent="researcher", instruction="Research AI trends")</typescript>
</ex-custom-subagents><ex-subagent-with-hitl>
<python>
Configure a subagent with HITL approval for sensitive operations.from deepagents import create_deep_agent
from langgraph.checkpoint.memory import MemorySaver
agent = create_deep_agent(
subagents=[
{
"name": "code-deployer",
"description": "Deploy code to production",
"system_prompt": "You deploy code after tests pass.",
"tools": [run_tests, deploy_to_prod],
"interrupt_on": {"deploy_to_prod": True}, # Require approval
}
],
checkpointer=MemorySaver() # Required for interrupts
)</python>
</ex-subagent-with-hitl><fix-subagents-are-stateless>
<python>
Subagents are stateless - provide complete instructions in a single call.# WRONG: Subagents don't remember previous calls
# task(agent='research', instruction='Find data')
# task(agent='research', instruction='What did you find?') # Starts fresh!
# CORRECT: Complete instructions upfront
# task(agent='research', instruction='Find data on AI, save to /research/, return summary')</python>
<typescript>
Subagents are stateless - provide complete instructions in a single call.// WRONG: Subagents don't remember previous calls
// task research: Find data
// task research: What did you find? // Starts fresh!
// CORRECT: Complete instructions upfront
// task research: Find data on AI, save to /research/, return summary</typescript>
</fix-subagents-are-stateless><fix-custom-subagents-dont-inherit-skills>
<python>
Custom subagents don't inherit skills from the main agent.# WRONG: Custom subagent won't have main agent's skills
agent = create_deep_agent(
skills=["/main-skills/"],
subagents=[{"name": "helper", ...}] # No skills inherited
)
# CORRECT: Provide skills explicitly (general-purpose subagent DOES inherit)
agent = create_deep_agent(
skills=["/main-skills/"],
subagents=[{"name": "helper", "skills": ["/helper-skills/"], ...}]
)</python>
</fix-custom-subagents-dont-inherit-skills>TodoList (Task Planning)
<when-to-use-todolist>| Use TodoList When | Skip TodoList When |
| Complex multi-step tasks | Simple single-action tasks |
| Long-running operations | Quick operations (< 3 steps) |
</when-to-use-todolist><todolist-tool>write_todos(todos: list[dict]) -> NoneEach todo item has:
content: Description of the taskstatus: One of"pending","in_progress","completed"</todolist-tool>
<ex-todolist-usage>
<python>
Invoke an agent that automatically creates a todo list for a multi-step task.from deepagents import create_deep_agent
agent = create_deep_agent() # TodoListMiddleware included by default
result = agent.invoke({
"messages": [{"role": "user", "content": "Create a REST API: design models, implement CRUD, add auth, write tests"}]
}, config={"configurable": {"thread_id": "session-1"}})
# Agent's planning via write_todos:
# [
# {"content": "Design data models", "status": "in_progress"},
# {"content": "Implement CRUD endpoints", "status": "pending"},
# {"content": "Add authentication", "status": "pending"},
# {"content": "Write tests", "status": "pending"}
# ]</python>
<typescript>
Invoke an agent that automatically creates a todo list for a multi-step task.import { createDeepAgent } from "deepagents";
const agent = await createDeepAgent(); // TodoListMiddleware included
const result = await agent.invoke({
messages: [{ role: "user", content: "Create a REST API: design models, implement CRUD, add auth, write tests" }]
}, { configurable: { thread_id: "session-1" } });</typescript>
</ex-todolist-usage><ex-access-todo-state>
<python>
Access the todo list from the agent's final state after invocation.result = agent.invoke({...}, config={"configurable": {"thread_id": "session-1"}})
# Access todo list from final state
todos = result.get("todos", [])
for todo in todos:
print(f"[{todo['status']}] {todo['content']}")</python>
</ex-access-todo-state><fix-todolist-requires-thread-id>
<python>
Todo list state requires a thread_id for persistence across invocations.# WRONG: Fresh state each time without thread_id
agent.invoke({"messages": [...]})
# CORRECT: Use thread_id
config = {"configurable": {"thread_id": "user-session"}}
agent.invoke({"messages": [...]}, config=config) # Todos preserved</python>
</fix-todolist-requires-thread-id>Human-in-the-Loop (Approval Workflows)
<when-to-use-hitl>| Use HITL When | Skip HITL When |
| High-stakes operations (DB writes, deployments) | Read-only operations |
| Compliance requires human oversight | Fully automated workflows |
</when-to-use-hitl><ex-hitl-setup>
<python>
Configure which tools require human approval before execution.from deepagents import create_deep_agent
from langgraph.checkpoint.memory import MemorySaver
agent = create_deep_agent(
interrupt_on={
"write_file": True, # All decisions allowed
"execute_sql": {"allowed_decisions": ["approve", "reject"]},
"read_file": False, # No interrupts
},
checkpointer=MemorySaver() # REQUIRED for interrupts
)</python>
<typescript>
Configure which tools require human approval before execution.import { createDeepAgent } from "deepagents";
import { MemorySaver } from "@langchain/langgraph";
const agent = await createDeepAgent({
interruptOn: {
write_file: true,
execute_sql: { allowedDecisions: ["approve", "reject"] },
read_file: false,
},
checkpointer: new MemorySaver() // REQUIRED
});</typescript>
</ex-hitl-setup><ex-approval-workflow>
<python>
Complete workflow: trigger an interrupt, check state, approve action, and resume execution.from deepagents import create_deep_agent
from langgraph.checkpoint.memory import MemorySaver
from langgraph.types import Command
agent = create_deep_agent(
interrupt_on={"write_file": True},
checkpointer=MemorySaver()
)
config = {"configurable": {"thread_id": "session-1"}}
# Step 1: Agent proposes write_file - execution pauses
result = agent.invoke({
"messages": [{"role": "user", "content": "Write config to /prod.yaml"}]
}, config=config)
# Step 2: Check for interrupts
state = agent.get_state(config)
if state.next:
print(f"Pending action")
# Step 3: Approve and resume
result = agent.invoke(Command(resume={"decisions": [{"type": "approve"}]}), config=config)</python>
<typescript>
Complete workflow: trigger an interrupt, check state, approve action, and resume execution.import { createDeepAgent } from "deepagents";
import { MemorySaver, Command } from "@langchain/langgraph";
const agent = await createDeepAgent({
interruptOn: { write_file: true },
checkpointer: new MemorySaver()
});
const config = { configurable: { thread_id: "session-1" } };
// Step 1: Agent proposes write_file - execution pauses
let result = await agent.invoke({
messages: [{ role: "user", content: "Write config to /prod.yaml" }]
}, config);
// Step 2: Check for interrupts
const state = await agent.getState(config);
if (state.next) {
console.log("Pending action");
}
// Step 3: Approve and resume
result = await agent.invoke(
new Command({ resume: { decisions: [{ type: "approve" }] } }), config
);</typescript>
</ex-approval-workflow><ex-reject-with-feedback>
<python>
Reject a pending action with feedback, prompting the agent to try a different approach.result = agent.invoke(
Command(resume={"decisions": [{"type": "reject", "message": "Run tests first"}]}),
config=config,
)</python>
<typescript>
Reject a pending action with feedback, prompting the agent to try a different approach.const result = await agent.invoke(
new Command({ resume: { decisions: [{ type: "reject", message: "Run tests first" }] } }),
config,
);</typescript>
</ex-reject-with-feedback><ex-edit-before-execution>
<python>
Edit the proposed action arguments before allowing execution.result = agent.invoke(
Command(resume={"decisions": [{
"type": "edit",
"edited_action": {
"name": "execute_sql",
"args": {"query": "DELETE FROM users WHERE last_login < '2020-01-01' LIMIT 100"},
},
}]}),
config=config,
)</python>
</ex-edit-before-execution><boundaries>
### What Agents CAN Configure- Subagent names, tools, models, system prompts
- Which tools require approval
- Allowed decision types per tool
- TodoList content and structure
What Agents CANNOT Configure
- Tool names (
task,write_todos) - HITL protocol (approve/edit/reject structure)
- Skip checkpointer requirement for interrupts
- Make subagents stateful (they're ephemeral)
</boundaries>
<fix-checkpointer-required>
<python>
Checkpointer is required when using interrupt_on for HITL workflows.# WRONG
agent = create_deep_agent(interrupt_on={"write_file": True})
# CORRECT
agent = create_deep_agent(interrupt_on={"write_file": True}, checkpointer=MemorySaver())</python>
<typescript>
Checkpointer is required when using interruptOn for HITL workflows.// WRONG
const agent = await createDeepAgent({ interruptOn: { write_file: true } });
// CORRECT
const agent = await createDeepAgent({ interruptOn: { write_file: true }, checkpointer: new MemorySaver() });</typescript>
</fix-checkpointer-required><fix-thread-id-required-for-resumption>
<python>
A consistent thread_id is required to resume interrupted workflows.# WRONG: Can't resume without thread_id
agent.invoke({"messages": [...]})
# CORRECT
config = {"configurable": {"thread_id": "session-1"}}
agent.invoke({...}, config=config)
# Resume with Command using same config
agent.invoke(Command(resume={"decisions": [{"type": "approve"}]}), config=config)</python>
<typescript>
A consistent thread_id is required to resume interrupted workflows.// WRONG: Can't resume without thread_id
await agent.invoke({ messages: [...] });
// CORRECT
const config = { configurable: { thread_id: "session-1" } };
await agent.invoke({ messages: [...] }, config);
// Resume with Command using same config
await agent.invoke(new Command({ resume: { decisions: [{ type: "approve" }] } }), config);</typescript>
</fix-thread-id-required-for-resumption><fix-interrupt-checks-between-invocations>
<python>
Interrupts happen BETWEEN invoke() calls, not mid-execution.result = agent.invoke({...}, config=config) # Step 1: triggers interrupt
if "__interrupt__" in result: # Step 2: check for interrupt
result = agent.invoke( # Step 3: resume
Command(resume={"decisions": [{"type": "approve"}]}),
config=config,
)</python>
</fix-interrupt-checks-between-invocations>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.

