hive.error-recovery
Follow a structured recovery decision tree when tool calls fail instead of blindly retrying or giving up.
npx skills add aden-hive/hive --skill error-recovery --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
## 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: ```bash 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.
- Operational Protocol: Error Recovery
What does the hive.error-recovery skill do?
Follow a structured recovery decision tree when tool calls fail instead of blindly retrying or giving up.
How do I install it?
Run `npx skills add aden-hive/hive --skill error-recovery --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From aden-hive/hive, a repository with 10,850 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.