What problem does it solve?
When an @novu/agent-evals scenario goes red, it is unclear whether the playbook under test regressed, the test scaffolding (grader, tape, scenario, judge) is broken, or the failure is just model non-determinism. This Skill provides a structured triage workflow to reach the correct verdict without fixing the wrong layer.
Core Features & Use Cases
- Flakiness screening: Re-run the failing scenario 3-5 times with vitest before changing anything, separating deterministic failures from flaky ones.
- Grader classification: Identify whether the failing grader is deterministic (catalog, contains, matches) or an LLM judge, and map it to the RunResult fields it inspects.
- Verdict-driven fixes: Apply one bounded fix to either the playbook (agent-onboarding.md) or the test layer (catalog.ts, scenario.ts, judge prompts), never both, then verify across re-runs.
- Use Case: A CI run shows the dashboard-prompt-login scenario failing on the readAuthUrlFile grader. Use this Skill to inspect the RunResult evidence, discover the agent behaved correctly but the grader's path check is too narrow, and fix catalog.ts instead of the playbook.
Quick Start
Ask the agent to triage why the agent-evals scenario dashboard-prompt-login is failing and decide whether to fix the playbook or the test.