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

コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。

ローカルで確認しますか？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

このリポジトリのすべてを見る

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