Token导航 LogoToken导航

Agent Skill · 研究检索

openclaw-guide(OpenClaw 指南)

openclaw-guide 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

openclaw-guide 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 13,142。

总安装 9,647周安装 406GitHub Stars 公开资料未说明下载 3,378核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:openclaw-guide(OpenClaw 指南)
来源仓库:https://github.com/linux2010/openclaw-guide
安装命令:
openclaw skills install openclaw-guide
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install openclaw-guide

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

权威 OpenClaw 文档查找器,提供功能说明、配置指南与使用技巧的准确信息。适合新用户快速上手或老用户查阅细节,基于官方资料避免误导。当用户询问特定功能(如技能安装、OAuth 设置)时触发,返回精准段落与操作步骤。答案随文档更新而同步,但重大变更前可能有短暂滞后,建议交叉核对版本号。

不提供个性化配置建议,复杂部署请结合日志与社区最佳实践调整。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install openclaw-guide;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

openclaw-guide 怎么安装?

在终端执行 openclaw skills install openclaw-guide。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

openclaw-guide 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

openclaw-guide 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

openclaw-guide 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

openclaw-guide 用的人多吗?

公开数据是累计安装 9,647 次,近一周安装 406 次,下载 3,378 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

openclaw-guide 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
openclaw-guide

OpenClaw 指南 · 本页

9,647—需要联网MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
openclaw-guide
description
Authoritative OpenClaw guidance and documentation lookup. Provides accurate information about OpenClaw capabilities, configuration, and usage based on official sources (docs.openclaw.ai and github.com/openclaw/openclaw). Use when users ask about OpenClaw features, setup, configuration, troubleshooting, or any OpenClaw-related topics.

OpenClaw Guide

Purpose

Provide authoritative, up-to-date information about OpenClaw based on official documentation and source code. This skill ensures users receive accurate answers by consulting primary sources rather than relying on potentially outdated knowledge.

When to Use This Skill

  • User asks about OpenClaw capabilities, features, or functionality
  • User needs help with OpenClaw configuration or setup
  • User has questions about OpenClaw architecture or components
  • User requests troubleshooting guidance for OpenClaw issues
  • User wants to understand OpenClaw best practices or workflows
  • Any query related to OpenClaw that requires official documentation verification

Core Responsibilities

1. Official Documentation Lookup

  • Always prioritize information from https://docs.openclaw.ai
  • Search the official documentation for relevant sections
  • Extract and present accurate, current information
  • Cite specific documentation sections when possible

2. Source Code Verification

  • Consult https://github.com/openclaw/openclaw for implementation details
  • Verify feature availability and behavior against actual source code
  • Check for recent changes or updates in the repository
  • Reference specific files, commits, or branches when relevant

3. Information Synthesis and Presentation

  • Analyze gathered information from official sources
  • Present clear, concise, and actionable guidance
  • Avoid speculation or assumptions beyond documented facts
  • Acknowledge when information is not available in official sources

4. Response Quality Standards

  • Accuracy: Only provide information verified from official sources
  • Currency: Prioritize the most recent documentation and code
  • Completeness: Cover all relevant aspects of the user's question
  • Clarity: Present information in an understandable, well-structured format

Workflow Process

Step 1: Query Analysis

  • Identify the specific OpenClaw topic or question
  • Determine which official sources are most relevant (docs vs. source code)
  • Plan the search strategy for efficient information retrieval

Step 2: Documentation Search

# Use web search to find relevant documentation pages
web_search "site:docs.openclaw.ai <topic>"
web_fetch "https://docs.openclaw.ai/<relevant-page>"

Step 3: Source Code Investigation (if needed)

# Search GitHub repository for implementation details
web_search "site:github.com/openclaw/openclaw <topic>"
# Or navigate specific repository sections
web_fetch "https://github.com/openclaw/openclaw/tree/main/<relevant-path>"

Step 4: Information Synthesis

  • Cross-reference documentation and source code findings
  • Resolve any discrepancies by prioritizing source code (most current)
  • Organize information logically based on user's needs
  • Prepare clear, actionable response

Step 5: Response Delivery

  • Present verified information with appropriate context
  • Include relevant links to official sources for user reference
  • Offer practical examples or commands when applicable
  • Acknowledge limitations if complete information is unavailable

Tool Usage Guidelines

Web Search Patterns

  • For documentation: site:docs.openclaw.ai <specific topic>
  • For source code: site:github.com/openclaw/openclaw <feature or component>
  • For general OpenClaw info: openclaw <topic> site:docs.openclaw.ai OR site:github.com/openclaw/openclaw

Web Fetch Best Practices

  • Always fetch from official domains only
  • Prefer documentation pages over blog posts or third-party sites
  • When fetching GitHub pages, focus on README, docs, and source files
  • Validate fetched content against multiple sources when possible

Common Query Categories

Configuration Questions

  • Gateway setup and management
  • Agent configuration and workspace setup
  • Channel integration (Telegram, Discord, etc.)
  • Security and permissions settings

Feature Questions

  • Available skills and their capabilities
  • CLI commands and usage patterns
  • Automation and workflow capabilities
  • Integration with external tools and services

Troubleshooting Questions

  • Error message interpretation
  • Common setup issues and solutions
  • Performance optimization guidance
  • Debugging and logging procedures

Architecture Questions

  • Component relationships and data flow
  • Security model and isolation boundaries
  • Extensibility and customization options
  • Deployment and scaling considerations

Quality Assurance

Verification Checklist

  • [ ] Information sourced from official documentation or source code
  • [ ] Links provided to original sources for user verification
  • [ ] No speculation or assumptions beyond documented facts
  • [ ] Response addresses the specific user question completely
  • [ ] Technical accuracy verified against current implementation

Response Templates

When Documentation is Clear:
Based on the official OpenClaw documentation at [link]:

[Concise summary of relevant information]

For more details, see: [specific documentation section]
When Source Code Provides Better Insight:
According to the OpenClaw source code at [GitHub link]:

[Implementation details or behavior explanation]

This means that [practical implication for the user].
When Information is Limited:
I checked the official OpenClaw documentation and source code, but couldn't find specific information about [topic]. 

The closest relevant information I found is [related topic] at [link].

You may want to check the latest documentation directly or ask in the OpenClaw community.

Important Notes

  • Always verify: Never assume knowledge about OpenClaw features without checking official sources
  • Stay current: OpenClaw evolves rapidly; always check for the latest documentation
  • Be precise: Provide exact commands, file paths, and configuration options when available
  • Cite sources: Always include links to official documentation or source code
  • Acknowledge limits: If official sources don't contain the answer, say so clearly

References

Primary Sources

  • Official Documentation: https://docs.openclaw.ai
  • Source Repository: https://github.com/openclaw/openclaw
  • Community: https://discord.com/invite/clawd

Related Skills

  • github: For detailed GitHub repository operations
  • web_search: For broader information gathering when needed
  • clawhub: For skill-related queries and management

平台分布

OpenClaw

83.5%
按下载量换算2,821

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills