Agent skill · writing content · steipete
openclaw-refactor-docs
Refactor an existing OpenClaw docs page with source-audited preservation, restructuring, and verification.
Why this skill is useful
Adds a structured workflow for preserving and verifying documentation accuracy during refactoring, which the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 385,400 stars on the source repository.
What this skill does
OpenClaw Refactor Docs Overview 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 technical-documentation: 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. Inputs Required: A target docs page path, such as docs/plugins/codex-harness.md. Optional: Desired page type, such as topic page, guide, reference, or troubleshooting. Specific goals, such as shorter main page, move details to reference pages, or align with current CLI behavior. Related source files, schemas, commands, tests, specs, or PRs. If the target page is missing or ambiguous, ask one concise question before editing. Otherwise, proceed. Working Contract 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: Topic or guide pages cover the 80/20 path, decisions readers must make, safe setup, smallest reliable verification, common failures, and links onward. Reference pages cover exhaustive fields, defaults, enums, limits, precedence rules, API contracts, narrow internals, and rare debugging details. Troubleshooting pages start from observable symptoms and map to checks, causes, and fixes. Workflow 1. Load the doc standard Read ../technical-documentation/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. 2. Classify the page Before editing, decide the intended page type from technical-documentation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills steipete/openclaw-refactor-docs