openclaw-metadata¶
Validate metadata.openclaw fields against the OpenClaw spec
| Severity | warning (auto) |
| Autofix | - |
| Since | v0.1.0 |
| Repo Types | agentskills, dot-claude, marketplace, single-plugin |
| Category | OpenClaw |
Why¶
metadata.openclaw drives real runtime behavior: platform gating (os),
activation requirements (requires), and dependency installation
(install). OpenClaw validates it loosely and silently ignores fields
it doesn't recognize — an invalid kind, os, or archive value
produces no error, the skill just quietly misbehaves (e.g. an installer
that never appears in openclaw skills info). This rule catches those
mistakes at author time.
See the OpenClaw skills spec for the authoritative field list.
Allowed values¶
| Field | Values |
|---|---|
install[].kind |
brew, node, go, uv, download |
os, install[].os |
darwin, linux, win32 |
install[].archive |
tar.gz, tar.bz2, zip |
requires keys |
bins, anyBins, env, config |
How to fix¶
Correct the flagged field to an allowed value. Common cases: npm isn't
a kind — use kind: node with a package; kind: download requires a
url; there is no apt/dnf kind (use brew, which also runs on
Linux, or download).
This rule only fires when metadata.openclaw is present — removing the
block suppresses it entirely.
Configuration¶
Run skillsaw explain openclaw-metadata to see this documentation and the rule's effective configuration in your terminal.