error-analysis

Analyze LLM execution traces to categorize failures and generate an error taxonomy.

226|55|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Miosa-osa/canopy --skill error-analysis-miosa-osa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: error-analysis
Source: https://github.com/Miosa-osa/canopy/tree/main/library/skills/analysis/error-analysis
Command: npx skills add https://github.com/Miosa-osa/canopy --skill error-analysis-miosa-osa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides through systematic analysis of LLM execution traces to categorize failure modes, detect recurring patterns, and produce an actionable taxonomy with prioritized fixes.

Core Features & Use Cases

  • Ingest traces from eval results, agent logs, or production runs.
  • Classify failures into common categories such as reasoning errors, factual errors, format violations, and tool misuse.
  • Detect recurring patterns across runs and quantify frequency.
  • Produce a prioritized recommendations report with root-cause hypotheses.

Quick Start

Analyze traces in a directory to generate an error taxonomy and prioritized improvement recommendations.

Frequently Asked Questions about error-analysis

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

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

You can analyze LLM traces by ingesting eval JSON, agent logs, or JSONL production runs to automatically classify failures into reasoning errors, factual errors, format violations, and tool misuse. The system parses these trace formats to detect recurring patterns and quantify their frequency across runs.

What is error taxonomy and how does it help debug agent logs?

Error taxonomy is a structured classification of LLM execution failures that groups similar issues like reasoning errors or tool misuse. Applied to agent logs, it identifies recurring failure patterns and generates root-cause hypotheses to guide systematic debugging and model improvements.

Can I generate a root-cause analysis report from eval JSON files?

Yes, you can ingest eval JSON files to automatically generate an error taxonomy and root-cause hypotheses. The analysis produces a structured report with prioritized recommendations for fixing the identified failure modes across your evaluation runs.

Does this approach work with production JSONL logs or only evaluation results?

This approach works with production JSONL logs, eval JSON, and agent logs. It parses various trace formats to classify failures and detect recurring patterns, making it suitable for both evaluation results and live production run analysis.

What is the best way to identify tool misuse patterns across LLM runs?

The best way to identify tool misuse is to aggregate execution traces from multiple runs and categorize failures automatically. This detects recurring tool misuse patterns, quantifies their frequency, and outputs root-cause hypotheses within a prioritized recommendations report.