SKILLEMALL.ai

AB navifare-flight-validator

Verify and compare flight prices across multiple booking sites using Navifare. Trigger when users share flight prices from any booking site (Skyscanner, Kayak, etc.) or upload flight screenshots to find better deals. Returns ranked results with booking links from multiple providers.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 11 files body ≈ 4 550 tokens Open the sourcegithub.com analyzed 2 d ago

Verify and compare flight prices across multiple booking sites using Navifare.

As a process B 74/100 · Nearly there — weak spots: consistency, running it twice, progress reporting

AnalyzerSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
97/100
safety, quality, tests
Safety 60%
100
Quality 40%
92
Run on models
none yet
Process rating
B
74/100
Nearly there
Progress reporting w 2
0
Running it twice w 4
30
Consistency w 8
40
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: navifare-flight-validator (LeoYeAI/openclaw-master-skills)

How to improve

    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: 11. 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 74/100

    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 5 mutating operations with no state check
    • 40Consistency. Frontmatter name (navifare-flight-validator) differs from the folder (gonza-navifare-deals)
    • 60Result and completion. Output format stated, no completion criterion
    • 70When it triggers. States when to use, but not when not to
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 70Execution cost. Instruction body is 4550 tokens
    • 85Steps. 102 steps, 1 vague phrases
    • 100Tools and files. Tools declared in frontmatter
    • 100Failures and branches. 4 branches, has a failure section
    • 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)
    • +2Single-language instructions
    • +3Description length 283: enough signal without eating the budget
    • +4Structure: 31 headings
    • +3Step-by-step instructions: 102 items
    • +3Output format is stated explicitly
    • +4Has examples (22 code blocks)
    • +4Reference files are cited in the instructions (3 of 3)
    • +1License stated

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