analyzing-mlflow-trace

Analyzes a single MLflow trace to debug errors and root-cause agent behavior.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/FMurray/mlfts --skill analyzing-mlflow-trace-fmurray
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyzing-mlflow-trace
Source: https://github.com/FMurray/mlfts/tree/main/.agents/skills/analyze-mlflow-trace
Command: npx skills add https://github.com/FMurray/mlfts --skill analyzing-mlflow-trace-fmurray

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When an AI agent or LLM application produces a wrong answer or fails, raw MLflow traces are large and hard to interpret. This Skill guides the investigation of a single trace by ID, turning span trees, assessments, and status codes into a concrete root-cause diagnosis. ## Core Features & Use Cases - Trace Health Check: Fetches the full trace via the MLflow CLI and summarizes state, span count, error spans, and assessment errors with jq queries. - Assessment Interpretation: Explains feedback values using the rationale field, distinguishing scorer failures from genuine trace problems. - Codebase Correlation: Maps span names to functions in the source code so issues can be root-caused beyond what the trace alone shows. - Use Case: A user provides a trace ID and asks why a support agent answered a refund question with shipping policy text; the Skill walks through the span tree, identifies the retrieval tool returned the wrong document, and recommends re-indexing the knowledge base. ## Quick Start Ask the assistant to analyze MLflow trace with a given trace ID and explain what went wrong.

Frequently Asked Questions about analyzing-mlflow-trace

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

FAQPage Schema
How do I analyze an MLflow trace to find errors?

Fetch the full trace with mlflow traces get --trace-id and redirect output to a file, then use jq to inspect .info.state, error spans, and assessments. Check span status codes and assessment rationale to locate where execution diverged.

How to debug an AI agent using MLflow tracing spans?

Examine the span tree, which mirrors the application's call stack, and compare span inputs and outputs against expected behavior. Correlate span names with functions in the source code to root-cause issues beyond what the trace shows.

Does an MLflow trace state of OK mean the output is correct?

No, state OK only means no unhandled exception occurred during execution. You must check assessments for quality signals or analyze span inputs and outputs directly to verify the response is actually correct.

Why does mlflow traces get produce no output when piped to jq?

Piping mlflow traces get directly to jq or head can silently produce no output for large traces. Always redirect the CLI output to a file first, then run jq queries against that file.

What does an error on an MLflow trace assessment mean?

An assessment error means the scorer or judge evaluating the trace failed, not that the trace itself has a problem. This happens when a scorer crashes or is applied to a trace type it was not designed for.