llm-observability-stack
Skill1 starsChanged 6 months agoMITView on GitHub
Meta-skill for building a complete LLM application stack using LangChain + LangGraph + Langfuse. Use when asked to: integrate langchain langgraph langfuse, setup full LLM stack, build LLM app with observability, end-to-end LLM pipeline with tracing, production LLM stack, connect langchain with langgraph and langfuse, fullstack LLM observability, or setup RAG agent with monitoring.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- build-with-ai-hq/llm-observability-stacktheir own version, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- build-with-ai-hq/llm-observability-stack★ 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 repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- academic-evaluationSkill
- academic-writingSkill
- agent-orchestrationSkill
- agents-md-writerSkill
- algorithmic-artSkill
- brand-guidelinesSkill
- codebase-architectureSkill
- code-reviewSkill
- commit-workflowSkill
- context-checkpointSkill
- doc-coauthoringSkill
- docxSkill
- etl-runnerSkill
- eval-runnerSkill
- feature-devSkill
- frontend-designSkill
- hpc-deucalionSkill
- internal-commsSkill
- langchainSkill
- langfuseSkill
- langgraphSkill
- mcp-builderSkill
- neo4j-verifySkill
- pdfSkill
- pptxSkill
- project-conventionsSkill
- python-best-practicesSkill
- react-namingSkill
- security-hooksSkill
- service-verifySkill
- skill-creatorSkill
- skill-inspectorSkill
- slack-gif-creatorSkill
- sprint-contractSkill
- theme-factorySkill
- uml-modelingSkill
- webapp-testingSkill
- web-artifacts-builderSkill
- web-debugSkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 31
When to use each component in the stack
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
LLM Observability Stack
Complete integration of LangChain, LangGraph, and Langfuse for production-ready LLM applications with full observability.
When to Use
- "integrate langchain langgraph langfuse"
- "setup full LLM stack"
- "build LLM app with observability"
- "end-to-end LLM pipeline with tracing"
- "production LLM stack"
- "connect langchain with langgraph and langfuse"
- "fullstack LLM observability"
- "setup RAG agent with monitoring"
What It Covers
- Architecture overview (LangChain + LangGraph + Langfuse)
- How the three components connect
- Data flow: user input -> LangGraph workflow -> LangChain chains/tools -> Langfuse tracing
- When to use each component in the stack
- Project structure recommendation
- Directory layout for maintainable code
- Separation of concerns: chains, graphs, tools, observability config
- Setup all 3 components together
- Combined dependency management
- Environment configuration
- Initialization order
- Integrate LangChain with LangGraph
- Using LangChain chains inside LangGraph nodes
- Passing state between LangChain operations
- Tool binding in graph workflows
- Add Langfuse observability to the stack
- Single Langfuse callback for the entire pipeline
- Tracing across LangGraph state transitions
- Cost and latency tracking end-to-end
- Best practices for production
- Error handling and fallback strategies
- Async execution patterns
- Resource cleanup and connection management
Architecture
User Input
|
v
+---------------+
| LangGraph | <-- State management, workflow orchestration
| (Graph) | Conditional edges, loops, branching
+---------------+
|
v
+---------------+
| LangChain | <-- Chains, RAG, tools, LLM calls
| (Chains) | Prompts, retrievers, output parsers
+---------------+
|
v
+---------------+
| Langfuse | <-- Tracing, monitoring, evaluation
| (Observability)| Spans, generations, scores, datasets
+---------------+Component Responsibilities
| Component | Role | Example |
| LangChain | Build chains, RAG, tools | retrieval_chain, agent_executor |
| LangGraph | Orchestrate workflow with state | StateGraph with conditional routing |
| Langfuse | Trace and monitor everything | Callback handler, manual traces |
Integration Points
- LangChain + LangGraph: LangChain chains/tools are used as node functions in LangGraph
- LangChain + Langfuse: Langfuse callback handler automatically traces all LangChain operations
- LangGraph + Langfuse: Langfuse traces the full graph execution including state transitions
- Full Stack: One Langfuse callback traces the entire pipeline from graph entry to final output
Templates
| Template | Purpose |
SKILL.md | This skill definition |
Examples
| Example | Purpose |
examples/complete-integration.py | Full project using all 3 tools together |
examples/project-structure.md | Recommended directory structure |
References
references/integration-patterns.md— Common integration patterns and anti-patterns../langchain/SKILL.md— LangChain individual skill (chains, RAG, tools)../langgraph/SKILL.md— LangGraph individual skill (state graphs, agents)../langfuse/SKILL.md— Langfuse individual skill (tracing, monitoring, evaluation)
Resources
Use When
The user wants to build a complete, production-ready LLM application using LangChain for chains/RAG, LangGraph for workflow orchestration, and Langfuse for observability. This is the go-to skill for full-stack LLM development with monitoring.
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.

