clawddocs

clawddocs is a documentation-navigation skill: instead of guessing which doc page answers a question, it routes through a decision tree. Ask 'how do I set up Discord?' and it sends you to `providers/discord`; ask 'why isn't X working?' and it goes to `debugging` / `gateway/troubleshooting` / `providers/troubleshooting` depending on the symptom. It bundles search scripts (sitemap, keyword, and a full-text index via qmd), doc fetching, version tracking, and ready config snippets across providers, gateway, automation, platforms and tools. The decision-tree framing is the part that actually saves time — it front-loads the triage you'd otherwise do by reading three pages to find the right one.

Use case: Answering 'how do I configure <provider?>' and 'why is <tool?> broken' questions without browsing the full doc tree manually.

# Use the decision tree before the search index This skill packages several ways to find documentation: a decision tree, a sitemap search, a keyword search and a full-text index. The mistake is reaching for the most powerful one first. Search returns passages; the decision tree returns a location, and a location is what you need to answer a configuration question correctly. ## Start with the tree for configuration questions When the question is "how do I make it do X", the decision tree narrows by area — providers, gateway, automation, platforms, tools — and lands you in the right section of the docs. That is faster and more reliable than matching keywords, because configuration questions usually contain the wrong vocabulary. ## Escalate to keyword, then full-text Use keyword search when you know the exact identifier you are looking for and the tree is too coarse. Use the full-text index when you need a phrase that appears in prose rather than in a heading, and treat its results as leads to verify in the page rather than as answers. ## Pin documentation to the version you run A documentation skill is only useful if its content matches the build you are operating. Track the version alongside the fetched docs, and re-fetch when the runtime version moves. Configuration snippets are the least portable part of any documentation and the most likely to be quoted wrongly. ## Copy snippets, then check them against your own config Every snippet from documentation is written against a default configuration. Diff it against your actual file before applying it, because the difference between a snippet that works and one that silently does nothing is usually a line you already changed.