langfuse-reviewer

Review Langfuse traces, observations, scores, and metrics to debug yuno.md issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Xuno-io/yuno-md --skill langfuse-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: langfuse-reviewer
Source: https://github.com/Xuno-io/yuno-md/tree/main/skill/langfuse-reviewer
Command: npx skills add https://github.com/Xuno-io/yuno-md --skill langfuse-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers and operators debug issues within the yuno.md application by providing direct access to Langfuse traces, observations, scores, and metrics.

Core Features & Use Cases

  • Full Observability: Access and analyze production traces, observations, sessions, and scores directly.
  • Debugging Workflows: Provides specific curl command examples for common debugging scenarios like investigating user issues, finding errors, and analyzing costs/latency.
  • Prompt Management: Integrates with MCP tools to manage and review Langfuse prompts.
  • Use Case: If a user reports an unexpected behavior in yuno.md, you can use this Skill to quickly find their session in Langfuse, examine the associated trace, and pinpoint the exact observation or LLM call that led to the issue.

Quick Start

Use the langfuse reviewer skill to find recent traces for the user with telegram ID 12345.

Frequently Asked Questions about langfuse-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug Langfuse traces to investigate user issues?

Debug Langfuse traces by reviewing observations, scores, and metrics to investigate user issues. Combine MCP tools with REST API calls to access traces, sessions, and metrics for comprehensive observability and pinpoint exact LLM calls causing errors.

What is LLM observability and how does trace review help error identification?

LLM observability provides visibility into application behavior through trace review. Analyzing trace observations and metrics helps with error identification by exposing the exact LLM calls and prompt executions that led to unexpected application behavior.

How do I analyze latency and cost using Langfuse metrics?

Analyze latency and cost using Langfuse metrics by executing REST API calls to retrieve production trace data. Review specific observations and scores to isolate expensive or slow LLM calls within your application sessions.

Can I review and manage Langfuse prompts during debugging workflows?

You can review and manage Langfuse prompts during debugging workflows by integrating MCP tools. This allows you to access documentation, manage prompts, and review prompt executions alongside trace observations to resolve issues.

What is the best way to find a specific user session in Langfuse traces?

The best way to find a specific user session in Langfuse traces is by using REST API calls with user identifiers, such as a telegram ID. This retrieves associated sessions, traces, and observations to debug reported issues.

Do I need MCP tools to access Langfuse observations and metrics?

You need MCP tools to access Langfuse prompts and documentation, while REST API calls handle traces, observations, sessions, and metrics. Combining both provides comprehensive observability for debugging latency, cost, and error issues.