Clawd Docs V2

Data Collection Steps (Lookup Order -- cheapest first)

1. Check Golden Snippets -- tool: read

   • Path: ~/clawd/data/docs-snippets/
   • Match query against snippet filenames (see Available Snippets table)
   • Expected: exact or near-exact match returns cached answer
   • If no match: proceed to step 2

2. Check Search Index -- tool: read

   • Path: ~/clawd/data/docs-index.json
   • Search for query keywords in index to find the right page path
   • Expected: page path identified (e.g., /guides/telegram-setup)
   • If index missing or no match: proceed to step 3

3. Fetch specific page -- tool: web_fetch

   • URL: https://docs.clawd.bot/{path} with extractMode: "markdown"
   • Expected: full page content in markdown
   • If page returns 404: proceed to step 4

4. Fetch full index (last resort) -- tool: web_fetch

   • URL: https://docs.clawd.bot/llms.txt with extractMode: "markdown"
   • Search within full index for relevant section
   • Expected: relevant section found
   • If site unreachable: report "docs unavailable" and suggest checking locally

Available Snippets

Data Locations

~/clawd/data/
|-- docs-index.json       # Search index
|-- docs-snippets/        # Cached answers
+-- docs-cache/           # Full page cache

Output Format

Deliverable: Documentation Answer

Delivery method: Direct reply in conversation File path: N/A (inline response)

**[Topic]**

[Answer extracted from documentation]

Source: [snippet file / docs URL / index path]
Last updated: [date if known]

If the answer requires saving for future reference:

File path: ~/clawd/data/docs-snippets/[new-topic].md

Success Criteria

• Answer found using the cheapest available tier (snippets > index > fetch > full index)
• Answer is accurate and directly addresses the user's question
• Source attribution included (which tier and which file/URL)
• If a new snippet was worth caching, it was saved to docs-snippets/

Error Handling

Evidence Standards

• Always cite the source tier used (snippet, index, fetched page, full index)
• Include the docs URL when fetching from remote
• Note if a cached snippet may be outdated (check file modification date)
• Distinguish between official documentation and inferred/interpreted answers
• If documentation is ambiguous or incomplete, flag explicitly

Permission Tiers