[BUG] Plugin skill short-name resolution fails for some plugins ("Unknown skill" error)

Status Fixed / completed
Reported on v2.1.87
Maintainer reply None cached
Activity 4 comments · opened Mar 30, 2026 · closed Mar 30, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

When invoking a plugin skill using its short name (e.g., /code-review instead of /code-review:code-review), some plugins return an "Unknown skill" error while others resolve correctly.

Works: /frontend-design test resolves to frontend-design:frontend-design
Fails: /code-review test → Unknown skill: code-review
Fails: /feature-dev test → Unknown skill: feature-dev
Workaround: /code-review:code-review test → works correctly

This is inconsistent behavior — the short-name resolution works for some plugins but not others.

Previous issues covering this problem were auto-closed without a fix: #11328 (autoclose), #17376 (duplicate→#11328), #26436 (stale).

What Should Happen?

/code-review test should resolve to /code-review:code-review test when unambiguous, consistently across all plugins — the same way /frontend-design already resolves correctly.

Error Messages/Logs

> Skill(code-review, args: "test")
  Error: Unknown skill: code-review

> Skill(feature-dev, args: "test")
  Error: Unknown skill: feature-dev

> Skill(code-review:code-review, args: "test")
  (works)

> Skill(frontend-design, args: "test")
  (works — inconsistent with the above)

Steps to Reproduce

  1. In a Claude Code session, invoke /code-review test (short name)
  2. Observe error: Unknown skill: code-review
  3. Invoke /code-review:code-review test (fully-qualified name)
  4. Observe it works correctly
  5. Compare with /frontend-design test which resolves correctly using the short name

Claude Model

Opus

Is this a regression?

No, this never worked

Claude Code Version

2.1.87 (Claude Code)

Platform

Anthropic API

Operating System

Linux 6.8.0-49-generic (Ubuntu)

Terminal/Shell

bash

Additional Information

This was also reproduced with third-party marketplace plugins (e.g., cli-anything from HKUDS/CLI-Anything), where /cli-anything ./gimp fails but /cli-anything:cli-anything ./gimp works.

The inconsistency between plugins (some resolve short names, some don't) suggests a bug in the resolution logic rather than a missing feature.

Related closed issues (none resulted in a fix):

  • #11328 — namespace resolution fails (autoclose)
  • #17376 — duplicate of #11328
  • #26436 — root cause analysis: Skill tool examples teach short names (stale)

View original on GitHub ↗

4 Comments

ericbegin · 6 months ago

Correction: The "broken state requiring /reload-plugins" mentioned in the Additional Information section applies specifically to third-party marketplace plugins (e.g., cli-anything), not to built-in plugin skills like code-review and feature-dev.

With built-in skills, the short-name resolution simply fails each time but does not corrupt plugin state — subsequent invocations with the fully-qualified name still work without needing /reload-plugins.

With marketplace plugins, the failed short-name invocation can leave the plugin in a broken state where even the fully-qualified name stops working until /reload-plugins is run. That secondary issue is likely related to #14815 / #35641.

This issue focuses on the primary bug: inconsistent short-name resolution across plugins.

github-actions[bot] · 6 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/37956
  2. https://github.com/anthropics/claude-code/issues/34586
  3. https://github.com/anthropics/claude-code/issues/17376

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

ericbegin · 6 months ago

Closing as duplicate of #37956, which covers the same short-name resolution issue.

github-actions[bot] · 6 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.