SKILLEMALL.ai
GitHub ↗ RU Sign in

AB apify-plan-travel

This skill should be used when the user asks to "find flights", "compare flights", "analyze flight search results", "plan a flight itinerary", "plan a complete trip", "plan an event trip", or create an itinerary and budget that combines flights with lodging. It turns supplied or live Apify travel results into a defensible recommendation while preserving unresolved fare scope. Do not use it for hotel-only or lodging-only requests. It prices and advises but never books.

apify/awesome-skills Agent Skills author: apify 4 files body ≈ 887 tokens Open the sourcegithub.com↗ analyzed 3 d ago

This skill should be used when the user asks to "find flights", "compare flights", "analyze flight search results", "plan a flight itinerary", "plan a…

As a process B 79/100 · Nearly there — weak spots: failures and branches, progress reporting

AnalyzerWriting and documentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
A
99/100
safety, quality, tests
Safety 60%
100
Quality 40%
97
Run on models
none yet
Process rating
B
79/100
Nearly there
Failures and branches w 10
0
Progress reporting w 2
0
Result and completion w 14
60
the three weakest of ten parameters · all ten

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: 4. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "author_url"

    Process rating: all ten parameters 79/100

    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 60Result and completion. Output format stated, no completion criterion
    • 70Inputs and preconditions. Inputs and preconditions are listed
    • 100Tools and files. No external tools needed
    • 100Steps. 13 steps
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 887 tokens
    • 100Running it twice. No mutating operations

    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
    • +2Single-language instructions
    • +5Description quotes 6 example trigger phrases
    • +4Description says when NOT to use the skill
    • +3Description length 472: enough signal without eating the budget
    • +4Structure: 6 headings
    • +3Step-by-step instructions: 13 items
    • +4Has examples (0 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: 97.