This skill helps answer questions about OpenClaw by retrieving information from official documentation and the GitHub repository, then providing comprehensive answers with source links.
Workflow
When the user asks an OpenClaw-related question:
Step 1: Identify the Question Type
Categorize the question to determine the best sources:
Getting Started/Installation
→ Documentation:
/start/getting-started
Concepts/Architecture
→ Documentation:
/concepts/
sections
API Usage
→ Documentation:
/api/
+ GitHub examples
Configuration
→ Documentation:
/guides/configuration
Troubleshooting
→ GitHub Issues + Documentation
Examples/Implementations
→ GitHub
/examples
directory
Advanced/Source Code
→ GitHub repository source code
Step 2: Fetch Relevant Documentation
Use
web_fetch
tool to retrieve content from:
Primary source
Official documentation at
https://docs.openclaw.ai/
Start with the most relevant documentation page based on the question type
Common pages:
/start/getting-started
,
/concepts/
,
/api/
,
/guides/
Secondary source
GitHub repository at
https://github.com/openclaw/openclaw
For code examples, implementation details, or when docs need clarification
Check README.md, examples directory, or source code as needed
Important
Always fetch the actual pages rather than guessing content, as OpenClaw is actively developed and documentation changes frequently.
Step 3: Synthesize Information
After retrieving documentation:
Extract relevant information
that answers the user's question
Organize the answer
in a clear, logical structure:
Start with a direct answer to the question
Provide necessary context or explanation
Include code examples if relevant
Note any caveats or best practices
Cite sources
by including the specific documentation URLs used
Step 4: Present the Answer
Format the response as follows:
[Direct answer to the question]
[Explanation and details]
[Code examples if applicable]
**
Sources:
**
-
[
Specific page title
]
:
[Full
URL to the documentation page]
-
[
Another source if used
]
:
[Full
URL]
Example response structure:
OpenClaw uses a declarative configuration approach for defining workflows.
To configure a workflow, you create a YAML file that specifies...
Example:
```yaml
workflow:
name: example
steps:
-
action: process
Sources:
Getting Started Guide:
https://docs.openclaw.ai/start/getting-started
Configuration Reference:
https://docs.openclaw.ai/guides/configuration
Best Practices
Always fetch current documentation - Don't rely on cached knowledge
Provide specific URLs - Include the exact page where information was found
Include code examples - When available in the documentation, include them
Be comprehensive - Cover edge cases and common pitfalls mentioned in docs
Link to GitHub for implementation - When users need to see source code or examples
Check multiple sources - If documentation is unclear, cross-reference with GitHub
Note version information - If the documentation mentions specific versions, include that context
Handling Common Scenarios
Question Not Directly Answered in Docs
Search GitHub Issues for similar questions
Check GitHub Discussions
Examine source code or examples for implementation patterns
Provide best available information with caveats
Multiple Possible Answers
Present all relevant approaches found in documentation
Note recommended approach if docs specify one
Explain trade-offs when applicable
Outdated or Conflicting Information
Prioritize official documentation over GitHub README
Note any conflicts found between sources
Suggest checking GitHub Issues for latest updates
Provide the most recent information available
Reference Files
references/documentation_guide.md - Overview of documentation structure and search strategies (consult when unsure where to find specific information)
Tools to Use
web_fetch - Primary tool for retrieving documentation pages
web_search - For finding specific pages or GitHub issues when exact URL is unknown
Notes
OpenClaw is actively developed - always fetch fresh documentation
User's questions may be in Chinese or English - respond in the same language
Include both Chinese and English technical terms when appropriate
Always verify URLs work before including in response