claude-code - 💡(How to fix) Fix User-defined skills (~/.claude/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#49641Fetched 2026-04-17 08:35:25
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×4commented ×1
RAW_BUFFERClick to expand / collapse

Environment

  • Claude Code v2.1.92
  • Model: Opus 4.6 (1M context)
  • OS: Linux (CentOS 7)

Issue

Built-in slash commands (e.g. /help, /skills) autocomplete when typing /, but user-defined skills installed under ~/.claude/skills/ (e.g. analyze-testbench, compare-testbench) do NOT appear in the autocomplete list.

Repro

  1. Create a skill at ~/.claude/skills/analyze-testbench/SKILL.md
  2. Start claude
  3. Type /anal and press Tab

Expected

/analyze-testbench appears as an autocomplete suggestion.

Actual

No suggestion shown. Typing the full command /analyze-testbench still invokes the skill correctly — only autocomplete is missing.

Note

Some environments also report /skills isn't available in this environment, which suggests the skills subsystem may be gated per-mode.

extent analysis

TL;DR

The issue can likely be resolved by ensuring the skills subsystem is properly enabled and configured for the current environment.

Guidance

  • Verify that the ~/.claude/skills/ directory is correctly populated with user-defined skills and that the SKILL.md files are properly formatted.
  • Check the Claude Code documentation to see if there are any specific configuration options or environment variables that need to be set to enable the skills subsystem.
  • Investigate the difference in behavior between built-in slash commands and user-defined skills to identify potential discrepancies in how they are handled by the autocomplete system.
  • Consider testing the skills subsystem in a different environment or mode to see if the issue is specific to the current setup.

Example

No code snippet is provided as the issue does not imply a specific code-related fix.

Notes

The issue may be related to the skills subsystem being gated per-mode, as hinted by the error message /skills isn't available in this environment. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Check the documentation and configuration options to ensure the skills subsystem is properly enabled and configured for the current environment, as this is the most likely cause of the issue.

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