Individual skill
tool-design-execution
Design how an agent tool runs: sync or async job, idempotency, timeouts, transactions, and compensation. Use when a tool is slow, has side effects that a retry could duplicate, or spans several systems.
plugins/runtypelabs/skills/skills/tool-design-execution/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,531
- Repository last updated
- Nov 6, 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 · 10,798 bytesagents/openai.yamlasset · 316 bytes
Read excerpt
# Tool Execution Design
Agents retry. They retry on timeouts, on ambiguous errors, and sometimes on nothing at
all. Execution design makes that safe: bounded time, safe repetition, and consistent
state when a multi-step operation fails halfway.
## Procedure
1. **Measure or estimate the wall-clock time** of the operation: typical (p50) and
worst case (p99).
2. **Pick the access pattern**: synchronous for bounded seconds, async job for minutes,
streaming when partial output is useful as it arrives, event-driven when the tool
notifies rather than answers.
3. **For every command tool, decide the retry story**: natural idempotency, an