
iii-error-handling
Handle iii engine and SDK errors across Node, Python, Rust, and browser workers
by iii-hqFree
Description
iii-error-handling is an iii skill for interpreting and handling errors from the engine and from the SDKs, across Node, Python, Rust and browser workers. iii has two broad error classes: SDK or local errors, and engine or remote invocation errors. The skill tells an agent to branch on the exact error code rather than matching message strings, and to keep engine wire codes separate from SDK-local codes. The codes it lists are function_not_found, when no function is registered under that ID, which calls for checking the ID, worker startup, discovery and trigger type hints; invocation_error, when the engine fails to route, record or complete an invocation, which calls for inspecting engine logs, protocol state and worker connectivity; invocation_stopped, when the engine or runtime cancels the work, which should be treated as failed; and FORBIDDEN, when RBAC denies the action, where the advice is not to retry blindly and to inspect the policy and allowed functions. It also covers function_not_invokable, invocation_failed for handler failures, and two timeout codes. TIMEOUT is the Node and Python SDK caller timeout, and the advice is to raise it only for work that is expected to run long, and to optimize or enqueue otherwise. The skill is installed with npx skills from the iii-hq/iii repository, and its audits all pass.…
Highlights
- Error codes separated by engine and SDK origin
- Branch on exact code strings, not messages
- RBAC denial and retry guidance
- Timeout guidance for long-running work
- Covers Node, Python, Rust and browser workers
Ratings & Reviews
No ratings yet
Be the first to rate iii-error-handling.
People also visit
iii-error-handling FAQ
What does this skill cover?
Error codes from the iii engine and SDKs, including function_not_found, invocation_error, FORBIDDEN and TIMEOUT, with how to handle each.
Should code match error messages?
No. The skill says to branch on the exact error code, and keep engine codes apart from SDK-local codes.
What should I do on a FORBIDDEN error?
Do not retry blindly. Inspect the policy, the auth context and the allowed functions.
When should I raise a timeout?
Only when the workload is expected to run long. Otherwise optimize the work or enqueue it.
How do I install it?
Run npx skills add https://github.com/iii-hq/iii --skill iii-error-handling.
What do the security audits show?
Gen Agent Trust Hub, Socket and Snyk all pass.
What are the best iii-error-handling alternatives?
Popular alternatives to iii-error-handling include error-handling, diagnosing-superpowers and diagnose. See all iii-error-handling alternatives











