Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Slash command autocomplete doesn't show custom skills from ~/.claude/skills/ [1 comments, 1 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#49103•Fetched 2026-04-17 08:50:48
View on GitHub
Comments
1
Participants
1
Timeline
5
Reactions
0
Author
maxreallycantcodemaxreallycantcode
Participants
maxreallycantcodemaxreallycantcode
Timeline (top)
labeled ×3closed ×1commented ×1

The / autocomplete dropdown in the input bar does not list any custom skills from ~/.claude/skills/ or installed plugin skills. Only built-in commands (schedule, btw, rewind) appear.

Root Cause

The / autocomplete dropdown in the input bar does not list any custom skills from ~/.claude/skills/ or installed plugin skills. Only built-in commands (schedule, btw, rewind) appear.

Fix Action

Workaround

Skills ARE loaded into the model context and work when:

  • The model invokes them via the Skill tool (e.g. user says "run /lint")
  • The model auto-triggers them based on skill description matching

The issue is specifically with the UI autocomplete — user cannot browse or directly invoke custom skills from the input bar.

RAW_BUFFERClick to expand / collapse

Description

The / autocomplete dropdown in the input bar does not list any custom skills from ~/.claude/skills/ or installed plugin skills. Only built-in commands (schedule, btw, rewind) appear.

Environment

  • Claude Code v2.1.110
  • macOS (Darwin 25.4.0)
  • 70 skill directories in ~/.claude/skills/
  • 13 plugins enabled via settings.json

Steps to Reproduce

  1. Create skills in ~/.claude/skills/<name>/SKILL.md with valid frontmatter (name, description, user-invokable: true)
  2. Restart Claude Code
  3. Type / in the input bar
  4. Only built-in commands appear — no custom skills or plugin skills are listed

Expected Behavior

Custom skills with user-invokable: true should appear in the / autocomplete dropdown, filterable by typing (e.g. /li should show lint).

Actual Behavior

Only 3 built-in commands show: schedule, btw, rewind. Typing further (e.g. /d) shows no matches from custom skills.

Workaround

Skills ARE loaded into the model context and work when:

  • The model invokes them via the Skill tool (e.g. user says "run /lint")
  • The model auto-triggers them based on skill description matching

The issue is specifically with the UI autocomplete — user cannot browse or directly invoke custom skills from the input bar.

Additional Context

  • All 70 skill directories contain valid SKILL.md files with YAML frontmatter
  • Previously had 22 broken symlinks (to /tmp/gstack-install) which were removed — did not fix the issue
  • Plugin skills (e.g. from frontend-design, hookify, telegram) also don't appear
  • ~/.claude/commands/ (legacy format) contains 2 .md files — these also don't appear

extent analysis

TL;DR

The issue can be resolved by verifying the user-invokable frontmatter in the SKILL.md files and checking the plugin configurations to ensure custom skills are properly registered.

Guidance

  • Check the SKILL.md files in ~/.claude/skills/ for correct YAML frontmatter, specifically the user-invokable: true field, to ensure custom skills are marked as invokable.
  • Review the settings.json file to verify that the 13 enabled plugins are correctly configured to register their skills.
  • Investigate the difference in behavior between the Skill tool invocation and the UI autocomplete to identify potential discrepancies in skill registration or loading.
  • Consider checking the legacy ~/.claude/commands/ directory to ensure that the 2 .md files are not causing conflicts with the new skill format.

Example

No code snippet is provided as the issue seems to be related to configuration and file formatting rather than code.

Notes

The issue might be related to the transition from the legacy ~/.claude/commands/ format to the new ~/.claude/skills/ format, and ensuring that all skills are properly registered and configured.

Recommendation

Apply a workaround by manually verifying the user-invokable frontmatter in the SKILL.md files and checking the plugin configurations, as the issue seems to be related to skill registration and configuration rather than a version-specific bug.

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…
#vector store#embedding generation#cache error#pipeline error#runtime error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING