openclaw-sage

What This Skill Does

The openclaw-sage skill serves as the primary intelligent interface for the OpenClaw documentation ecosystem. It functions as a specialized documentation expert capable of navigating the entire OpenClaw knowledge base to provide accurate, context-aware answers regarding setup, configuration, provider integrations, and troubleshooting. By utilizing a combination of live documentation fetching, BM25-based semantic searching, and internal change tracking, the agent ensures that developers are always working with the most current and relevant information. This skill eliminates the need for manual navigation of documentation sites by surfacing specific details directly within the agent chat interface.

Installation

To install this skill, use the ClawHub command line interface within your project terminal:

clawhub install openclaw/skills/skills/alfonso46674/openclaw-sage

Ensure that you have the appropriate permissions to install skills within your current workspace environment.

Use Cases

• Configuration Assistance: Quickly look up configuration parameters for the OpenClaw gateway without switching context to a web browser.
• Troubleshooting: Diagnose common errors by fetching specific sections of the documentation related to authentication or retry logic.
• Documentation Discovery: Users can list all available documentation topics to explore the full capabilities of the OpenClaw framework.
• Version Updates: Check for what's new in the latest OpenClaw releases through the system's change tracking logs.

Example Prompts

1. "How do I configure the authentication settings for the OpenClaw gateway?"
2. "Show me all available documentation categories so I can see what I can manage with OpenClaw."
3. "Fetch the retry settings section from the gateway configuration guide to help me debug my current connection drops."

Tips & Limitations

• TOC First: Always use the --toc flag with fetch-doc.sh when dealing with long documents. This helps you identify the correct section heading, saving tokens and improving response accuracy.
• Metadata Checking: Use the info.sh tool before fetching large documents to verify if the information is current and to estimate the volume of data being retrieved.
• Caching: Remember that documents have a 24-hour cache TTL. If you suspect a recent update hasn't propagated, rely on the live fetching capabilities or wait for the cache to refresh.
• Path Precision: Documentation paths must be accurate; if you receive an empty response, use sitemap.sh to confirm the correct path structure.