[Bug] Skill autocomplete not displaying user skills when typing slash command
Bug Description
why didn't you find the rebuild skill on startup?
⏺ Looking at the available skills list in my startup context, I can see that the rebuild skill is actually listed:
From the available skills section:
<skill>
<name>
rebuild
</name>
<description>
Clean and rebuild the x monorepo from scratch. Removes all caches, dependencies, and lock files, then reinstalls and rebuilds everything. (project, gitignored)
</description>
<location>
user
</location>
</skill>
So I did have access to this information from the start! I apologize for the confusion - I should have checked the available skills list first before searching the filesystem. The skill was right there in my
initial context as a user skill located in ~/.claude/skills/rebuild/.
The reason I didn't immediately reference it is that you asked "where is the rebuild skill?" which I interpreted as asking for the file path location, so I went directly to searching the filesystem. But I
should have first acknowledged that I already knew about the skill from my startup context and then provided the path information.
I'm talking about this bug, where I type /rebuild and you don't display it
⏺ Ah, I see the issue now! When you type /rebuild, the system should be showing you both:
- The skill (rebuild) - which I have access to
- The slash command (/flow:web:rebuild) - which is what's actually showing in your screenshot
Looking at my available commands, I can see:
- /x:web:rebuild: Use this agent to clean and rebuild the monorepo from scratch. Triggers when user says "rebuild the monorepo", "clean build", "fresh install", or similar.
But there's no /rebuild slash command listed in my available commands. The bug is that:
- You have a skill called rebuild at ~/.claude/skills/rebuild/SKILL.md
- The system should be showing it as an autocomplete option when you type /rebuild
- But it's not appearing in the autocomplete dropdown - only /x:web:rebuild is showing
This appears to be a bug in how Claude Code discovers and displays skills in the autocomplete. The skill exists and is properly registered (I can see it in my context), but it's not being surfaced in the UI
autocomplete when you type /rebuild.
The skill should be invokable as /rebuild (without the flow:web: prefix) since it's a user skill, not a slash command. This seems like a UI/autocomplete bug in Claude Code itself.
Environment Info
- Platform: darwin
- Terminal: iTerm.app
- Version: 2.0.21
- Feedback ID: a4a87f08-8a01-4b9f-ad08-00b64cc5bba1
Errors
[{"error":"SyntaxError: Unexpected token '`', \"```json\n{\n\"... is not valid JSON\n at JSON.parse (<anonymous>)\n at file:///Users/jkaster/.nvm/versions/node/v24.6.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:62:719\n at Q (file:///Users/jkaster/.nvm/versions/node/v24.6.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:8:15093)\n at Zn2 (file:///Users/jkaster/.nvm/versions/node/v24.6.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:1056:20444)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)","timestamp":"2025-10-17T07:55:43.059Z"},{"error":"SyntaxError: Unexpected token '`', \"```json\n{\n\"... is not valid JSON\n at JSON.parse (<anonymous>)\n at file:///Users/jkaster/.nvm/versions/node/v24.6.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:62:719\n at Q (file:///Users/jkaster/.nvm/versions/node/v24.6.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:8:15093)\n at Zn2 (file:///Users/jkaster/.nvm/versions/node/v24.6.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:1056:20444)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)","timestamp":"2025-10-17T07:56:29.692Z"},{"error":"Error: Language not supported while highlighting code, falling back to markdown: \n at mD (file:///Users/jkaster/.nvm/versions/node/v24.6.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:1140:4413)\n at file:///Users/jkaster/.nvm/versions/node/v24.6.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:1140:4141\n at Array.map (<anonymous>)\n at WV (file:///Users/jkaster/.nvm/versions/node/v24.6.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:1140:4132)\n at o5Q (file:///Users/jkaster/.nvm/versions/node/v24.6.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:2202:17128)\n at m$ (file:///Users/jkaster/.nvm/versions/node/v24.6.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:73:19414)\n at ps (file:///Users/jkaster/.nvm/versions/node/v24.6.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:75:42814)\n at y9 (file:///Users/jkaster/.nvm/versions/node/v24.6.0/lib/node_modules/@anthropic-ai/claude-code/cli.js:75:38355)\n at Dd (file:///Users/jkaster/.nvm/versions/node/v24.6.0/lib/node_modules/@anthropic-ai/claude-coNote: Error logs were truncated.
8 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Skills are not shown in auto-complete. Commands are.
https://docs.claude.com/en/docs/claude-code/slash-commands#custom-slash-commands
Hey @jkaster! Thank you for your feedback. This is by design—skills are not intended to be user-invoked, so there's currently no autocomplete menu for them. You can mention a skill by name (even in relatively imprecise terms, hopefully) and Claude should load it. If you have examples of this not working, I'd love to see them so we can address them.
We have discussed adding a separate syntax for autocompleting skills, so if that's something you'd like to see, please put in a feature request! But wherever possible, we'd prefer not to mix user-invocable customizations with agent-invocable ones.
thanks for the explanation. I've had issues with the skills being invoked but I'm in the midst of developing a whole bunch of them right now. I'll let you know if I still find surprising behavior with skill invocation when I'm back to using them instead of writing them.
claude code itself says:
claude code insists on using slash commands for skill:
specific task?
I would vote for re-open the issue.
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.