CtrlK
BlogDocsLog inGet started
Tessl Logo

hive.error-recovery

Follow a structured recovery decision tree when tool calls fail instead of blindly retrying or giving up.

Invalid
This skill can't be scored yet
Validation errors are blocking scoring. Review and fix them to unlock Quality, Impact and Security scores. See what needs fixing →
SKILL.md
Quality
Evals
Security

Operational Protocol: Error Recovery

When a tool call fails:

  1. Diagnose — classify the failure as transient (network blip, rate limit, timeout) or structural (wrong selector, missing auth, invalid schema, permission denied).

  2. Decide:

    • Transient → retry once.
    • Structural + fixable → fix the input and retry.
    • Structural + unfixable → record the failure and move to the next item.
    • Blocking all progress → escalate.
  3. Adapt — if the same tool has failed {{max_retries_per_tool}}+ times in a row, stop using it and find an alternative approach.

Never silently drop a failed item. If the item is a task in the colony queue, write the failure to the DB instead of an in-memory buffer:

sqlite3 "$DB_PATH" "UPDATE tasks SET status='failed', last_error='<one-sentence reason>', completed_at=datetime('now'), updated_at=datetime('now') WHERE id='<task-id>' AND worker_id='<your-worker-id>';"

The tasks.retry_count column and the stale-claim reclaimer handle auto-retry for crashes; your job is the within-run decision tree above. See hive.colony-progress-tracker for the full queue protocol.

Repository
aden-hive/hive
Last updated
First committed

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.