BA Urgent Appointment Scramble Board
Track urgent appointment calls across multiple providers with a live availability board, call log, openings, callbacks, and confirmation details.
As a process A 80/100 · Runs to the end — weak spots: consistency, running it twice
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.
Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 1
-
high Concealment
en-hide-from-userSKILL.md:177Instruction to hide actions from the user- Do not tell the user it is safe to wait for an appointment when immediate professional help may be needed.
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "type"
Process rating: all ten parameters 80/100
- 30Running it twice. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (Urgent Appointment Scramble Board) differs from the folder (urgent-appointment-scramble-board)
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 5 branches
- 85Steps. 70 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Result and completion. Output format and completion criterion are stated
- 100Execution cost. Instruction body is 2421 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +1No license
- +2Single-language instructions
- +3Description length 145: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 70 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.