Agent Skill

@yoooclaw/cli ships a set of Skills (SKILL.md) — natural-language descriptions of "which yoooclaw commands to call, and when" — so an Agent can drive the CLI on its own without you teaching it step by step.

Difference from the plugin form

In the openclaw plugin, these Skills are auto-registered via the skills field in openclaw.plugin.json and loaded automatically when the host starts. The standalone CLI has no host to do this for it — the Skills just sit in <pkg>/skills/ inside the npm package and need to be installed manually into the current Agent's skills discovery directory.

Built-in Skills

The CLI used to ship a separate Skill for notification queries and one per recording-processing workflow; with that many, they started competing for the same triggers. They've since been consolidated into 4 Skills split by routing role: queries all go through yoooclaw-context-query, recording processing all goes through yoooclaw-recordings-process, and light-effect rules and tunnel debugging each keep their own. The old yoooclaw-notification-query, yoooclaw-recording-query, yoooclaw-recording-meeting-minutes, yoooclaw-recording-interview, yoooclaw-recording-entity-extraction, yoooclaw-recording-translation, and yoooclaw-recording-mindmap Skills have been merged into the new ones and are no longer shipped separately; running yoooclaw skills install --force after an upgrade also cleans up any of those old Skills you had installed.

Skill	Trigger scenario
yoooclaw-context-query	The sole entry point for querying data already synced to this machine — notifications/messages ("check my recent notifications"), recordings/transcripts ("what recordings are there"), saved/synced web pages ("what did I bookmark in the last day"), images ("sync images"), and cross-source "where was X mentioned." Covers list / search / get / answer / summarize / statistics intents, pure disk reads, no daemon needed. Generic live-web-search or current-events requests are explicitly excluded and routed to a web-search tool instead.
yoooclaw-recordings-process	Turns recordings/transcripts (or supplied text/files) into structured artifacts — meeting minutes, translation (with a two-stage glossary pass), Markdown mind maps, interview writeups, entity extraction. Shares one recording-source-location workflow and only loads the requested artifact branch. For recording lists, transcript lookup, content search, or existing summaries, use yoooclaw-context-query instead.
yoooclaw-lightrule-create	"Light up / blink when I get some kind of notification" — this kind of persistent rule is compiled, evaluated, and triggered by the cloud Notification Intelligence Agent; lightrule management commands call the cloud API directly and need an account API key configured (no local daemon required).
yoooclaw-tunnel-debug	"Phone pushes aren't arriving / notifications aren't syncing / check the tunnel / is the daemon alive" — combines doctor / auth status / daemon status / tunnel status / tunnel +test / gateway test / daemon logs to self-check the local environment, daemon, ingest auth, and Relay WebSocket link. Most of these commands need the daemon running.

yoooclaw-context-query splits its guidance into per-source reference docs (notifications / recordings / web-pages / images) and only loads the one that matches; yoooclaw-recordings-process does the same by artifact type. Neither Skill dumps every reference into context at once.

yoooclaw skills list                 # list the built-in Skills shipped with the package and their triggers
yoooclaw skills targets              # see the supported Agent targets and detection results

Installation

yoooclaw skills install              # auto-detect the single available Agent and symlink-install
yoooclaw skills install --agent codex
yoooclaw skills install --agent claude
yoooclaw skills install --copy       # copy instead of symlinking
yoooclaw skills install --target ~/.config/agent/skills --force

Flag	Description
--agent <agent>	The target Agent to install into; supports auto / claude / codex / custom, default auto.
--target <dir>	The target install directory; when passed, takes priority over auto-detection — suitable for any Agent compatible with the SKILL.md directory layout.
--copy	Copy the directory instead of creating a symlink. Use this when creating symlinks fails without admin rights on Windows.
--force	Overwrite if a Skill with the same name already exists at the target; otherwise it's skipped and reported under skipped.

auto mode only auto-installs when exactly one Agent is detected. If both Claude Code and Codex are detected, or neither is, the CLI returns the candidate targets and requires you to explicitly pass --agent or --target, to avoid silently installing into the wrong host.

Default directories for the built-in Agents:

Agent	Default skills directory
claude	~/.claude/skills
codex	${CODEX_HOME}/skills, or ~/.codex/skills if unset

Symlink by default vs. copy

By default, a symlink is created pointing into the package's skills/: after yoooclaw update self upgrades the CLI, the Skill content automatically follows the new version, with no reinstall needed. --copy produces a snapshot, which needs install --force again after an upgrade.

Once installed, restart the Agent session for it to be discovered. After that, just say something like "check my recent notifications," and the Agent will follow yoooclaw-context-query's guidance to call yoooclaw notification commands.

Idempotency and troubleshooting

• If you're not sure where it should be installed, first run yoooclaw skills targets to see detected and target.
• Re-running skills install (symlink mode) when the link already points to the same source is treated as "already installed" — no error, and it's not counted in skipped.
• In the output, installed lists Skills newly installed or already in place this run; skipped lists ones skipped because they already exist (with a reason) — add --force to overwrite.
• If creating a symlink fails with YOOOCLAW_STORAGE_UNAVAILABLE (EPERM/EACCES, most often on Windows), use --copy instead.