$ loading_
Refactor OpenClaw docs pages with source-checked preservation, clearer structure, and verification.
The material indicates a prompt-only documentation refactoring skill with no required secrets and no declared remote endpoints, resulting in a low overall risk profile. Combined with its GitHub open-source source and very strong community adoption, no concrete high-risk red flags are evident, though its workflow mentions reading related docs and running local documentation commands, so execution boundaries should still be verified in practice.
The material explicitly states that no keys or environment variables are required, and the README does not request login, tokens, or authentication to external services; no credential collection or misuse indicators are present.
The material declares no remote endpoints, and the README focuses on a local documentation refactoring workflow; it does not state that user data is sent to external services, and no unknown egress destination is indicated.
The README explicitly mentions 'Run `pnpm docs:list` when available,' indicating the workflow may trigger local command execution; this is a normal capability for such tools, and no request for excessive system privileges or execution unrelated to the stated function is shown.
This skill is intended to refactor a target documentation page and asks to read the target page plus related entry/reference pages, which is a normal scope of access for local project docs; the material does not describe broad data harvesting or excessive access beyond the documentation context.
The source is an open-source GitHub repository with extremely strong community adoption (about 377k stars), providing good auditability and source credibility; the unspecified license and unknown maintenance status are minor review gaps but do not by themselves constitute a high-risk red flag.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "openclaw-refactor-docs" skill from askskill: 1. Download https://raw.githubusercontent.com/openclaw/openclaw/main/.agents/skills/openclaw-refactor-docs/SKILL.md 2. Save it as ~/.claude/skills/openclaw-refactor-docs/SKILL.md 3. Reload skills and tell me it's ready
Please refactor this OpenClaw documentation page. Preserve only information verified by the source code or current implementation, remove unverified claims, reorganize it into Overview, Prerequisites, Steps, Examples, and FAQ, and list the evidence you checked plus any points that still need confirmation.
A clearer, source-audited documentation page with verification notes and a list of open questions.
This OpenClaw documentation page may be outdated. Compare it against the current source code, configuration options, and command usage, update outdated descriptions, preserve still-valid content, and add Change Notes and Verification Method sections at the end.
An updated document aligned with the current implementation, clearly showing what changed and how it was verified.
Please turn this poorly structured OpenClaw document into a more readable version: merge duplicate content, split overly long paragraphs, add clear headings and action order, and ensure every technical detail can be traced back to the original text or source code without adding unverified content.
A cleaner, deduplicated, and traceable documentation rewrite that is easier to read.
Use this skill when the user gives a target OpenClaw docs page and asks to rewrite, refactor, reorganize, split, shorten, or improve it.
This skill builds on openclaw-docs: use that skill for style, page types,
structure, examples, discoverability, and verification. This skill adds the
rewrite workflow needed to avoid losing accurate behavior during a major docs
refactor.
Required:
docs/plugins/codex-harness.md.Optional:
If the target page is missing or ambiguous, ask one concise question before editing. Otherwise, proceed.
Refactor the target page to be more useful, concise, and comprehensive within its stated scope.
Do not treat a rewrite as permission to discard behavior facts. Preserve, verify, move, or explicitly retire existing material. Incorrect docs are worse than verbose docs.
Prefer this split:
Read ../openclaw-docs/SKILL.md first. Apply its page-type, style,
examples, navigation, and verification guidance throughout the refactor.
Run pnpm docs:list when available, then read only the target page and the
likely entry points, references, or related pages needed for the refactor.
Before editing, decide the intended page type from openclaw-docs.
If the current page mixes page types, choose the main page type and plan where the other material belongs:
Create a working inventory from the old page before rewriting. Include:
For each fact, choose one outcome:
Do not infer defaults, permissions, policy, timeout behavior, or safety posture from names or intent. Verify them.
Use the nearest authoritative source for each behavior-sensitive claim:
…
Fetch GitHub issues, create fixes, open PRs, and handle reviews.
Convert text to speech locally and offline with sherpa-onnx, no cloud needed.
Regenerate OpenClaw release changelog sections from Git history before releases.
Prepare and verify OpenClaw stable or beta releases and release notes.
Automate web page workflows, login checks, tab handling, and recovery steps.
Verify an OpenClaw release is fully published and working across all channels.
Deeply review code and fix only small, high-confidence OpenClaw bugs.
Review, triage, and manage OpenClaw issues and pull requests faster.
Find and fix small high-confidence OpenClaw bugs ready to land.
Draft OpenClaw release announcements and testing guidance from release evidence.
Run, debug, monitor, and summarize OpenClaw release CI workflows.
Investigate test memory growth, heap leaks, and OOM root causes.