coworkplugins
Guide

Plugin installed but skills are missing: what to check

The plugin shows as installed but Claude never uses its skills. The documented causes, in check order.

By Arun BabuIntermediate

The plugin is installed, yet Claude behaves as if it is not there. The documented causes are a short list (October 2026 docs; CLI behavior verified on Claude Code v2.1.296).

1. The skill never matched your request

A skill triggers on its description field - the text Claude matches your request against. If you ask in words far from that description, the skill stays unused even though it is installed. Read the plugin's SKILL.md or README for its trigger phrases and ask in those terms. This is the most common cause and the only one that is not really a malfunction.

2. A reload is pending

New plugins load at session start. In Claude Code, /reload-plugins loads file changes without restarting (verified on v2.1.296 with init-scaffolded plugins); an already-open session elsewhere may simply predate the install. Start a fresh session.

3. The plugin is disabled, not installed

Disable and uninstall are different states: a disabled plugin stays visible in your list but loads nothing. claude plugin list shows the status per plugin; claude plugin enable name@marketplace flips it back. More in disable or remove safely.

4. Wrong scope

A plugin installed at project scope exists only in that project. If you installed it in one repo and expect it everywhere, install at user scope instead. Plugin scopes explained.

5. Sync never carried it to your other surface

Code-to-Cowork sync is one-way, needs v2.1.273+, and excludes API-key and Bedrock sign-ins. If the skills exist in Code but not Cowork, work through plugin not syncing.

6. The skills were never in the package

Some plugins are connector-only or command-only. Check the plugin's README for its component list before assuming skills are missing - if none ship, none will appear. How components differ: plugins vs skills vs connectors.

Sources

Read more