Individual skill
analyze-exports
Analyze tau2-bench task export files to identify exactly where and why tasks failed. Map failures to specific conversation rounds, show root causes, check whether relevant documentation was available, and cite sources. Use this skill whenever you need to debug a tau2-bench evaluation, understand why an agent made wrong decisions, identify missing knowledge, or review task performance—especially when context length, eligibility criteria, or policy compliance might be at fault.
skills/analyze-exports/SKILL.md
Source commit 7a708ce17d05bd390da88b2350f4b794d9427f18
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Local scripts
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,124
- Repository last updated
- Oct 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,322 bytesSKILL.mdcore · 10,322 bytesreferences/common_failures.mddoc · 10,473 bytesreferences/export_format.mddoc · 11,599 bytesscripts/analyze_failures.pyruns · 9,576 bytesscripts/parse_export.pyruns · 6,708 bytes
Read excerpt
# Analyze Exports Skill
## Purpose
When a tau2-bench task returns reward 0.0 (or fails), the export file contains everything you need to understand why—but it's buried in tool-call summaries and conversation transcripts. This skill systematically analyzes the export to show:
1. **Where it failed** — the exact round (Assistant #X, User #Y) and tool-call sequence
2. **What should have happened** — ground truth from the task explanation
3. **Why it failed** — root cause (missing logic, wrong arguments, bad order, policy misunderstanding)
4. **Was the docs available?** — whether the KB had the answer the agent needed
5. **Evidence** — quotes and citations from both the transcript and source documents
## Input Format
