Orientation.
Start with the registry, the runtime, and the manifest. These three documents define what a skill may do before it is invoked.
OpenClaw operation is not physical claw control. It is the disciplined use of installable skills: read the source, confirm the runtime, then run the narrowest module that matches the task.
The operator should be able to answer three questions before invoking a skill: what it changes, what it reads, and how it reports failure.
Install & Inspect.
A skill enters the manual as a package, not as folklore. The install command, source URL, version, and required tools must all be visible.
Copy the install line from the registry entry. Then open the module source and read the frontmatter before you trust the prose below it.
Runtime labels are operational facts. If a module is marked for OpenClaw and Claude Code, do not imply support for Codex, Cursor, or another harness unless the source says so.
{
"name": "frontend-design",
"runtime": ["openclaw", "claude-code", "cursor"],
"install": "clawhub install steipete/frontend-design",
"source": "github.com/openclaw/skills"
}Invoke Safely.
Advanced use is about boundaries: inputs, tools, credentials, and rollback. A module should make scope narrower, not blurrier.
Declare the task in the smallest form the skill can execute. Provide the exact file, service, or URL it needs, and withhold unrelated context.
Side-load patterns reduce redundancy. If the primary step lacks context, the helper step will not compensate automatically. Reserve them for flows with explicit inputs, reversible outputs, and declared dependencies.
Assess Fit.
Before running a module, classify the task by domain, side effects, required tools, and recovery path.
Class A: read-only lookup. Class B: local file edits. Class C: browser or service interaction. Class D: credentialed automation. Class E: publishing, deployment, or irreversible external effects.
Most failures come from a mismatch between task class and module scope. Treat unclear class boundaries as a reason to inspect, not to improvise.
Attest & Record.
The final step is evidence. A skill is ready for the registry only when source, install path, runtime support, and verification notes agree.
Record the module name, author, version, runtime labels, source URL, and a short verification note. Keep the note factual: what was installed, what ran, and what remains untested.
Passing does not mean prestige. It means the next operator can reproduce the result without decoding the Academy voice first.