A SKILL.md Edit Is a Production Change — Even When No Code Changed

OpenClaw skills are not passive documentation. They change when tools are invoked and how work is performed. A local skill in your workspace has the highest loading precedence, so it can silently replace a bundled or managed version — without touching application code. That makes any edit to a SKILL.md a production change, even if no code changed.

Why It Matters

OpenClaw's skills documentation notes that the skills watcher is enabled by default. A modified SKILL.md can refresh the session snapshot on the next agent turn. The security guidance explicitly recommends treating skill folders as trusted code — because they can request filesystem access, network calls, credential handling, or approval workflows.

Audit Before You Change

Before you modify any skill, capture what the agent can actually load. Run these commands and save the output:

openclaw skills list --json
openclaw skills check --agent main --json
openclaw skills info SKILL_NAME --agent main --json

These give you the effective sources and hashes — useful as release evidence. Keep skill roots under version control and review any new filesystem, network, credential, or approval-related instructions in the diff.

Disable Mid-Session Changes

If you don't want skills swapped mid-session, the documented configuration supports disabling automatic watching:

{
  "skills": {
    "load": {
      "watch": false
    }
  }
}

Test Like It's Production

When you do activate reviewed changes, start a controlled new session and run one bounded task. Confirm the expected tool sequence, permissions, and final outcome. A successful load only proves the skill is eligible — not that its behavior is safe.

The Takeaway

Which files in your OpenClaw setup can currently change agent behavior without passing your normal code-review process? Treat every SKILL.md like a production deployment: audit, version, test, and record what you changed.