Attempts to improve skill discovery in Claude Code A single paragraph added to Claude Code's CLAUDE.md standing-instructions file raised the rate at which Claude opened the skill a task needed from 2 of 58 tasks to 47 of 58 on Haiku and from 7 of 58 to 40 of 58 on Sonnet, according to tests by developer ydmitry published on ydmitry.github.io. The paragraph instructs Claude to search its skills before writing code, a plan or a review, using either the author's skill-finder script or a plain grep over ~/.claude/skills, and to repeat the lookup after each file it reads; the two methods performed about equally well in the 897-skill test setup. The author notes the results come from test tasks rather than real work, and that a ten-task sample on Opus followed the same pattern. The same text as a page: ydmitry.github.io/skill-finder https://ydmitry.github.io/skill-finder/ . When using skills in Claude Code, I was concerned about the following things: - Mostly I needed to explicitly say which skill to use. - If in the middle of a session some skill appears to be useful, will it be auto-invoked? - If I need a specific reference, will it be added to the context? - Is the description enough for the LLM to decide if a skill needs to be used? - Also, what about skills with a badly written description, or skills too broad to describe with only one description? So that's why I decided to write a skill which helps with finding the needed skills: skill-finder. It appeared that the secret is in the CLAUDE.md instruction, and skill-finder itself can be replaced with grep. Claude Code rarely reads the skill a task needs unless it is told to look. In my tests it opened the needed skill in 2 of 58 tasks on Haiku and 7 of 58 on Sonnet. One paragraph in CLAUDE.md , the file of standing instructions Claude Code reads in every session, changed that to 47 and 40. A ten-task sample on Opus went the same way. The paragraph tells Claude to search its skills first, with my script skill-finder "the finder" or with a plain grep . Both did about equally well. These are test tasks, not real work. Jump to the instruction. the-instruction-to-put-in-claudemd - With many skills, Claude gets only their names and short descriptions, and rarely opens the right one. I tested with 897 skills, not with a few dozen. - When a team keeps its conventions in skills, Claude cannot follow a rule it has not read. - When a task needs a second skill that nobody could name at the start. For example, a review opens a file, and the file touches something that has its own rules. Put this in ~/.claude/CLAUDE.md or in a project's CLAUDE.md . Get the script first: git clone https://github.com/ydmitry/skill-finder ~/.claude/skills/skill-finder . Skills Before you write code, a plan, a review or any other piece of work, look the skills up. First read the request and every file it names. List what appears in them: the things, activities, materials and technologies, and what the finished thing is called. Look all of them up in one plain command no loop, no variable , one --phrase for each, two or three words in order. Run it as a command of its own, not joined to other commands: python3 ~/.claude/skills/skill-finder/scripts/find skills.py --phrase "