Status: doc-verified ☑ — matches the openclaw.ai skills docs; not executed here.
OpenClaw's native extension surface is the same one we ship: directories
of SKILL.md files. No MCP config needed — the CLI-wrapping skills work
as-is.
# puts `watch-skill` on PATH, which the skills call
uv tool install "watch-skill[standard]" # or: pipx install "watch-skill[standard]"
watch-skill doctorPoint OpenClaw's skill discovery at the skills library (it scans any
configured root for SKILL.md, up to 6 levels deep). In your OpenClaw
config, under skills.load:
{
"skills": {
"load": {
"extraDirs": ["C:\\path\\to\\watch-skill\\adapters\\claude-skill\\skills"]
}
}
}That picks up all of them: watching-videos, asking-with-evidence,
the-loop, learning-from-mistakes, extracting-structure,
video-memory, sharing-results, configuring-vision,
recovering-from-errors, plus /watch.
- Ask: "Watch https://www.youtube.com/watch?v=aqz-KE-bpKQ — what
happens at 0:10?" — the
watching-videosskill should fire and runwatch-skill watch. - Check the reply cites
t=MM:SStimestamps from the report. - Follow up: "what color is the bird?" — the
asking-with-evidenceskill should runwatch-skill ask, not re-watch.
- Our frontmatter carries
name,description,version,license,allowed-tools. OpenClaw ignores keys it doesn't know; the trigger description is what matters. - The skills call the
watch-skillCLI, so theuv tool install .step (orpip install watch-skill) is what makes them portable here.
