Internal AI tools: a test runner for which Claude skill loads A developer built a small Python test runner that scores which Claude Agent Skill gets loaded for a given request, walking a skills folder, parsing each SKILL.md frontmatter (including folded and literal YAML descriptions), and exposing the library as a single Skill tool. In a test on an invented sales team, seven skills with one-sentence descriptions routed 40 messy requests correctly in 120 of 120 runs, while twenty overlapping skills scored 117 of 120. Rewriting the description of the one skill that missed fixed that request but moved two previously correct requests to the wrong skill in every run, which the developer cites as the reason the regression runner exists. Internal AI tools built on Claude Agent Skills have a step that nobody tests: the moment Claude reads every skill's name and description and picks one, or none. By the end of this post you will be able to point a small Python runner at your own skills folder and a list of labelled requests, and get a scorecard of which skill Claude loads and every miss. I had Claude build it for a test on an invented sales team; the code below is trimmed from the runner that ships. A drawing on an ivory ground: a sales team's skill library as two shelves of open bins with gold dots in them, a speech bubble dropping requests in, a pen rewriting the label of one bin ringed in oxblood, and a red dot pulled across into it from the bin next door https://brinvik.com/lab/skill-trigger-test/cover-en-1600x720.png https://brinvik.com/lab/skill-trigger-test/cover-en-1600x720.png Why internal AI tools need a regression test for skills A skill is a folder with a SKILL.md. The frontmatter holds a name\ and a description\ ; the body is the procedure. Claude sees only the name and description when it decides what to load, and the body loads after the pick. So the description is the whole interface between a seller's request and the team's recipe. The test that came out of this build: seven sales skills with one-sentence descriptions got 40 messy requests right in 120 of 120 runs. Twenty overlapping skills got 117 of 120. Then Claude rewrote the description of the one skill that missed, which fixed that request and moved two others that had been right into the wrong skill, in every run. That last part is why the runner exists. The full story is in the write-up on the Claude skill test https://brinvik.com/en/resources/internal-ai-tools-claude-skill-test?utm source=devto&utm medium=article&utm campaign=lab-skill-trigger-test&utm content=devto-en