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

70%

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

The skill body is a well-organized, clearly sequenced diagnostic workflow with an executable detection function and ready-made logging templates, though it is somewhat repetitive and mixes executable code with descriptive/pseudocode guidance.

Suggestions

Consolidate the repeated 0-iteration/0-tools classification logic so it is stated once and referenced, reducing redundancy across the checklist, table, function, and example.

Replace the pseudocode routing block and descriptive Step 2 with concrete, executable checks or commands to push actionability higher.

Turn the Common Causes table's 'Resolution' column into specific, runnable actions rather than short descriptive phrases.

DimensionReasoningScore

Conciseness

The body is mostly efficient (checklists, tables, short code blocks) but restates the 0-iteration/0-tools classification across the 'When to Apply', checklist, classification table, Python function, and example sections, so it could be tightened.

2 / 3

Actionability

Provides one executable Python function and copy-paste JSON/YAML templates, but substantial portions (the routing block, Step 2 error-context review, and the Common Causes table) are pseudocode or descriptive rather than fully executable, matching the 'some concrete guidance but pseudocode' anchor.

2 / 3

Workflow Clarity

Presents a clear 4-step sequenced workflow with an explicit confirm-zero-iteration checkpoint (Step 1), a confirmation checklist, and routing feedback (system vs standard analysis), matching the 'clear sequence with explicit validation steps and checklists' anchor.

3 / 3

Progressive Disclosure

A single, cohesive SKILL.md with no need for external bundle files, organized into clearly navigable sections (When to Apply, Checklist, Classification, Investigation Steps, Causes, Escalation, Example, Anti-Patterns, Integration).

3 / 3

Total

10

/

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, specific niche but lacks explicit 'when to use' trigger guidance and natural trigger terms, capping several dimensions at 2.

Suggestions

Add an explicit 'Use when...' clause with concrete triggers, e.g. 'Use when an agent run reports 0 iterations, no tool calls, and no artifacts.'

Surface natural user-facing terms ('agent didn't run', 'failed before starting', 'no output') alongside the technical 'pre-execution system issues' phrasing.

List concrete actions the skill takes (classify the failure mode, route to system vs agent investigation, log the categorization) to lift specificity.

DimensionReasoningScore

Specificity

Names the domain ('agent failures with 0 iterations', 'pre-execution system issues') and a couple actions ('Identify and handle'), but does not enumerate multiple specific concrete actions, fitting the 'names domain and some actions' anchor.

2 / 3

Completeness

Clearly states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Has some relevant keywords a user might say ('agent failures', '0 iterations'), but 'pre-execution system issues' is technical jargon and common natural variations are missing, matching the 'some relevant keywords but missing variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The zero-iteration / pre-execution niche is fairly specific, but the broad 'agent failures' framing could overlap with a general failure-analysis skill and lacks distinct trigger phrasing.

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.