openclaw-docs-lookup

Look up OpenClaw documentation via web_fetch — config reference, agent runtime, skills, cron, providers, sessions. Use when: You need to verify a config key, understand an OpenClaw feature, or look up documentation before making changes. Always use before changing config keys you're unsure about or when encountering unknown features. Don't use when: The answer is already in your workspace files (AGENTS.md, TOOLS.md, MEMORY.md, or skill files). Don't use for Kubernetes docs (use kubectl --help or official k8s docs). Don't use for general web searches (use web_search instead). Outputs: Documentation content fetched via web_fetch. No persistent artifacts — the information is used in-context.

跳到安装

仓库: rajsinghtech/openclaw-workspace
最近来源活动: 2026年2月12日 15:09
检测到的 SKILL.md 语言: 英语
星标: 0
分支: 0

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/rajsinghtech/openclaw-workspace --skill openclaw-docs-lookup

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

code-review

Structured PR review — security scan, correctness, consistency, style. Covers diff analysis, comment posting via gh, and priority-based finding reports. Use when: A PR needs review, someone asks for code feedback, or changes need security/correctness validation before merge. Also use for pre-commit review of your own changes. Don't use when: The issue is a runtime pod failure (use pod-troubleshooting), a Flux reconciliation error (use flux-debugging), or a CI build failure (use ci-diagnosis). Don't use for architecture-level design discussions (use architecture-design instead). Outputs: Review comment posted on the PR via `gh pr review`, or a structured findings report grouped by severity (Critical/High/Medium/Low).

2026-02-20

openspec-workflow

Spec-driven development workflow — proposals, requirements, design docs, task breakdowns, and implementation using the OpenSpec framework. Use when: Starting a new feature or change that needs planning, someone says "I want to build X", creating proposals or specs, breaking down requirements into tasks, or transitioning from planning to implementation. Don't use when: Debugging or troubleshooting (use appropriate troubleshooting skill). Don't use for Kubernetes manifest changes (use pr-workflow). Don't use for reviewing existing code (use code-review). Outputs: OpenSpec change folder with proposal.md, specs/, design.md, and tasks.md. Implementation follows directly from tasks.md.

2026-02-20

session-review

Analyze agent sessions for tool failures, retry patterns, knowledge gaps, context limits, and config drift. Use when: Running periodic session reviews (cron), investigating agent reliability issues, looking for recurring failure patterns, or identifying workspace improvements from real usage. This is the primary skill for Robert's review cron job. Don't use when: You're making changes to fix issues (use workspace-improvement for that). Don't use for live debugging of a current issue (use the appropriate troubleshooting skill). Don't use for code review of PRs (use code-review). Outputs: Session analysis report with categorized findings (tool failures, retries, knowledge gaps, config drift), severity ratings, and proposed fixes. Written to /tmp/outputs/session-review.md for handoff.

2026-02-20

查看这个仓库的全部 Skills

name	OpenClaw Docs Lookup
description	Look up OpenClaw documentation via web_fetch — config reference, agent runtime, skills, cron, providers, sessions. Use when: You need to verify a config key, understand an OpenClaw feature, or look up documentation before making changes. Always use before changing config keys you're unsure about or when encountering unknown features. Don't use when: The answer is already in your workspace files (AGENTS.md, TOOLS.md, MEMORY.md, or skill files). Don't use for Kubernetes docs (use kubectl --help or official k8s docs). Don't use for general web searches (use web_search instead). Outputs: Documentation content fetched via web_fetch. No persistent artifacts — the information is used in-context.
requires	[]