agentleFS
pauloribeiro16pauloribeiro16/my-skills/llm-observability-stack/SKILL.md

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

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
  1. Distinctive:

    When to use each component in the stack

    line 31

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. 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
  2. Project structure recommendation
    • Directory layout for maintainable code
    • Separation of concerns: chains, graphs, tools, observability config
  3. Setup all 3 components together
    • Combined dependency management
    • Environment configuration
    • Initialization order
  4. Integrate LangChain with LangGraph
    • Using LangChain chains inside LangGraph nodes
    • Passing state between LangChain operations
    • Tool binding in graph workflows
  5. 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
  6. 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

ComponentRoleExample
LangChainBuild chains, RAG, toolsretrieval_chain, agent_executor
LangGraphOrchestrate workflow with stateStateGraph with conditional routing
LangfuseTrace and monitor everythingCallback handler, manual traces

Integration Points

  1. LangChain + LangGraph: LangChain chains/tools are used as node functions in LangGraph
  2. LangChain + Langfuse: Langfuse callback handler automatically traces all LangChain operations
  3. LangGraph + Langfuse: Langfuse traces the full graph execution including state transitions
  4. Full Stack: One Langfuse callback traces the entire pipeline from graph entry to final output

Templates

TemplatePurpose
SKILL.mdThis skill definition

Examples

ExamplePurpose
examples/complete-integration.pyFull project using all 3 tools together
examples/project-structure.mdRecommended 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.