CtrlK
BlogDocsLog inGet started
Tessl Logo

triage-agent-eval-failures

Triage failing @novu/agent-evals scenarios to decide whether a failure is real or flaky, and whether to fix the playbook/prompt or the test (grader, tape, scenario, or judge). Use when an agent-evals scenario fails, when the user asks why an eval is red, or when deciding whether to fix the test or the prompt.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, highly actionable triage workflow with explicit validation checkpoints and concrete commands. The only notable weakness is a dangling reference.md link with no corresponding bundle file.

Suggestions

Add the referenced reference.md to ./references/ (or remove the link) so the worked-examples pointer resolves.

Tighten a few explanatory sentences (e.g. the 'one red run is one sample' rationale) to lift conciseness toward 5.

Consider moving the grader-location table into reference.md to keep SKILL.md as a pure overview, improving progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly efficient and operational — no conceptual padding about what evals or graders are — with a few spots ('Scenarios run a live model concurrently, so one red run is one sample') that could be trimmed further.

4 / 5

Actionability

Provides copy-paste-ready commands (pnpm --filter @novu/agent-evals exec vitest run ...), a location table mapping each layer to a file, and concrete RunResult fields to inspect — fully executable guidance covering the common triage cases.

5 / 5

Workflow Clarity

Clear top-down sequence (Rule 0 → Step 4) with explicit validation checkpoints (re-run 3–5×, confirm fix across re-runs, run synthetic unit tests) and a feedback loop, fully meeting the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

Well-organized into clear sections with a single clearly-signaled one-level reference to reference.md; the gap is that reference.md is referenced but not present in any bundle directory, a minor navigation flaw.

4 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A tight, third-person description that names concrete actions and pairs them with multiple natural trigger phrases, clearly distinguishing the skill's narrow eval-triage niche. Only minor: trigger coverage could add a few more lay synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — triage failures, decide real vs flaky, and route the fix to a specific component (playbook/prompt vs grader/tape/scenario/judge) — with comprehensive coverage of the triage decision space.

5 / 5

Completeness

Explicitly answers both what ('triage failing scenarios to decide whether a failure is real or flaky...') and when ('Use when an agent-evals scenario fails, when the user asks why an eval is red...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural user phrases ('scenario fails', 'why an eval is red', 'deciding whether to fix the test or the prompt'); a few lay synonyms are missing and the '@novu/agent-evals' framing leans slightly technical.

4 / 5

Distinctiveness Conflict Risk

Targets a very specific niche (failing @novu/agent-evals scenarios) with distinct triggers, making overlap with unrelated skills minimal.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
novuhq/novu
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.