clawhub skill not working

[lucid pulsar]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[smoky stone]

What you’re seeing usually comes down to (a) skill eligibility and/or (b) session caching / wrong install location.

1) Make sure the skill is actually eligible (not just installed)

openclaw skills list shows everything found. The agent only gets the eligible skills injected into its system prompt.

Run:

openclaw skills list --eligible --verbose
openclaw skills check

If your ClawHub skill is not in --eligible, it’s being gated (common reasons: missing required CLI binary on PATH, missing env var/API key, OS mismatch, or a required config flag is off). Then run:

openclaw skills info <skill-name>

That output will tell you exactly what’s missing (bins, env, config, os).

2) Start a new session after installing skills

OpenClaw snapshots the eligible skills when the session starts. If you installed the skill after you already had a chat going, the agent won’t see it until a new session.

In chat, send /new (or restart the gateway).

3) Verify you installed into the same workspace the agent is using

ClawHub installs into ./skills under your current directory by default (unless it falls back to your OpenClaw workspace). It’s easy to install into the “wrong” folder.

Check your workspace:

openclaw config get agents.defaults.workspace

Then install explicitly into that workspace (or cd there first), e.g.:

clawhub install <skill-slug> --workdir "<that-workspace-path>"

If you paste these outputs, I can tell you exactly which case it is

1. openclaw --version
2. openclaw skills list --eligible --verbose
3. openclaw skills check

Docs that match this behavior:

• https://docs.openclaw.ai/tools/skills
• https://docs.openclaw.ai/tools/clawhub
• https://docs.openclaw.ai/cli/skills

[smoky stone]

There isn’t a separate “skills log” stream — skill loading/eligibility shows up in the normal Gateway logs.

Best “why can’t my agent use this skill?” view (usually enough)

These commands are more useful than logs because they tell you exactly what’s missing:

openclaw skills check
openclaw skills list --eligible --verbose
openclaw skills info <skill-name>

Tail logs and filter for your skill name

If the Gateway is reachable (even in remote mode):

openclaw logs --follow --json | grep -i "<skill-name>"