detect-zero-iteration-failures

Identify and handle pre-execution agent failures occurring before any iterations or tool usage

Quality

60%

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-failures/SKILL.md

Quality

Content

75%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 body is well-structured and highly actionable, with executable code and a clear diagnostic workflow. Its main weakness is mild verbosity from redundant summary/restatement sections.

Suggestions

Trim the opening paragraph and 'Key Takeaways' section, which restate content already conveyed by the diagnostic steps and examples.

Consider shortening the 'Normal Execution Failure' contrast example since the categorize_failure() function already encodes the same distinction.

Optionally move the two Python helpers into a scripts/ file and reference them, to reduce inline code in SKILL.md.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but sections like the opening summary, the contrast example, and 'Key Takeaways' restate points already covered elsewhere and could be tightened.	3 / 5
Actionability	Provides two complete executable Python functions, a concrete checklist, a routing flowchart, and a worked example with real log fields — copy-paste ready and covering the common cases.	5 / 5
Workflow Clarity	A clear three-step diagnostic sequence with an implicit gating checklist and audience-specific response actions; no explicit validate-and-retry loop, but the task is non-destructive so that cap does not apply.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections with no nested or broken references (no bundle files exist), though the skill is self-contained at ~150 lines and the Python helpers could optionally live in a scripts/ file.	4 / 5
	Total	16 / 20 Passed

Description

46%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 names a specific niche and clear actions but relies on technical jargon rather than natural trigger phrases and lacks an explicit 'Use when...' clause. It is reasonably distinct but would benefit from more user-facing trigger language.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke the skill, e.g. 'Use when analyzing agent runs that completed zero iterations and invoked no tools.'

Replace jargon with natural trigger phrases users would say, such as 'agent didn't start', 'task never ran', or 'zero iterations'.

Make 'handle' concrete by naming the actual action (e.g. 'categorize and route') instead of the generic verb.

Dimension	Reasoning	Score
Specificity	Names the domain ('pre-execution agent failures') and two actions ('Identify and handle'), but 'handle' is generic and coverage is not comprehensive, matching the 1-2 concrete actions anchor.	3 / 5
Completeness	The 'what' is clear, but 'when' is only weakly implied by the failure description and there is no explicit 'Use when...' clause, which caps completeness at 3 per the guidelines.	3 / 5
Trigger Term Quality	Terms like 'pre-execution agent failures', 'iterations', and 'tool usage' are technical jargon; the natural phrases an analyst would actually say (e.g. 'agent didn't run', 'task never started') are missing.	2 / 5
Distinctiveness Conflict Risk	The zero-iteration pre-execution niche is specific and mostly distinct from general failure analysis, with only minor overlap risk against related debugging skills.	4 / 5
	Total	12 / 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-failures/SKILL.md
Commit: 3827781

Reviewed: 11 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.