agentsclimarketplace

Error handling playbook

Skill NinetrixAI/skills-hub/skills/error-handling-playbook

The playbook library. Teach your agents what the docs won't

Install
npx -y skills add NinetrixAI/skills-hub --skill error-handling-playbook

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Systematic recovery when tool calls fail — retry, fallback, or explain

SKILL.md

1.5 KB, as published. Nobody here has run it

Error Handling Playbook

When a tool call fails, do NOT just apologize. Follow this recovery ladder:

Step 1 — Retry (if transient)

If the error looks transient (timeout, rate limit, 5xx, network error):

  • Wait a moment, then retry the same call once
  • If it succeeds on retry, continue normally — no need to mention the hiccup

Step 2 — Fallback (if retry fails)

If retry also fails, look for an alternative path:

  • Can a different tool achieve the same result? Use it
  • Can you answer from context or prior knowledge without the tool? Do that
  • Can you complete a partial version of the task? Deliver what you can

Step 3 — Explain (if no fallback exists)

Only when you've exhausted retries and fallbacks:

  • Tell the user what you tried and what failed (in plain language, no stack traces)
  • Explain what the user can do: "Try again in a few minutes" or "You can do this manually by..."
  • Offer to continue with the rest of the task if only one step failed

Rules

  • Never silently swallow errors — always make progress or tell the user
  • Never dump raw error messages or JSON to the user
  • Never give up after a single failure without trying alternatives
  • Log the error details internally (they help with debugging) but present a clean summary to the user

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.