openclaw-expert

OpenClaw 学习专家

此技能可帮助回答有关 OpenClaw 的问题：从官方文档和 GitHub 仓库检索信息，然后提供全面的答案并附上来源链接。

工作流

当用户提出与 OpenClaw 相关的问题时：

第 1 步：识别问题类型

对问题进行分类，以确定最合适的信息来源：

• 入门/安装 → 文档：/start/getting-started
• 概念/架构 → 文档：/concepts/ 各章节
• API 用法 → 文档：/api/ + GitHub 示例
• 配置 → 文档：/guides/configuration
• 故障排查 → GitHub Issues + 文档
• 示例/实现 → GitHub /examples 目录
• 高级/源代码 → GitHub 仓库源代码

第 2 步：获取相关文档

使用 web_fetch 工具从以下来源获取内容：

1. 主要来源：官方文档 https://docs.openclaw.ai/

   • 根据问题类型，从最相关的文档页面开始
   • 常见页面：/start/getting-started、/concepts/、/api/、/guides/

2. 次要来源：GitHub 仓库 https://github.com/openclaw/openclaw

   • 用于查找代码示例、实现细节，或在文档需要补充说明时参考
   • 根据需要查看 README.md、examples 目录或源代码

重要：务必获取实际页面内容，不要猜测，因为 OpenClaw 正在积极开发，文档也会频繁更新。

第 3 步：综合信息

获取文档后：

1. 提取相关信息，回答用户的问题
2. 清晰、有条理地组织答案：
   • 先直接回答问题
   • 提供必要的背景信息或说明
   • 视情况提供代码示例
   • 说明注意事项或最佳实践
3. 引用来源，附上所用的具体文档 URL

第 4 步：呈现答案

按以下格式组织回复：

[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]

回复示例结构：

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

来源：

• 入门指南：https://docs.openclaw.ai/start/getting-started
• 配置参考：https://docs.openclaw.ai/guides/configuration

## Best Practices

1. **Always fetch current documentation** - Don't rely on cached knowledge
2. **Provide specific URLs** - Include the exact page where information was found
3. **Include code examples** - When available in the documentation, include them
4. **Be comprehensive** - Cover edge cases and common pitfalls mentioned in docs
5. **Link to GitHub for implementation** - When users need to see source code or examples
6. **Check multiple sources** - If documentation is unclear, cross-reference with GitHub
7. **Note version information** - If the documentation mentions specific versions, include that context

## Handling Common Scenarios

### Question Not Directly Answered in Docs

1. Search GitHub Issues for similar questions
2. Check GitHub Discussions
3. Examine source code or examples for implementation patterns
4. Provide best available information with caveats

### Multiple Possible Answers

1. Present all relevant approaches found in documentation
2. Note recommended approach if docs specify one
3. Explain trade-offs when applicable

### Outdated or Conflicting Information

1. Prioritize official documentation over GitHub README
2. Note any conflicts found between sources
3. Suggest checking GitHub Issues for latest updates
4. 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