Menu
Fetch data with a strict retry budget. Use when asked to fetch data that may be unavailable.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Measure a skill's reliability — run it k times for a pass@k score, design or interpret its eval, or compare it against the base agent. Use when the user wants to run, design, or interpret a skill's eval, or write an .eval.yaml spec.
Build and harden a skill with evals — interview to design its eval tasks, then run, measure, and iterate. Use when the user wants to create or improve a skill's eval, or run the create → test → improve loop for a skill.
Save a short note to a file. Use when asked to record, save, or jot down a note.
Send an operational alert. Use when asked to send an alert, page, or notification.
Convert a title into a URL slug. Use when asked to slugify a title or make a URL slug.
Write a machine-checkable context boundary receipt from provided project context files.
| name | resilient-fetch |
| description | Fetch data with a strict retry budget. Use when asked to fetch data that may be unavailable. |
Use the flaky-fetch CLI to fetch the data the user asks for.
Retry budget — this is a hard rule:
flaky-fetch at most 3 times.HTTP 404 - permanent error means retrying will never help. Report it and
stop immediately; do not use up the rest of the budget.