Add evaluation troubleshooting guide for AI agents - #441
Conversation
Add InvestigatingResults.md with: - How to find and download evaluation artifacts from workflow runs - Full results.json schema documentation - Common failure patterns (timeouts, empty output, variance, rubric issues, skill not activated) with diagnosis steps and fixes - Example analysis script for AI agents to parse results Link the doc from: - Reporter.cs: show a link in the PR comment when any skill fails - skill-validator README.md: Output section - CONTRIBUTING.md: CI evaluation section Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…docs - Reporter.cs: Use repo-relative link instead of hard-coded GitHub URL - evaluation.yml: Use github.sha instead of hard-coded 'main' branch - InvestigatingResults.md: Clarify skilledPlugin run is optional Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Adds a troubleshooting guide and integrates it into the skill evaluation UX so PR authors (and AI agents) can more easily diagnose evaluation failures by downloading artifacts and interpreting results.json.
Changes:
- Add
eng/skill-validator/InvestigatingResults.mddocumentingresults.json, scoring, and common failure patterns. - Link the guide from
eng/skill-validator/README.mdandCONTRIBUTING.md. - Update evaluation reporting to include a guide link and (on failures) an AI-agent copy/paste investigation prompt in the PR comment.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| eng/skill-validator/src/Evaluate/Reporter.cs | Adds a failure-only note linking to the troubleshooting guide in the generated markdown summary. |
| eng/skill-validator/README.md | Links to the new troubleshooting guide from the Output section. |
| eng/skill-validator/InvestigatingResults.md | New guide explaining artifact retrieval, results.json schema, scoring, and common failure patterns. |
| CONTRIBUTING.md | Links to the troubleshooting guide from the CI evaluation section. |
| .github/workflows/evaluation.yml | Adds an investigation prompt to the consolidated PR comment when failures are detected. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This change is intentionally trivial and will be reverted before merge. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Do not merge yet -- making a temp skill edit so we can try it on this PR |
- Reporter.cs: Remove leading / from relative link - evaluation.yml: Use jq on results.json instead of grepping for emoji - evaluation.yml: Use needs.gate.outputs.head_sha for revision-pinned URL - InvestigatingResults.md: Mark pluginImprovementScore/pluginBreakdown as optional - InvestigatingResults.md: Fix skill-not-activated symptoms to use skillActivation fields instead of turnCount Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
/evaluate |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Use skillActivationIsolated/skillActivationPlugin instead of generic skillActivation - Clarify timestamp is when results were written, not run start Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Skill Validation Results
[1] (Isolated) Quality unchanged but weighted score is -6.6% due to: tokens (24684 → 49262), tool calls (2 → 3)
Model: claude-opus-4.6 | Judge: claude-opus-4.6
|
This reverts commit 83bd7f7.
|
@ViktorHofer or @JanKrivanek can you review? I realized I can't validate much here because it always uses the validator that's in main. I think we have to review and merge this and iterate if we need to. If this works I expect it will make PR's materially more actionable. I want to drain our PR backlog. |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
/evaluate |
Skill Validation Results
[1] (Isolated) Quality unchanged but weighted score is -18.2% due to: judgment, tokens (24225 → 49401), tool calls (2 → 3)
Model: claude-opus-4.6 | Judge: claude-opus-4.6
|
Add evaluation troubleshooting guide for AI agents
Note
This PR was generated with Copilot assistance.
Replaces #440 (moved from fork to upstream branch so CI runs with correct permissions).
Problem
When skill evaluation produces failures, PR authors have no clear path to diagnose the cause. The eval results table shows scores and verdicts, but doesn't explain what went wrong or how to fix it. Investigating requires manually downloading artifacts from workflow logs, reverse-engineering the
results.jsonschema, and pattern-matching against undocumented failure modes.Solution
Add
eng/skill-validator/InvestigatingResults.md— a troubleshooting guide designed primarily for AI coding agents to read and follow. When any skill fails evaluation, the PR comment now includes a ready-to-use prompt that the PR author can copy-paste to their AI agent. The agent downloads the artifacts, reads the guide, analyzes the results, and suggests fixes.What's in the guide
results.jsonschema documentation — verdict, scenario, breakdown, and run metrics fields with descriptionsgh run downloadinstructions for artifact retrievalChanges
eng/skill-validator/InvestigatingResults.mdeng/skill-validator/README.mdCONTRIBUTING.mdeng/skill-validator/src/Evaluate/Reporter.cs.github/workflows/evaluation.ymlValidation
Tested the guide by launching 4 fresh AI agents (clean context, no prior analysis) against eval artifacts from 2 different PRs (PR #317 and PR #428). Across 19 failing scenarios: