CtrlK
BlogDocsLog inGet started
Tessl Logo

detect-zero-iteration-failure

Identify and classify agent failures occurring before execution starts

64

Quality

75%

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

Quality

Content

100%

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

The body is a tight, well-structured instruction-only workflow with concrete criteria, named diagnosis checks, and actionable tagging/escalation guidance; it appropriately fits the simple-skill profile.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence; aside from one restatement of the description in the opening line, every section (criteria, diagnosis, action plan, example) earns its place with concrete parenthetical examples rather than padded concept explanations.

3 / 3

Actionability

As an instruction-only skill it gives concrete, specific guidance: explicit four-condition criteria, named diagnosis checks with examples, concrete tag values (failure_mode: pre_execution), and a copy-ready example indicator block; the absence of code is not penalized because the guidance is actionable.

3 / 3

Workflow Clarity

The detect -> diagnose -> act sequence is clearly laid out, and the four identification conditions act as an explicit validation gate ("if all of the following conditions are met") before classification; no destructive or batch operation is involved, so the missing retry feedback loop does not cap the score.

3 / 3

Progressive Disclosure

At under 50 lines with no need for external references and no bundle files, the well-organized sections (Identification Criteria, Diagnosis Strategy, Action Plan, Example Indicators) satisfy the simple-skill allowance for a top progressive-disclosure score.

3 / 3

Total

12

/

12

Passed

Description

50%

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 domain and purpose but lacks explicit trigger guidance and concrete, varied action verbs, leaving it at the mid-level across dimensions.

Suggestions

Add an explicit "Use when..." clause naming natural user triggers (e.g., "Use when an agent reports zero iterations, invokes no tools, or fails before producing any output").

List more concrete actions beyond "identify and classify" (e.g., "detect zero-iteration sessions, classify the failure mode, and route to the correct diagnosis").

Include common natural phrasings users would actually say, such as "agent didn't start" or "no tools called", to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The phrase "Identify and classify agent failures occurring before execution starts" names a domain and two actions (identify, classify), but the actions are abstract rather than the multiple concrete operations (e.g., extract, fill, merge) expected for a 3; it is more comprehensive than the bare score-1 example.

2 / 3

Completeness

It states what the skill does (identify and classify pre-execution failures) but has no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2; the when is only implied.

2 / 3

Trigger Term Quality

"agent failures occurring before execution starts" contains some relevant natural terms a debugger might say, but it omits common variations a user would actually voice (e.g., "zero iteration", "agent didn't start", "no tools called"), matching the score-2 anchor of some-but-incomplete keywords.

2 / 3

Distinctiveness Conflict Risk

The pre-execution framing is a somewhat specific niche, but "agent failures" is broad enough to overlap with general agent-debugging skills and there are no explicit distinct triggers to reduce conflict risk, matching the score-2 anchor.

2 / 3

Total

8

/

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.