detect-zero-iteration-failure

Identify and classify agent failures occurring before execution starts

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/detect-zero-iteration-failure/SKILL.md

Quality

Content

86%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.

The content is a well-structured, concise diagnostic workflow with concrete, actionable guidance and clear sequencing. Its main limitation is the absence of explicit validate-then-act feedback checkpoints in the workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean with tight numbered criteria and no padding or explanation of concepts Claude already knows; every section earns its place, matching the score-5 anchor.	5 / 5
Actionability	It provides concrete guidance (specific labels like 'failure_mode: pre_execution', explicit checks, routing, and retry reset instructions) with only minor gaps, matching score 4; it stops short of fully copy-paste-ready artifacts inherent to a diagnostic skill.	4 / 5
Workflow Clarity	The identify-diagnose-act sequence is clearly laid out with a gated all-conditions-met decision, but validation/checkpoint feedback loops are implicit rather than explicit, matching score 4.	4 / 5
Progressive Disclosure	As a simple, under-50-line single-purpose skill with no bundle files and well-organized sections (Identification Criteria, Diagnosis Strategy, Action Plan, Example Indicators), it qualifies for score 5 under the simple-skills exception.	5 / 5
	Total	18 / 20 Passed

Description

42%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.

The description clearly states what the skill does but lacks trigger guidance and natural keywords, making it generic enough to risk overlap with other debugging skills. Adding a 'Use when...' clause with concrete trigger phrases would substantially raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases a user would say (e.g., 'agent ran 0 iterations', 'session failed before first step', 'no tools were called').

Expand the action list beyond 'Identify and classify' to specify outputs (e.g., tag the failure mode, route to infrastructure).

Include natural synonyms and concrete indicators to improve trigger-term coverage and reduce overlap with general agent-debugging skills.

Dimension	Reasoning	Score
Specificity	The description names the domain ('agent failures occurring before execution starts') and two concrete actions ('Identify', 'classify'), but does not enumerate several specific actions, matching the score-3 anchor.	3 / 5
Completeness	It gives a clear 'what' (identify and classify pre-execution agent failures) but omits any 'when'/'Use when...' guidance, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	It relies on technical phrasing ('agent failures', 'before execution starts') with essentially no natural user-facing trigger keywords, synonyms, or file extensions, fitting between score 1 and 3 and leaning toward 2.	2 / 5
Distinctiveness Conflict Risk	The niche (pre-execution failures) is somewhat specific, but without concrete distinct triggers it could overlap with general agent-debugging skills, matching the score-3 anchor.	3 / 5
	Total	11 / 20 Passed

Validation

100%

Warnings & errors only

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: HKUDS/OpenSpace
Path: benchmarks/gdpval/skills/detect-zero-iteration-failure/SKILL.md
Commit: 3827781

Reviewed: 21 days ago

Table of Contents

Discovery Implementation Validation

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.