CtrlK
BlogDocsLog inGet started
Tessl Logo

zero-iteration-failure-analysis

Identify and handle agent failures with 0 iterations as pre-execution system issues

54

Quality

60%

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/zero-iteration-failure-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 actionable with executable code, clear templates, and a sequenced investigation workflow, but it repeats the core diagnostic criteria across multiple formats and is fully monolithic with no progressive disclosure of supporting detail into references.

Suggestions

Consolidate the repeated zero-iteration criteria (bullet list, checklist, Python function, table row, example) into a single canonical definition referenced by the other sections to reduce redundancy.

Move the supporting Example Analysis, Common Causes table, and YAML/JSON templates into a reference file linked from the main workflow to add progressive disclosure.

Add an explicit verification checkpoint confirming the classification before escalating (e.g., re-check iteration/tool counts against the log) to strengthen the workflow feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly efficient and does not explain concepts Claude already knows, but restates the zero-iteration criteria in four+ formats (bullet list, checkbox list, the is_zero_iteration_failure Python function, a table row, and the example block), which could be tightened; fits score 3 rather than 4 because the redundancy is more than minor, and not 2 because it avoids padded conceptual explanation.

3 / 5

Actionability

Provides an executable is_zero_iteration_failure function plus concrete YAML and JSON templates and a cause/symptom/resolution table, matching score 4's mostly executable guidance with minor gaps; not 5 because the resolution column ('Restart environment, check dependencies') is high-level rather than copy-paste commands, not 3 because real executable code is present rather than pseudocode.

4 / 5

Workflow Clarity

Investigation Steps 1-4 are clearly sequenced (confirm status, extract context, route, document) with a confirm-checkpoint and an IF/ELSE routing decision plus an identification checklist, matching score 4's clear sequence with most checkpoints; not 5 because there is no validate/fix/retry feedback loop, not 3 because checkpoints and sequence are explicit rather than missing.

4 / 5

Progressive Disclosure

The skill is a self-contained ~134-line workflow organized into clear logical sections (When to Apply, Identification Checklist, Failure Mode Classification, Investigation Steps, Common Causes, Escalation Criteria, Example Analysis, Anti-Patterns, Integration), with content appropriately placed inline and no broken or buried references, matching score 4's good structure with minor organization gaps; not 5 because there is no overview-pointing-to-references architecture and it exceeds the under-50-line simple-skill threshold, not 3 because the sectioning is genuinely well-organized rather than merely 'some structure'.

4 / 5

Total

15

/

20

Passed

Description

53%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 and targets a specific niche, but lacks any 'Use when...' trigger guidance and relies on somewhat technical phrasing, which limits trigger-term quality and caps completeness at 3.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when an agent reports 0 iterations, no tool calls, and fails before execution begins').

Include common user-facing synonyms such as 'agent never started', 'no iterations ran', or 'pre-execution crash' to improve trigger-term coverage.

Expand 'Identify and handle' into a couple more concrete actions (e.g., 'classify, route, and document') to raise specificity.

DimensionReasoningScore

Specificity

Quotes 'Identify and handle agent failures with 0 iterations as pre-execution system issues' — names a specific domain and two concrete actions ('identify', 'handle'), matching the score-3 anchor of domain plus 1-2 actions without comprehensive coverage; not 4 because it lists no further concrete actions, not 2 because the domain is concrete rather than generic.

3 / 5

Completeness

The 'what' is explicit ('Identify and handle agent failures with 0 iterations...') but there is no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the judging guideline and matches the score-3 anchor of clear 'what' with 'when' missing.

3 / 5

Trigger Term Quality

Terms like 'agent failures' and '0 iterations' are somewhat natural but 'pre-execution system issues' is jargon and common variations/synonyms are missing, fitting the score-3 anchor of some relevant keywords without broad coverage; not 4 because natural-term coverage is thin, not 2 because it is more than one or two generic keywords.

3 / 5

Distinctiveness Conflict Risk

The '0 iterations' / 'pre-execution' niche is a distinct trigger with only minor overlap risk against general agent-failure-analysis skills, matching the score-4 anchor; not 5 because no explicit trigger phrases are given, not 3 because it is more specific than a broadly overlapping 'works with document files' style description.

4 / 5

Total

13

/

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.

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.