Handle web research failures with explicit error recognition and domain-specific fallback strategies
56
63%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./benchmarks/gdpval/skills/research-fallback-enhanced/SKILL.mdThis skill provides a workflow for handling tasks that require external research when web search or webpage reading tools fail due to network issues or tool unavailability.
Begin by attempting to use available web research tools:
1. Use search_web for current information, statistics, or recent developments
2. Use read_webpage for detailed source material when URLs are provided
3. Document what you attempted to findRecognize when to pivot — including explicit error patterns:
unknown error from search_web — immediately recognize this as a tool failure trigger (do not retry excessively)Do not spend excessive time retrying failed tools. After 1-2 attempts with unknown error or similar failures, proceed to Step 3.
When external tools fail:
When producing deliverables:
- Include a note that external verification is recommended for time-sensitive information
- Flag any claims that would benefit from current source verification
- Focus on established principles, frameworks, and well-documented facts
- Avoid making specific claims about very recent events or statisticsProceed with the original task deliverable:
Task requires research on [TOPIC]
|
v
Attempt search_web / read_webpage
|
+----+----+
| |
Success Failure (after 1-2 attempts)
| |
| | **Note: `unknown error` = immediate pivot signal**
v v
Use sources Pivot to internal knowledge
| |
+----+----+
|
v
Generate content with appropriate disclaimers
|
v
Create deliverable fileunknown error from search_web is a clear signal to pivot, not a reason for extended retriesExample 1: Legal Memo
Task: Create legal memo on privacy law violations
Workflow:
unknown errorOutcome: Comprehensive memo produced despite tool failures, with appropriate disclaimers about verification.
Example 2: Anatomical/Medical Content
Task: Create proposal with anatomical utilization analysis and procedure capacity estimates
Workflow:
unknown errorunknown errorOutcome: High-quality proposal with anatomical tables, procedure estimates, and cost analysis created using internal knowledge, with transparent disclaimers about statistical verification.
In these cases, report the tool failure and request guidance rather than proceeding with internal knowledge alone.
c5a9c4b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.