Individual skill
tool-design-errors
Design actionable agent tool errors, ambiguity handling, retry guidance, and fallback behavior, or debug an agent that loops on or misreads a failing tool.
plugins/runtypelabs/skills/skills/tool-design-errors/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,537
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 12,205 bytesSKILL.mdcore · 12,205 bytesSKILL.mdcore · 12,205 bytesagents/openai.yamlasset · 292 bytes
Read excerpt
# Tool error design
An agent that receives only `429` either retries in a tight loop or gives up. An agent
that receives "Rate limited. Wait 30 seconds, or reduce `batchSize` to 50 and retry"
makes a better second call. Give every error a class, a reason, and the next call to
make. Design the failure paths with the same care as the success path.
## Procedure
1. **List every way the tool can fail**: bad input, missing prerequisite, not found,
ambiguous match, upstream unavailable, rate limit, timeout, permission denied,
missing scope, partial completion.
2. **Classify each failure** into exactly one class (below). The class tells the agent
whether to retry, change the call, ask the user, or have the user re-authenticate.