Agent skill

Eval Analyzer

Analyze evaluation baseline results, identify failure patterns, and generate actionable insights. Use after running eval baselines or when user asks to analyze eval results, check benchmarks, investigate failures, or understand what's failing.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill eval-analyzer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 13 KB
Bundled scripts: none
Path: skills/analysis/eval-analyzer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Eval Analyzer Analyze AILANG evaluation baseline results to identify failure patterns, compare model performance, and generate actionable insights. ## Quick Start **Most common usage:** ```bash # User says: "Analyze the v0.3.24 eval results" # This skill will: # 1. Run eval-analyze to categorize failures (standard eval) # 2. Run agent KPIs to analyze efficiency (agent eval) # 3. Generate summary with jq queries # 4. Identify top failing benchmarks # 5. Show model performance comparison # 6. Provide optimization recommendations ``` **For agent evaluation analysis** (NEW - optimization focus): ```bash # Step 1: Get efficiency metrics (turns, tokens, cost) .claude/skills/eval-analyzer/scripts/agent_kpis.sh eval_results/baselines/v0.3.24 # Step 2: Investigate expensive benchmarks .claude/skills/eval-analyzer/scripts/agent_transcripts.sh eval_results/baselines/v0.3.24 simple_print # Step 3: Compare Python vs AILANG ./tools/compare_agents.sh eval_results/baselines/v0.3.24 ``` **See [`resources/agent_optimization_guide.md`](resources/agent_optimization_guide.md) for complete optimization strategies.** ## When to Use This Skill Invoke this skill when: - User asks to "analyze eval results

What's inside
Steps it walks through
  1. Quick Start
  2. When to Use This Skill
  3. Key Eval Commands
  4. 1. Quick Overview - eval-matrix
  5. 2. Detailed Analysis - eval-analyze
  6. 3. Query-Friendly Summary - eval-summary
  7. 4. Compare Versions - eval-compare
  8. 5. Fair Comparison (RECOMMENDED) - faircomparison.py
  9. 6. Validate Results - validateevalresults.py
  10. Agent Analysis Scripts (NEW!)
  11. 1. Agent KPIs - Minimize Tokens & Turns
  12. 2. Agent Transcripts - View AILANG Conversations
  13. 3. Python vs AILANG Comparison
  14. Standard Eval Workflow (Non-Agent)
Ships with 1 file
  • metadata.json
Commands it runs
User says: "Analyze the v0.3.24 eval results"
This skill will:
Step 1: Get efficiency metrics (turns, tokens, cost)
Step 2: Investigate expensive benchmarks
Step 3: Compare Python vs AILANG
ailang eval-matrix eval_results/baselines/v0.3.16 0.3.16 | head -60
Dry run (no design docs, just analysis)
ailang eval-analyze -results eval_results/baselines/v0.3.16 -dry-run
Full analysis with design doc generation
ailang eval-analyze -results eval_results/baselines/v0.3.16
More from claude-skill-registry
All skills →
About this skill
What does the Eval Analyzer skill do?

Analyze evaluation baseline results, identify failure patterns, and generate actionable insights. Use after running eval baselines or when user asks to analyze eval results, check benchmarks, investigate failures, or understand what's failing.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill eval-analyzer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going