CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

antithesis-triage

Triage Antithesis test reports to understand what happened in a run: look up runs, check status, investigate failed properties (assertions), view metadata, download logs, search events across all timelines, inspect findings, and examine environmental details. Load after a run completes, to follow a live run, or when investigating a failure.

Quality

89%

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

85%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 well-structured operational skill: concrete snouty commands, gated preflight validation, branching workflows with feedback loops, and exemplary progressive disclosure into a verified one-level reference bundle. Its only weaknesses are mild verbosity in the follow-up-skills section and a handful of inherently open-ended analysis steps.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence — no explanations of concepts Claude already knows, and dense operational prose throughout. Minor trimming is possible: the five-skill "Suggesting follow-up skills" section (including the long mutation-testing gating conditions) and the duplicated version/compatibility details push it past lean, matching anchor 4's "minor instances of over-explanation that could be trimmed" rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Concrete, executable commands appear throughout ("snouty doctor --json", "snouty runs --json properties", "snouty runs --json show ${RUN_ID}", "snouty runs --json build-logs ${RUN_ID}", "snouty runs show <RUN_ID> --web") plus a jq pipeline example and explicit decision rules for edge cases. A few steps remain open-ended ("Analyze the downloaded log locally", "Deeply investigate the failure") with execution detail deferred to reference files, so it is mostly-executable anchor 4 rather than fully copy-paste-ready anchor 5.

4 / 5

Workflow Clarity

Each workflow is a numbered sequence with explicit validation checkpoints and error recovery: the preflight gates ("Proceed only when the top-level `ok` is `true`"), the DO-NOT-PROCEED prerequisites, conditional branches (triage_report null → fetch properties anyway; 404 → report and stop), the retry loop of downloading more counterexample and passing logs when uncertain, and a closing Self-Review checklist. This matches anchor 5's explicit validation, feedback loops, and checklists; the workflows are read-only triage so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

SKILL.md is a clear overview that explicitly instructs "Do NOT read them all up front — only read a reference file when you are told to" and names each of the six reference files at the point of need; all six exist in references/ (verified) and are one level deep with bulk detail (e.g., the 17KB logs guide) appropriately split out. The only cross-links are two clearly signaled sibling pointers inside properties.md, which do not bury content, so this matches anchor 5 rather than the minor-gaps anchor 4.

5 / 5

Total

18

/

20

Passed

Description

88%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 strong description that clearly states what the skill does through a comprehensive list of concrete triage actions and gives an explicit three-trigger "when" clause. Its only weaknesses are a few missing natural trigger phrases and slight overlap with sibling Antithesis skills on the generic "investigating a failure" trigger.

DimensionReasoningScore

Specificity

The description lists eight concrete actions ("look up runs, check status, investigate failed properties (assertions), view metadata, download logs, search events across all timelines, inspect findings, and examine environmental details") — comprehensive, specific coverage of the triage domain, matching the anchor for multiple specific concrete actions rather than the anchor-4 case of minor gaps.

5 / 5

Completeness

It explicitly answers both questions: the "what" is the enumerated action list, and the "when" is a concrete trigger clause — "Load after a run completes, to follow a live run, or when investigating a failure." This matches the anchor-5 example structure of clear what AND when with concrete trigger phrases, not the merely adequate anchor-4 case.

5 / 5

Trigger Term Quality

Good natural keyword coverage — "run", "failure", "failed properties", "assertions", "logs", "live run", "status", "test reports" — including the "assertions" synonym for properties. A few natural phrases users might say are missing (e.g., "root cause", "debug the run"), so it fits anchor 4 rather than the comprehensive synonym-plus-extension coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Triage Antithesis test reports" carves out a clear, tool-specific niche with run-centric triggers, so it is mostly distinct. However, "when investigating a failure" is a trigger shared with the closely related antithesis-debug skill described in the body, giving minor overlap risk with a closely related skill — anchor 4 rather than anchor 5's minimal conflict risk.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

antithesishq/antithesis-skills

Path

antithesis-triage/SKILL.md

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.