AC padel-tui-playtomic-booking
This skill should be used when the user asks to "book a padel court", "find available padel courts", "search padel courts near me", "reserve a Playtomic court", "book a court tonight", "list my active matches", "cancel a padel booking", "install padel-tui", "use padel-tui CLI", or "book through terminal instead of the app".
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
The same skill appears in 1 more place: ClawHub
How to improve
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 55/100
- 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
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (padel-tui-playtomic-booking) differs from the folder (padel)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Failures and branches. 2 branches
- 85Steps. 42 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 695 tokens
- low The response is described with custom markup (5 tags): a typed call is more reliable
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
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 10 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 325: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 42 items
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.