SKILLEMALL.ai

BC flight-search

Search flights, compare prices, and monitor airfare using Amadeus API

modbender/skill-library-mcp Agent Skills author: modbender MIT 20 files · 3 scripts body ≈ 1 876 tokens Open the sourcegithub.com analyzed 2 d ago

Search flights, compare prices, and monitor airfare using Amadeus API

As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, consistency

IntegrationSoftware developmentInfrastructureSales and CRMtype and topics are labelled automatically from the skill text
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
100
Quality 40%
62
Run on models
none yet
Process rating
C
61/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 20. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "triggers"
  • note frontmatter-key unknown frontmatter key "credentials"

Process rating: all ten parameters 61/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (flight-search) differs from the folder (flight-search-skill)
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 75 steps
  • 100Execution cost. Instruction body is 1876 tokens
  • 100Running it twice. Mutating operations check current state
  • low 14 top-level sections: this looks like several domains in one skill

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)
  • +3Description length 69: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • -218 emoji in the instructions: noise for the model
  • -33 of 3 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +4Structure: 27 headings
  • +3Step-by-step instructions: 75 items
  • +4Has examples (8 code blocks)

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