upgrade-evals

Analyze LLM pipeline traces to categorize failures and prioritize root causes.

16|3|Updated Oct 23, 2025
One-click install
npx skills add https://github.com/breethomas/bette-think --skill upgrade-evals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrade-evals
Source: https://github.com/breethomas/bette-think/tree/main/plugins/pm-thought-partner/skills/upgrade-evals
Command: npx skills add https://github.com/breethomas/bette-think --skill upgrade-evals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help product managers and engineers discover, quantify, and prioritize real failure modes in AI features by analyzing actual pipeline traces rather than relying on intuition or pre-defined categories.

Core Features & Use Cases

  • Trace collection guidance: sampling strategies for diverse and representative traces from production or staged systems.
  • Pass/fail labeling and note-taking: structured instructions for binary judgments and concise observations that surface root causes.
  • Grouping, labeling, and prioritization: iterative clustering into actionable failure categories, computing failure rates, and recommending fixes or evaluators.
  • Use Case: A PM uses ~100 real user traces to surface top failure categories, then directs engineers to fix prompt issues, add validators, or build evaluators.

Quick Start

Ask the skill to analyze recent production traces, label pass/fail, surface emergent failure categories, and recommend the highest-impact fixes.

Frequently Asked Questions about upgrade-evals

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

FAQPage Schema
How do I analyze LLM pipeline traces to identify failure modes?

To find AI failures, perform systematic error analysis on LLM pipeline traces by sampling dozens to hundreds of traces, labeling pass/fail, clustering into failure categories, and prioritizing root causes. This replaces intuition with quantified failure rates.

What's the best way to categorize and prioritize errors in AI features?

Categorize and prioritize AI errors by iteratively clustering labeled pipeline traces into actionable failure categories, computing failure rates per category, and recommending fixes or evaluators based on impact. This requires a PM to judge pass/fail outcomes.

How many production traces do I need for LLM error analysis?

You need dozens to hundreds of production or staging traces for effective LLM error analysis. This scale ensures representative sampling for accurate pass/fail labeling, meaningful failure clustering, and reliable root-cause prioritization.

Do I need tooling to aggregate labels when analyzing LLM traces?

Yes, you need tooling to aggregate labels and compute failure rates, plus a PM to judge pass/fail. Access to inputs, intermediate tool calls, and outputs is also required to perform root-cause prioritization on LLM pipeline traces.

When should I use systematic trace analysis instead of predefined failure categories?

Use systematic trace analysis instead of predefined categories when you need to discover emergent failure modes in AI features. It helps product managers and engineers quantify real issues from actual pipeline traces and direct fixes accurately.