What problem does it solve? Manually inspecting individual MLflow traces makes it hard to understand aggregate behavior like token consumption, latency trends, error rates, and evaluation quality across experiments. This Skill queries the MLflow tracking server and returns aggregated metrics so you can analyze usage and quality at scale. ## Core Features & Use Cases - Aggregated Metrics: Compute COUNT, SUM, AVG, MIN, MAX, P50, P95, and P99 over trace_count, latency, and token usage metrics. - Time-Bucketed Trends: Group metrics into hourly or daily intervals with flexible start and end time ranges. - Dimensional Breakdowns: Group results by trace name, trace status, or assessment name, including LLM judge evaluation scores via the ASSESSMENTS view. - Use Case: An engineer wants to know how many tokens their coding agent consumed per hour over the last 24 hours and the average correctness score from LLM judges, then exports the results as JSON for a report. ## Quick Start Ask the agent to show the total and average token usage for experiment 1 on your MLflow server, optionally grouped by hour or trace status.