claude-code - 💡(How to fix) Fix Plugin skills discoverable but not invocable via Skill tool [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46079Fetched 2026-04-11 06:29:31
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×5commented ×1

Skills defined in skills/*/SKILL.md within a custom org plugin appear correctly in the Cowork slash command menu (under a "Plugin name" section). However, invoking them — either by clicking in the menu or typing /skill-name — returns:

Unknown skill: plugin-name:skill-name

The Skill tool cannot resolve plugin skills. Only anthropic-skills:* skills work via the Skill tool.

Root Cause

Skills defined in skills/*/SKILL.md within a custom org plugin appear correctly in the Cowork slash command menu (under a "Plugin name" section). However, invoking them — either by clicking in the menu or typing /skill-name — returns:

Unknown skill: plugin-name:skill-name

The Skill tool cannot resolve plugin skills. Only anthropic-skills:* skills work via the Skill tool.

Fix Action

Workaround

Add a skills table to the plugin's CLAUDE.md that maps trigger phrases to file paths. Claude reads the SKILL.md file directly via the Read tool when the Skill tool fails. This works but adds an unnecessary failure/retry step to every skill invocation.

Code Example

Unknown skill: plugin-name:skill-name
RAW_BUFFERClick to expand / collapse

Description

Skills defined in skills/*/SKILL.md within a custom org plugin appear correctly in the Cowork slash command menu (under a "Plugin name" section). However, invoking them — either by clicking in the menu or typing /skill-name — returns:

Unknown skill: plugin-name:skill-name

The Skill tool cannot resolve plugin skills. Only anthropic-skills:* skills work via the Skill tool.

Reproduction

  1. Create an org plugin with skills in skills/*/SKILL.md (standard structure, valid YAML frontmatter)
  2. Deploy via Claude Team Plan admin as an org plugin
  3. Open Cowork — skills appear in the / slash command menu under the plugin name
  4. Click any skill or type /skill-name
  5. Result: "Unknown skill: plugin-name:skill-name"

Expected behavior

Plugin skills that appear in the slash command menu should be invocable via the Skill tool, the same way anthropic-skills:* skills work.

Workaround

Add a skills table to the plugin's CLAUDE.md that maps trigger phrases to file paths. Claude reads the SKILL.md file directly via the Read tool when the Skill tool fails. This works but adds an unnecessary failure/retry step to every skill invocation.

Environment

  • Cowork (claude.ai)
  • Custom org plugin deployed via Claude Team Plan admin
  • GitHub-hosted plugin repo
  • Skills use standard skills/*/SKILL.md structure with YAML frontmatter

🤖 Generated with Claude Code

extent analysis

TL;DR

The issue can be worked around by adding a skills table to the plugin's CLAUDE.md file that maps trigger phrases to file paths, allowing the Skill tool to invoke plugin skills.

Guidance

  • Verify that the skills are defined correctly in the skills/*/SKILL.md files within the custom org plugin, with valid YAML frontmatter.
  • Check that the plugin is deployed correctly via the Claude Team Plan admin and appears in the Cowork slash command menu.
  • To mitigate the issue, add a skills table to the plugin's CLAUDE.md file, mapping trigger phrases to file paths, as described in the provided workaround.
  • Test the workaround by invoking a plugin skill via the Skill tool after adding the skills table to the CLAUDE.md file.

Example

No code snippet is provided as it is not clearly supported by the issue, but the skills table in the CLAUDE.md file should map trigger phrases to file paths, similar to how the Read tool reads the SKILL.md file directly.

Notes

The workaround adds an unnecessary failure/retry step to every skill invocation, but it allows the Skill tool to invoke plugin skills. The root cause of the issue is that the Skill tool cannot resolve plugin skills, only anthropic-skills:* skills work via the Skill tool.

Recommendation

Apply the workaround by adding a skills table to the plugin's CLAUDE.md file, as it allows the Skill tool to invoke plugin skills, albeit with an additional step.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Plugin skills that appear in the slash command menu should be invocable via the Skill tool, the same way anthropic-skills:* skills work.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Plugin skills discoverable but not invocable via Skill tool [1 comments, 2 participants]