Verified:GitHub

retry-search-then-deliver

Retries search in a loop until results are found, then delivers the answer.

1|Updated Jul 1, 2026

Search Tags:#search #agent workflow #tool use #retry loop #tail recursion #deliver answer

One-click install

npx skills add https://github.com/ginaecho/skill-achievability-compiler --skill retry-search-then-deliver-ginaecho

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: retry-search-then-deliver
Source: https://github.com/ginaecho/skill-achievability-compiler/tree/main/corpus/skills/retry_loop_ok
Command: npx skills add https://github.com/ginaecho/skill-achievability-compiler --skill retry-search-then-deliver-ginaecho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Search attempts often return nothing on the first try, and a single-shot search workflow gives up too early. This Skill defines a tail-recursive retry loop that keeps searching until information is found, then delivers the answer, so transient search failures do not block task completion. ## Core Features & Use Cases - Retry Loop Workflow: Repeats the search step until results are found, with an explicit retry-or-found decision after each attempt. - Guarded Delivery: The deliver step only runs once the information is marked found, ensuring the answer is grounded in actual results. - Use Case: An agent answering a research question issues a search, gets no results, reformulates and retries several times, and only delivers the final answer once relevant information has been located. ## Quick Start Use this skill to keep searching until you find the information, then deliver the answer to my question.

Frequently Asked Questions about retry-search-then-deliver

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I make an agent retry a search until it finds results?▼

Use a tail-recursive retry loop: after each search, the agent decides between retrying with a new attempt or exiting the loop when results are found. Once the loop exits, the agent delivers the answer.

How to handle empty search results in an agent workflow?▼

Treat an empty result as a retry signal rather than a failure. The workflow loops back to the search step and only proceeds to delivery once the information is marked found.

What tools does a retry search workflow need?▼

It needs two tools: a search tool that marks information as found, and a deliver tool that requires the found state and marks the question answered. Delivery is blocked until search succeeds.

When should I not use a retry-until-found search loop?▼

Avoid it when the information may not exist at all, since the loop has no built-in maximum attempt count or timeout. For unbounded cases, add an explicit retry limit or fallback answer path.