Skip to content
cccskills
FreePublished on GitHub

detect-zero-iteration-failure

Identify agent failures that happen before any work starts by checking iteration counts, tool use, artifacts, and logs. Classify these incidents as pre-execution failures and guide investigation toward environment setup, initialization, and resource limits.

OriginalShow the original description

Identify and classify agent failures occurring before execution starts

See how to install

Good for

  • Investigating agent sessions with zero completed iterations
  • Classifying failures before the first tool call
  • Routing incidents to infrastructure or platform teams
  • Planning retries after session initialization failures

Files included (2)

  • SKILL.md1.9 KB
  • .skill_id43 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

Detect Zero-Iteration Failure

This skill provides a workflow for identifying and classifying agent failures that occur prior to any task execution.

Identification Criteria

Flag a task execution as a Zero-Iteration Failure if all of the following conditions are met:

  1. Iteration Count: The agent reports 0 completed iterations.
  2. Tool Usage: No tools were invoked during the session.
  3. Artifacts: No documents, files, or code artifacts were created.
  4. Conversation Log: The log ends abruptly or contains only an initial error message without agent reasoning steps.

Diagnosis Strategy

When a Zero-Iteration Failure is detected, do not attempt standard agent-level debugging (e.g., analyzing reasoning chains or tool parameters). Instead, investigate system-level causes:

  1. Environment Health: Check if the runtime environment initialized correctly (e.g., dependencies installed, API keys loaded).
  2. Prompt Parsing: Verify if the initial user instruction was malformed or triggered safety filters immediately.
  3. Initialization Crash: Look for stack traces or panic logs occurring before the first agent step.
  4. Resource Limits: Check if memory or quota limits were hit before execution began.

Action Plan

  1. Tag the Failure: Label the incident as failure_mode: pre_execution rather than failure_mode: agent_logic.
  2. Escalate: Route to infrastructure or platform engineering rather than prompt engineering.
  3. Retry Strategy: If automating retries, reset the environment context before retrying, as the previous context may be poisoned.

Example Indicators

Status: Failed
Iterations: 0
Tools Called: []
Error: "Session initialization failed: Missing environment variable"

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Prepare audio stems, the separate parts of a track, for mixing by matching their durations with silence, loops, or crossfades. Verify each generated and processed file before moving to the next production step.

  • Match audio parts with different durations
  • Extend drums and melodic parts using suitable methods
  • Check audio specifications before mixing
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Produce audio in separate stems, meaning individual instrument tracks, and verify each output as you go. Align track lengths with silence, loops, or crossfades, then apply effects, mix a master, and package the files.

  • Align instrument tracks to a reference audio file
  • Choose how to extend tracks that are too short
  • Verify audio properties after generation and effects
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Build serverless endpoints that relay external API requests for a dashboard while keeping API keys on the server. Includes Vercel examples for input checks, caching, cross-origin access, and consistent JSON responses.

  • Connect a dashboard to external APIs without exposing API keys
  • Create endpoints for stock quotes and news
  • Standardize API responses and error handling
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Produce a master track and separate audio parts through a structured Python workflow. Apply filters and reverb, export WAV files with consistent settings, package them in a ZIP archive, and check that the deliverables meet the requested specifications.

  • Export a master track with separate audio parts
  • Apply filters and reverb to audio
  • Check duration and format across deliverables
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

Keep document creation moving when web searches and page retrieval repeatedly fail. The skill preserves the original task, uses the model’s existing knowledge, and clearly identifies information that could not be checked against external sources.

  • Continue drafting after repeated web retrieval failures
  • Preserve task requirements during network errors
  • Mark information that could not be externally verified
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

When Python execution repeatedly fails in execute_code_sandbox, use a file-based alternative: save the script, run it through the shell, and capture results or errors. The guidance covers paths, imports, timeouts, structured output, and optional cleanup.

  • Retry Python work through the shell after repeated sandbox failures
  • Run longer tasks with an adjusted timeout
  • Execute Python work that needs multiple files or system utilities
HKUDS/OpenSpace7.8KUpdated Aug 13, 2026

See all skills by HKUDS

Report a problem with this skill