本文へ移動
cccskills
無料GitHub で公開

search-fail-pivot

Heuristic for detecting search tool failures and pivoting to domain knowledge for document generation

インストール方法を見る

含まれるファイル(2)

  • SKILL.md4.5 KB
  • .skill_id31 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Search Tool Failure Detection and Pivot Strategy

Purpose

When using search_web or similar external data retrieval tools, repeated failures waste iterations. This skill provides a diagnostic heuristic to recognize when to abandon search attempts and proceed with existing domain knowledge.

Core Heuristic

If search_web fails 2+ consecutive times with 'unknown error' or similar non-recoverable errors, pivot to domain knowledge + run_shell for document generation.

Do not attempt more than 2 retries on the same or similar queries before pivoting.

Step-by-Step Instructions

Step 1: Track Search Failures

Monitor search_web outcomes during your task:

  • Count consecutive failures (empty results, 'unknown error', timeout, access denied)
  • Note the error type - distinguish between:
    • Recoverable: Rate limiting, temporary timeout (retry 1-2 times)
    • Non-recoverable: 'unknown error', persistent empty results, access denied

Step 2: Apply the 2-Failure Rule

IF search_web failures >= 2 (same or similar queries)
THEN:
  1. Stop attempting search_web
  2. Document what information you attempted to retrieve
  3. Proceed with existing domain knowledge

Step 3: Pivot to Domain Knowledge

When pivoting:

  1. Acknowledge the limitation: Note that external verification was attempted but unavailable
  2. Use established knowledge: Draw on training data for well-known facts, laws, cases, standards
  3. Generate with run_shell: Create documents using Python/bash scripts rather than waiting for external data

Example pivot workflow:

# Instead of continuing search_web attempts:
# 1. Compile known information from domain knowledge
known_facts = {
    "law": "COPPA requirements for children's data",
    "precedent": "FTC v. Google/YouTube settlement patterns",
    "jurisdiction": "California privacy law framework"
}

# 2. Generate document directly
# Use run_shell with Python to create PDF/DOC

Step 4: Document Generation Pattern

When generating documents after pivoting:

# Use run_shell to execute document generation
# Example: Create legal memo with Python + reportlab
python << 'EOF'
from reportlab.lib.pagesizes import letter
from reportlab.pdfgen import canvas

# Generate document with domain knowledge
c = canvas.Canvas("memo.pdf", pagesize=letter)
c.drawString(100, 750, "Legal Analysis based on established precedents")
# ... continue with known information
c.save()
EOF

When This Applies

This heuristic is particularly useful for:

Task TypeWhy It Applies
Legal researchCase law and statutes are well-documented in training
Technical documentationStandards and best practices are established knowledge
Historical analysisPast events and data are in training corpus
Regulatory complianceMajor regulations (GDPR, COPPA, HIPAA) are well-known

When NOT to Pivot

Do NOT apply this heuristic when:

  • You need current/time-sensitive data (stock prices, weather, news < 24hrs)
  • The task explicitly requires external verification
  • You have not yet attempted the search (first attempt should complete)
  • Errors are clearly recoverable (rate limit with retry-after header)

Example Decision Flow

Attempt search_web → Success? → Yes → Use results
                         ↓
                        No
                         ↓
            Is this failure #1? → Yes → Retry once with modified query
                         ↓
                        No (failure #2+)
                         ↓
            Pivot to domain knowledge + run_shell document generation

Benefits

  • Saves iterations: Avoids wasting 3-4 attempts on unavailable data
  • Maintains progress: Task continues instead of stalling on search
  • Leverages training: Uses the substantial knowledge already available
  • Clear handoff: Explicitly documents the pivot decision for transparency

Anti-Patterns to Avoid

❌ Continuing search_web attempts beyond 2 failures
❌ Not documenting why you pivoted from search
❌ Applying this to tasks requiring real-time data
❌ Abandoning search on first failure without retry

✅ Apply 2-failure rule consistently
✅ Document the pivot decision in your output
✅ Use run_shell efficiently after pivoting
✅ Distinguish recoverable vs non-recoverable errors

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Incremental audio production with duration mismatch handling, adaptive stem extension, and pre-mix alignment verification

日本語の概要は準備中です。原文の説明を表示しています。

HKUDS/OpenSpace7,7552026年8月13日 更新

Incremental audio production with duration alignment handling, per-stem verification, and adaptive extension strategies

日本語の概要は準備中です。原文の説明を表示しています。

HKUDS/OpenSpace7,7552026年8月13日 更新

Create serverless API proxy endpoints that hide API keys and provide a unified backend for the dashboard frontend. Designed for Vercel deployment.

日本語の概要は準備中です。原文の説明を表示しています。

HKUDS/OpenSpace7,7552026年8月13日 更新

End-to-end audio production workflow with stems, effects, archiving, and verification

日本語の概要は準備中です。原文の説明を表示しています。

HKUDS/OpenSpace7,7552026年8月13日 更新

Handle cascading data retrieval tool failures by falling back to embedded knowledge generation

日本語の概要は準備中です。原文の説明を表示しています。

HKUDS/OpenSpace7,7552026年8月13日 更新

Fallback pattern for executing Python code when execute_code_sandbox fails

日本語の概要は準備中です。原文の説明を表示しています。

HKUDS/OpenSpace7,7552026年8月13日 更新

HKUDS のスキルをすべて見る

このスキルの問題を報告する