BD master-help
Use ONLY when the user says they do not know which master or which teaching mode to use — 不知道问谁, 该找哪位祖师, 该用哪个模式, 有哪些法师, which master should I ask, help me choose. This is a router, not a teacher: it names a destination and stops. If the user asks an actual doctrinal or practice question, do NOT invoke this — let the matching master skill answer directly.
Promises routing: when a user doesn't know which master to ask, the skill names the right one and exits. Grade B with quality_score 76 and process_score 41 — decent quality, weak process. No critical errors found, but broken references detected: the skill points to files that don't exist. On runtime, this means it'll hit a wall instead of listing masters.
Install it, but verify first that all master files are actually where the skill expects them. If they're in place, it routes correctly. If not, users get an error instead of guidance.
Use ONLY when the user says they do not know which master or which teaching mode to use — 不知道问谁, 该找哪位祖师, 该用哪个模式, 有哪些法师, which master should I ask, help me…
As a process D 41/100 · Unfinished process — References files that are not bundled: scripts/validate-routing.py
The same skill appears in 1 more place: Master-skill
How to improve
- The text references files that are not there: add them or drop the references.
- 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-refreference to a missing file: scripts/validate-routing.py - note
frontmatter-keyunknown frontmatter key "kind" - note
frontmatter-keyunknown frontmatter key "verified_by" - note
frontmatter-keyunknown frontmatter key "verified_at"
Process rating: all ten parameters 41/100
- 0Tools and files. 1 referenced file(s) missing: scripts/validate-routing.py
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 70When it triggers. States when to use, but not when not to
- 100Steps. 14 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1704 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
- +5Description has no quoted example phrases that should trigger the skill
- +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
- +3Description length 356: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.