claude-code - 💡(How to fix) Fix Plugin skills not appearing in slash command autocomplete [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#45510Fetched 2026-04-09 08:03:45
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
0
Timeline (top)
labeled ×6closed ×1commented ×1

Skills installed via plugins (e.g., example-skills@example) do not appear in the / slash command autocomplete list in the Claude Code CLI.

Root Cause

Skills installed via plugins (e.g., example-skills@example) do not appear in the / slash command autocomplete list in the Claude Code CLI.

Fix Action

Workaround

Creating stub .md files in ~/.claude/commands/ allows them to appear in autocomplete, but this is a manual workaround and disconnects the stub from the actual plugin skill.

Code Example

{
     "enabledPlugins": {
       "example-skills@example": true
     }
   }
RAW_BUFFERClick to expand / collapse

Summary

Skills installed via plugins (e.g., example-skills@example) do not appear in the / slash command autocomplete list in the Claude Code CLI.

Environment

  • Claude Code version: 2.1.87
  • Platform: macOS (darwin 25.3.0)
  • Shell: zsh

Steps to Reproduce

  1. Install a plugin with skills via enabledPlugins in settings.json:
    {
      "enabledPlugins": {
        "example-skills@example": true
      }
    }
  2. Verify the plugin is installed in ~/.claude/plugins/installed_plugins.json and skills exist at ~/.claude/plugins/cache/<org>/<plugin>/<version>/skills/
  3. Open Claude Code CLI and type /
  4. Observe that plugin skills (e.g., example-skills:plan, example-skills:gemini) do not appear in the autocomplete list

Expected Behavior

Plugin skills should appear in the / slash command autocomplete, similar to how locally defined commands in ~/.claude/commands/ appear.

Actual Behavior

Plugin skills are completely absent from the autocomplete list. However, they do work correctly when invoked programmatically within a conversation (they appear in the system's available skills and can be called via the Skill tool internally).

Additional Context

  • Skills stored in ~/.claude/commands/ (local markdown files) correctly appear in autocomplete
  • The autocomplete appears to only read from the commands/ directories, not from ~/.claude/plugins/cache/
  • Typing /example- or the full skill name does not produce any autocomplete suggestions
  • The skills themselves function correctly once a session is active

Workaround

Creating stub .md files in ~/.claude/commands/ allows them to appear in autocomplete, but this is a manual workaround and disconnects the stub from the actual plugin skill.

extent analysis

TL;DR

The most likely fix involves updating the autocomplete mechanism to include skills from plugins, potentially by modifying the settings.json or the plugin installation process.

Guidance

  • Verify that the enabledPlugins setting in settings.json is correctly configured and that the plugin is installed in ~/.claude/plugins/installed_plugins.json.
  • Check the ~/.claude/plugins/cache/<org>/<plugin>/<version>/skills/ directory to ensure that the skills exist and are correctly formatted.
  • Consider creating a feature request to update the autocomplete mechanism to include skills from plugins, as the current workaround of creating stub .md files in ~/.claude/commands/ is manual and disconnected from the actual plugin skill.
  • Investigate the possibility of modifying the commands/ directory to include symbolic links to the plugin skills, which could potentially allow them to appear in the autocomplete list.

Example

No code snippet is provided as the issue does not imply a specific code-based solution.

Notes

The issue appears to be related to the autocomplete mechanism not reading from the ~/.claude/plugins/cache/ directory, and instead only reading from the commands/ directories. This limitation may be a design choice or a bug, and further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Creating stub .md files in ~/.claude/commands/ allows plugin skills to appear in autocomplete, although this is a manual process and may not be ideal. This workaround is recommended as it provides a temporary solution until a more permanent fix can be implemented.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING