OpenClaw Skill Installed but Not Working? 3-Step Allowlist Fix (2026)

openclawskillsclawhubtroubleshootingallowlist

What this article solves

You ran openclaw skill install <name> but the skill never triggers. In most cases the skill is fine — it is blocked by allowlist, config wasn’t applied, or the gateway wasn’t restarted.

Here is a 3-step, verifiable flow with copyable commands.

3-step fix (copy/paste ready)

Step 1: Confirm the skill is installed

ls ~/.openclaw/skills/

If you see the directory (e.g., home-assistant), installation succeeded. If not, reinstall:

openclaw skill install <skill-name>

If the name is not found, double-check spelling and see the ClawHub Skill Security Guide for naming conventions.

Step 2: Check the plugin allowlist (plugins.allow)

OpenClaw does not load skills that are not explicitly allowed. Check:

openclaw config get plugins.allow

If your skill is missing, edit the config file:

# default config path
~/.openclaw/openclaw.json

Example:

{
  "plugins": {
    "allow": ["home-assistant", "github", "weather"]
  }
}

If you are unsure about config structure, see: OpenClaw Config Guide & Common Fixes.

Step 3: Restart the gateway and validate

Apply the change:

openclaw gateway restart
openclaw gateway status

Validation:

If there is still no response, check channel status: openclaw channels status (see Channel No-Reply Diagnosis).

Common mistakes (1-minute check)

Minimum evidence pack (for quick escalation)

Final takeaway

If you follow “install check → allowlist → restart + validate”, most skill issues are fixed in under 5 minutes.

If it still fails, use the evidence pack to debug config or channel layer (linked below).

Further reading

Core Guides (Recommended)

Was this article helpful?

💬 Comments