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

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

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

   • 用于代码示例、实现细节或当文档需要澄清时
   • 根据需要检查 README.md、示例目录或源代码

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

步骤 3：整合信息

检索文档后：

1. 提取相关信息以回答用户的问题
2. 组织答案，使其结构清晰、逻辑合理：
   • 以对问题的直接回答开始
   • 提供必要的背景或解释
   • 如果相关，包含代码示例
   • 注明任何注意事项或最佳实践
3. 引用来源，包含所使用的具体文档 URL

步骤 4：呈现答案

按以下格式组织回复：

[对问题的直接回答]

[解释和细节]

[如果适用，包含代码示例]

**来源：**
- [具体页面标题]: [文档页面的完整 URL]
- [如果使用了其他来源]: [完整 URL]

示例响应结构：

OpenClaw 使用声明式配置方法来定义工作流。

要配置工作流，你需要创建一个指定...的 YAML 文件。

示例：
```yaml
workflow:
  name: example
  steps:
    - action: process

来源：

• 入门指南: https://docs.openclaw.ai/start/getting-started

• 配置参考: https://docs.openclaw.ai/guides/configuration

  最佳实践

  1. 始终获取最新文档 - 不要依赖缓存的知识
  2. 提供具体的 URL - 包含找到信息的确切页面
  3. 包含代码示例 - 如果文档中有，请包含它们
  4. 力求全面 - 涵盖文档中提到的边缘情况和常见陷阱
  5. 链接到 GitHub 以查看实现 - 当用户需要查看源代码或示例时
  6. 检查多个来源 - 如果文档不清楚，请与 GitHub 交叉参考
  7. 注意版本信息 - 如果文档提到特定版本，请包含该上下文

  处理常见场景

  文档未直接回答的问题

  1. 在 GitHub Issues 中搜索类似问题
  2. 检查 GitHub Discussions
  3. 检查源代码或示例以了解实现模式
  4. 提供最佳可用信息并注明注意事项

  存在多个可能的答案

  1. 呈现文档中找到的所有相关方法
  2. 如果文档指定了推荐方法，请注明
  3. 在适用时解释权衡

  信息过时或冲突

  1. 优先考虑官方文档而非 GitHub README
  2. 注明在来源之间发现的任何冲突
  3. 建议检查 GitHub Issues 以获取最新更新
  4. 提供可用的最新信息

  参考文件

  • references/documentation_guide.md - 文档结构概述和搜索策略（当不确定在哪里找到特定信息时查阅）

  使用的工具

  • web_fetch - 用于检索文档页面的主要工具
  • web_search - 当确切 URL 未知时，用于查找特定页面或 GitHub issues

  注意事项

  • OpenClaw 正在积极开发中 - 始终获取最新的文档
  • 用户的问题可能是中文或英文 - 使用相同的语言回复
  • 在适当时包含中英文技术术语
  • 在将 URL 包含在响应中之前，始终验证其是否有效

每周安装量

92

仓库

fanthus/agent-skills

首次出现

2026年2月6日

安全审计

Gen Agent Trust HubPassSocketPassSnykWarn

安装于

opencode88

gemini-cli84

codex81

github-copilot79

kimi-cli76

amp75

Step 2: Fetch Relevant Documentation

Use web_fetch tool to retrieve content from:

1. 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/

2. 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:

1. Extract relevant information that answers the user's question
2. 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
3. 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

  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

Weekly Installs

92

Repository

fanthus/agent-skills

First Seen

Feb 6, 2026

Security Audits

Gen Agent Trust HubPassSocketPassSnykWarn

Installed on

opencode88

gemini-cli84

codex81

github-copilot79

kimi-cli76

amp75