SKILLEMALL.ai

AC skill-router

This skill should be used when the user has a vague or cross-domain request and asks "which skill should I use", "is there a skill for this", "find the right skill", or "route this to the best skill" — it matches an intent against the whole skills library and recommends the best-fit skill(s).

borghei/Claude-Skills Agent Skills author: borghei 2 files · 1 script body ≈ 1 039 tokens Open the sourcegithub.com↗ analyzed 8 h ago

This skill should be used when the user has a vague or cross-domain request and asks "which skill should I use", "is there a skill for this", "find the right…

As a process C 54/100 · Has gaps — References files that are not bundled: scripts/build_manifest.py

ProcedureSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
87
Run on models
none yet
Process rating
C
54/100
Has gaps
References files that are not bundled: scripts/build_manifest.py
Tools and files w 18
0
Result and completion w 14
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: scripts/build_manifest.py

Process rating: all ten parameters 54/100

Will not run. References files that are not bundled: scripts/build_manifest.py
  • 0Tools and files. 1 referenced file(s) missing: scripts/build_manifest.py
  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 55Failures and branches. 1 branches
  • 100Steps. 15 steps
  • 100When it triggers. States when to use and when not to
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1039 tokens
  • 100Running it twice. No mutating operations

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +5Description quotes 4 example trigger phrases
  • +3Description length 293: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 15 items
  • +4Has examples (1 code blocks)
  • +3All 1 scripts are documented
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.