langgraph-orchestration
Skill2 starsChanged 4 months agoMITView on GitHub
Build or modify LangGraph StateGraph agents in vpeetla-ai repos: typed state, nodes, conditional edges, MemorySaver, interrupt_before HITL. Use when adding orchestrators, coding loops, or multi-agent graphs.
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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 19
Use TypedDict with total=False for optional fields
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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
LangGraph Orchestration
Standard pattern
START → observe/plan → specialist nodes → evaluate → route (retry|pass|hitl) → ENDState
- Use
TypedDictwithtotal=Falsefor optional fields - Accumulate
trace_eventsexplicitly (list replacement per node unless using reducer) - Set
max_iterationsin state; enforce in routing
Nodes
- Async wrappers:
async def n_x(state): return sync_node(state, deps) - One responsibility per node (orchestrate, act, review, quality)
- Return partial state updates only
Routing
builder.add_conditional_edges("quality", route_fn, {"retry": "plan", "pass": "ship", "escalate": "hitl"})- Security failures → escalate/HITL
- Max iterations → escalate, never infinite loop
HITL
graph.compile(checkpointer=MemorySaver(), interrupt_before=["hitl"])Resume with graph.ainvoke(update, config) after human approval.
Reference implementations
loop-engine-agent-platform/src/loop_engine/graph/build.pyloop-engine-agent-platform/src/loop_engine/graph/repo_build.py- venkat-ai-platform orchestrators
Tests
- Mock LLM for deterministic paths
pytest.mark.asyncio+tmp_pathfor filesystem side effects
Other versions5 projects use a version of this.
Word for word · 4
- vpeetla-ai/aegisai-enterprise-agent-platform★ 2100% same
- vpeetla-ai/multi-agent-system-pattern★ 2100% same
- vpeetla-ai/reflection-agent-pattern★ 2100% same
- vpeetla-ai/swarm-agent-pattern★ 2100% same
Edited · 0
None found.
Wrote their own version · 1
- HermeticOrmus/ormus-meta-prompting★ 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.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- aegis-gatewaySkill
- agentic-engineeringSkill
- deploy-vercel-renderSkill
- governed-ai-stackSkill
- grill-with-contextSkill
- hitl-side-effectsSkill
- loop-engineeringSkill
- portfolio-adrSkill
- rag-governanceSkill
- repo-fix-prSkill
- setup-vpeetla-skillsSkill
- tdd-agent-loopsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.