What problem does it solve?
When a skill evaluation in the dotnet/skills repository returns a regression, an underpowered verdict, a timeout, or "no credible improvement", the most common mistake is rewriting skill prose when the real cause is the eval spec, the fixtures, or the harness. This Skill enforces a classify-first workflow so you fix the actual root cause instead of editing content blindly.
Core Features & Use Cases
- Failure classification: A symptom-to-cause table routes verdicts to the right fix path — fixture defects, harness/reliability failures, statistical power limits, eval design flaws, skill content, or activation/routing problems.
- Statistical power analysis: Explains the two-bar gate (≥5 distinct stimuli and p ≤ 0.05 sign test over discordant votes) so you know when to add discriminating stimuli instead of padding runs.
- Content and activation fixes: Reference guides cover writing skill content that beats the unskilled baseline and repairing frontmatter descriptions that fail to route.
- Use Case: A PR's
/evaluate comment reports 16W/8T/1L but the verdict fails. Use this Skill to determine the ties made a pass statistically unreachable, then add discriminating stimuli rather than rewriting the skill.
Quick Start
Ask the agent to diagnose why the latest /evaluate run for your skill reported a regression and recommend the correct fix.