CtrlK
BlogDocsLog inGet started
Tessl Logo

detect-zero-iteration-failures

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

57

Quality

64%

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

Fix and improve this skill with Tessl

tessl review fix ./benchmarks/gdpval/skills/detect-zero-iteration-failures/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The skill is well-structured and actionable with executable code and clear sectioning, but it repeats its core premise and lacks explicit validation checkpoints in its diagnostic workflow.

Suggestions

Collapse the redundant 'When to Apply', 'Identification Checklist', and 'Key Takeaways' sections into a single concise statement of indicators to reduce repetition.

Add an explicit verification checkpoint in the diagnostic steps (e.g. confirm all zero-iteration indicators hold before categorizing as PRE_EXECUTION_FAILURE).

Document or define the expected execution_log dict shape so the provided functions are fully self-contained.

DimensionReasoningScore

Conciseness

The core premise is restated three times across 'When to Apply', the 'Identification Checklist', and 'Key Takeaways', so while mostly efficient the body could be tightened, matching 'mostly efficient but includes some unnecessary explanation'.

2 / 3

Actionability

Provides executable Python functions (is_zero_iteration_failure, categorize_failure), a concrete checklist, and a routing decision tree that are copy-paste ready, matching the 'fully executable code/commands' anchor.

3 / 3

Workflow Clarity

Diagnostic steps are clearly numbered (Step 1-3) but lack explicit validation checkpoints or feedback loops, fitting 'steps listed but validation gaps; checkpoints missing or implicit' rather than the level-3 anchor requiring validation steps.

2 / 3

Progressive Disclosure

The body is well-organized into clearly labeled sections with no nested or deep references and no bundle files to navigate, so section headers provide clear navigation matching the well-organized level-3 case for a self-contained skill.

3 / 3

Total

10

/

12

Passed

Description

57%

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 conveys a clear, distinctive niche but relies on technical phrasing and omits an explicit 'Use when' trigger clause, leaving it efficient yet incomplete as activation guidance.

Suggestions

Add an explicit trigger clause, e.g. 'Use when analyzing agent runs that completed zero iterations with no tool usage or output.'

Replace the vague 'handle' with concrete actions like 'categorize and route' to lift specificity.

Include more natural user-facing terms (e.g. 'agent did nothing', 'failed before starting') alongside the technical jargon.

DimensionReasoningScore

Specificity

Names the domain and the concrete actions 'Identify and handle pre-execution agent failures', but 'handle' is vague and the action set is not comprehensive, fitting the 'names domain and some actions' anchor rather than the multi-action level 3.

2 / 3

Completeness

It states what the skill does but lacks an explicit 'Use when...' trigger clause; per the judging guidelines a missing explicit trigger caps completeness at 2, and it is not the level-1 case because the 'what' is clearly present.

2 / 3

Trigger Term Quality

Terms like 'pre-execution agent failures', 'iterations', and 'tool usage' are domain-relevant but lean technical; they miss the natural phrasings a user might actually say, so this matches 'some relevant keywords but missing common variations' rather than the jargon-only level 1.

2 / 3

Distinctiveness Conflict Risk

The narrow framing 'pre-execution agent failures occurring before any iterations or tool usage' carves out a clear, distinct diagnostic niche unlikely to trigger for unrelated skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

9

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
HKUDS/OpenSpace
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.