search-fallback-workflow
Graceful degradation workflow for continuing tasks when web search tools fail, using internal knowledge with verification caveats
- License 许可
- MIT
- 所属仓库
- AG064/OpenSpace
- 最近更新
- 2026-10-08
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- search-fallback-workflow
- description
- Graceful degradation workflow for continuing tasks when web search tools fail, using internal knowledge with verification caveats
02 资源文件 1
- 其他.skill_id38 B
03 SKILL.md 正文
Search Fallback Workflow
When to Apply
Use this workflow when:
search_webtool fails repeatedly (typically 2+ consecutive failures)- External information is needed but unavailable due to tool limitations
- Task completion is still possible with reasonable confidence using internal knowledge
- The output can include appropriate caveats about verification needs
Core Pattern
-
Detect Search Failure
- Monitor
search_webresponses for errors, empty results, or timeouts - After 2 consecutive failures, assess whether the task can proceed without fresh data
- Monitor
-
Assess Feasibility
- Determine if internal knowledge is sufficient for the task at hand
- Identify which sections/claims require external verification
- Evaluate risk level: Can the task proceed safely with caveats?
-
Proceed with Internal Knowledge
- Continue the task using well-established facts, regulations, or principles
- Prioritize accuracy over completeness when uncertain
- Use conservative language for claims that cannot be verified
-
Flag for Verification
- Clearly mark any claims that should be verified:
[VERIFICATION NEEDED: Search tool unavailable during generation] - Include a verification checklist in the execution summary
- Distinguish between high-confidence and low-confidence assertions
- Clearly mark any claims that should be verified:
-
Document Limitations
- Include an explicit note in the output about search unavailability
- List specific items requiring follow-up verification
- Provide recommendations for manual verification steps
Implementation Template
## Execution Notes
**Search Tool Status**: Unavailable during generation
**Confidence Levels**:
- ✓ High confidence: Established regulations, well-documented facts
- ⚠ Medium confidence: Industry standards, commonly accepted practices
- ✗ Requires verification: Time-sensitive data, recent changes, specific citations
**Verification Checklist**:
- [ ] Verify citation: [specific reference]
- [ ] Confirm current status: [specific item]
- [ ] Review recent updates: [specific topic]
Code Pattern for Agents
# Pseudocode for search fallback detection
search_attempts = 0
max_search_attempts = 2
search_failed = False
for query in required_searches:
result = search_web(query)
if result.success:
process_result(result)
else:
search_attempts += 1
if search_attempts >= max_search_attempts:
search_failed = True
log_warning("Search tool unavailable, proceeding with fallback")
break
if search_failed:
# Apply graceful degradation
content = generate_with_internal_knowledge()
add_verification_flags(content)
document_limitations_in_summary()
Example Output Structure
When using this fallback, structure documents with clear sections:
# Document Title
## Disclaimer
This document was generated with limited access to external verification tools.
Items marked with [VERIFICATION NEEDED] should be confirmed before final use.
## Content Sections
[Standard content with internal knowledge]
## Items Requiring Verification
- Topic A: Current regulatory status needs confirmation
- Topic B: Recent policy changes should be checked
- Topic C: Specific citations require source validation
## Recommendations
1. Cross-reference with official sources
2. Verify time-sensitive information
3. Consult subject matter experts for critical decisions
Best Practices
- Don't fabricate citations - Better to flag as unverified than invent sources
- Use conservative language - "Generally," "Typically," "Commonly" instead of absolutes
- Prioritize safety - If misinformation could cause harm, recommend manual verification
- Track what's missing - Maintain a clear list of items needing follow-up
- Be transparent - Clearly communicate limitations to end users
When NOT to Use This Pattern
- Tasks requiring current/real-time data (stock prices, news, weather)
- Legal or medical advice requiring authoritative sources
- Compliance documentation where citations are mandatory
- Situations where incorrect information could cause significant harm
Related Patterns
citation-management: Handling references and sources in documentserror-recovery-workflow: General patterns for tool failure recoveryconfidence-annotation: Marking certainty levels in generated content
04 同仓库更多 Skills
write-special-chars-ts-check
Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.
write-special-chars-readback
Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of /tmp helper scripts.
write-special-chars-heredoc
Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) by using a Python heredoc script executed via shell.
worldmonitor-reference
Curated architecture index of the WorldMonitor open-source dashboard. Reference for extracting patterns — vanilla TypeScript, Panel class hierarchy, service layer, CSS grid, API edge functions, refresh scheduler, and 60+ data source integrations.
virtual-list
Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations
verify-directory-structure
Diagnose and resolve file access issues by first verifying the directory structure.