AF tennis-grand-slam-planner
When a user mentions watching tennis, Grand Slam travel, or planning a trip to the Australian Open, French Open (Roland Garros), Wimbledon, or US Open, activate this skill. It combines the Grand Slam calendar with flyai travel APIs to generate a complete "match-chasing" itinerary — including flights, hotels near the venue, local attractions, and event tickets — all organized around the tournament schedule. Not for general travel planning without a tennis event context.
As a process F 58/100 · Will not run — References files that are not bundled: {mainPic}, {picUrl}, {jumpUrl}
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: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: {mainPic} - warning
missing-refreference to a missing file: {picUrl} - warning
missing-refreference to a missing file: {jumpUrl} - warning
missing-refreference to a missing file: {detailUrl}
Process rating: all ten parameters 58/100
- 0Tools and files. 4 referenced file(s) missing: {mainPic}, {picUrl}, {jumpUrl}
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (tennis-grand-slam-planner) differs from the folder (ace-trip)
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 21 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Execution cost. Instruction body is 997 tokens
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
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 473: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 21 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.