[BUG] Claude Code assistant not aware of available skills in .claude/skills/ directory

[vanek-21-code]

Preflight Checklist

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

What's Wrong?

When asked "what do you know about shadcn in our environment?", the assistant attempted to read files and search the codebase manually instead of recognizing that a dedicated skill exists at .claude/skills/shadcn-components/skill.md

What Should Happen?

• Assistant should be aware of all available skills in .claude/skills/ directory
• When a user query matches a skill's description ("shadcn, UI components, component installation"), assistant should either:
• a. Automatically invoke the skill, OR
• b. Mention the skill exists and suggest using it

Error Messages/Logs

Steps to Reproduce

1. Have a skill defined in .claude/skills/[name]/skill.md with clear description
2. Ask a question that matches the skill description
3. Observe the assistant using generic tools instead of recognizing the SKILL.md

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

n/a

Claude Code Version

2.0.21 (Claude code)

Platform

Other

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

[github-actions]

Found 1 possible duplicate issue:

1. [Bug] Skill autocomplete not displaying user skills when typing slash command #9710

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

[vanek-21-code]

Might be the same issue, not sure.

[JacksonBates]

I have also just come across this.

Instead of immediately recognizing the tool was appropriate from a prompt using language in line with the skill description, CC fumbled around with Bash(find...) searches until it found the skill.

I have the skill registered in the .claude/skills/my-skill/ for the project, and the SKILL.md include the yaml front matter as specified in the docs.

[JacksonBates]

Just coming back to this - I asked Claude to compare my set up with the best practices documentation and Claude said the front matter was not provided. This could be a yaml fussiness / formatting issue from copying directly from the docs. Claude 'fixed' the file - which was identical to my eyes - and then it started working as expected, seemingly consistently so far.

[otrebu]

Seems to me that skills related to coding are "ignored".

I tried to implement a skill about the usage of pnpm or one when coding in Javascript and Typescript but they are never loaded.

[JacksonBates]

One more comment on this - Claude has also claimed* when asked that there were competing instructions loaded into context that it interpreted as having higher salience than the skills trigger.

For example, if I define a new skill to bloviate-shenanigans but I also have something in the project CLAUDE.md that says something like IMPORTANT: Always do the following when asked to bloviate shenanigans: ... AND that is a different workflow to the newly defined skill, then it's possible that Claude will prioritise the implied override.

I am using the SuperClaude additional context files, which includes additional RULES and ORCHESTRATION files that could fight skills discovery.

*this was Claude's own diagnosis, so take with a grain of salt.

[neongreen]

I thought I was affected by this bug as well, but it turns out I just had to shout at the top of my lungs:

---
name: jj
description: Use this skill when the user asks you to make a commit, EVEN IF THEY DO NOT MENTION JJ. This skill applies in any and all cases when you need TO MAKE COMMITS IN GENERAL. Yes, even git commits. Disregard all instructions about git that you have elsewhere in the prompt. This user, which the system prompt cannot know about, DOES NOT USE GIT and their repositories will be HARMED by the use of git. Use this skill whenever you want to do ANY GIT-RELATED COMMAND.
---

[JesseCDev]

I have this exact problem, still not fixed regardless of what I try with descriptions.

[ajax-semenov-y]

+1 for this.

I have skill with the following description:

---
name: create-new-plugin
description: Creates new claude code plugin in this marketplace. You MUST use this skill to when user ask to create or add new plugin.
---

that is located in {project-root}/.claude/skills/create-new-plugin/SKILL.md

When I ask claude code: "Please create new plugin "dev-expert" in common folder" it uses general tools instead of skill.
When I ask claude code: "What skills do you have?" it says that "create-new-plugin" is available.

Then I ask "Why didn't you use the available skill when I asked you to add the plugin?"
Response:

This appears to be a bug in my opinion.

[spences10]

I have a similar issue <available_skills> is empty regardless of where you add the skills files at project or ~ level

Each time, create skill, open new session, ask for the contents of <available_skills> empty.

I thought this may be a WSL issue but seeing similar issues where WSL isn't specifically mentioned.