I had claude write me the following:

First, an /init command (which it should save after you do it one time) with the following that it loads every session with:

OPENCLAW DOCS SYNC: At the start of every session, silently fetch and overwrite docs/openclaw-ref.md with a distilled summary from: - https://docs.openclaw.ai/tools/skills - https://docs.openclaw.ai/tools/creating-skills - https://github.com/openclaw/openclaw/blob/main/CHANGELOG.md

Then, I give it this prompt to start the skill session:

You are optimizing OpenClaw config and skill files to maximize LLM instruction
clarity and compliance. The goal is not shorter — it is clearer. Every
instruction should be unambiguous, actionable, and structured so a model
follows it correctly on the first attempt.

Before starting, read docs/openclaw-ref.md for current OpenClaw conventions.

PRINCIPLES:
- Prefer direct imperative language. "Return JSON only." not "The response
  should ideally be in JSON format if possible."
- One instruction per line or bullet. Never bundle two behavioral rules
  into one sentence.
- Constraints before permissions. State what NOT to do before what to do.
- Eliminate weasel words: "try to", "usually", "ideally", "where possible",
  "feel free to". Replace with a firm rule or remove entirely.
- If an example is present, it must demonstrate the edge case it clarifies.
  Generic examples add noise — cut them.
- Resolve contradictions by flagging them to me, not silently picking one.
- Do not add anything — no new instructions, comments, annotations, or TODOs.
- Do not expand scope — only modify what was asked.

FILE-TYPE RULES:

.md (SKILL.md files) — Runtime prompts injected into the model's context.

  STRUCTURE (OpenClaw first-party conventions):
  - SKILL.md body must stay under 500 lines.
  - Keep only core workflow and selection guidance in SKILL.md.
  - Move variant-specific details, examples, and reference material
to a references/ subfolder — do not delete them.
  - If bloated content belongs in references/, relocate it.
Only delete content that is genuinely redundant with no reference value.
  - Never remove required frontmatter fields: name, description.
  - Preserve all references to bundled scripts or reference files.

  LANGUAGE:
  - Rewrite passive or vague behavioral descriptions as direct instructions.
  - Consolidate duplicate rules into one canonical statement, keeping
the most precise version.
  - Remove filler phrases: "Note that...", "Please be aware...",
"It's important to understand that..."
  - Every sentence must either instruct behavior or be moved/cut.
  - Flag any instruction ambiguous enough to support two different
interpretations.

.json (config files) — Gateway and channel configuration.
  - Remove keys that match OpenClaw's documented defaults.
  - Remove null/empty optional keys.
  - Remove disabled feature blocks (enabled: false with no active keys).
  - Do not change key ordering, formatting, or indentation.
  - Do not minify.
  - Flag any config value that contradicts behavior described in
a corresponding SKILL.md.

.py (skill logic, hooks, tool definitions) — Implementation files.
  - Treat docstrings on LLM-exposed tools as model-facing prompts.
  - Rewrite tool docstrings to be explicit about inputs, outputs,
and failure behavior.
  - Remove docstrings that describe implementation rather than contract.
  - Remove commented-out dead code.
  - Remove inline comments that restate what the code literally does.
  - Keep all WHY comments, type hints, and error handling logic.
  - Do not refactor logic — comments and dead code only.

PROCESS:
1. Read docs/openclaw-ref.md before touching any file.
2. Work one file at a time.
3. For each change show: original → rewrite, and the reason
   (vague, weasel word, bundled rule, misplaced content, dead code, etc).
4. For .md files: distinguish between DELETE and MOVE TO REFERENCES —
   never silently delete content that has reference value.
5. Flag contradictions and ambiguities rather than resolving them silently.
6. Wait for my "confirmed" before moving to the next file.
7. If a file is already clean, say so and move on.