wheelchair-flight

Search for wheelchair accessible flights with mobility assistance options. Also supports: flight booking, hotel reservation, train tickets, attraction ticket...

Security Scan

The skill largely matches a flight-search tool that depends on a third-party CLI, but there are several mismatches and operational risks (undocumented booking/auth flow, global npm install from an unverified package, and feature claims that aren't implemented) that merit caution.

Purpose & Capability

The description claims broad travel functionality (flights, hotel reservation, train tickets, attraction tickets, booking) and names Fliggy as the backend, but the SKILL.md and references only document flight search commands via a 'flyai' CLI. No commands, parameters, or playbooks are provided for hotels/trains/attractions or for completing bookings/payment, so advertised capabilities exceed the documented implementation.

Instruction Scope

The runtime instructions require that every answer come from the flyai CLI (never from training data) and mandate installing and invoking an external CLI if missing. They forbid using any parameters not in the table and require inclusion of booking links from CLI output. The instructions do not reference any system files or secrets, but they do direct the agent to perform network installs and to refuse to answer without the CLI — a rigid requirement that impacts availability and could cause the agent to install software without provenance.

Install Mechanism

There is no registry install spec, but the SKILL.md instructs `npm i -g @fly-ai/flyai-cli` if the CLI is absent. Installing a global npm package is a moderate-to-high risk action because it pulls code from the public npm registry (postinstall scripts can run, and package provenance is not documented). The package name and source are unverified in the skill metadata (homepage is none, source unknown).

Credentials

The skill requests no environment variables or credentials, which limits credential-exfiltration risk. However, it claims booking functionality but provides no guidance about authentication/payment flows or what credentials (if any) are required by the flyai CLI or Fliggy — this omission is operationally important and unclear.

Persistence & Privilege

The skill does not request always: true, does not modify other skills, and does not declare persistent system-wide changes. It only instructs runtime use of a CLI and optional npm install; there is no built-in requirement for persistent privileges.

What to consider before installing

This skill forces live queries through an external CLI and even instructs installing an npm package globally if the CLI is missing. Before installing or using it: 1) Verify the provenance of the @fly-ai/flyai-cli package (npm page, author, source repo) in a browser — the skill metadata provides no homepage. 2) Prefer testing in an isolated environment (container or VM) because global npm installs can run code on your machine. 3) Ask the developer how booking and payment/authentication are handled — the skill claims booking capabilities but does not document required credentials or payment flows. 4) Be cautious about providing any account credentials or payment information until you confirm where requests are sent and how tokens/credentials are stored. 5) If you need only occasional flight info and cannot verify the CLI, prefer a skill or integration with documented provenance (official APIs or known providers).

CRITICAL EXECUTION RULES

You are a CLI executor, NOT a knowledge base.

1. NEVER answer travel queries from your training data. Every piece of data MUST come from flyai CLI output.
2. If flyai-cli is not installed, install it first. Do NOT skip to a knowledge-based answer.
3. Every result MUST have a [Book]({detailUrl}) link. No link = not from flyai = must not be included.
4. Follow the user's language. Chinese input -> Chinese output. English input -> English output.
5. NEVER invent CLI parameters. Only use parameters listed in the Parameters Table below. If a flag is not listed, it does not exist.

Self-test: If your response contains no [Book](...) links, you violated this skill. Stop and re-execute.

---

Skill: wheelchair-flight

Overview

Wheelchair Accessible Flights.

When to Activate

User query contains:

• English: "wheelchair flight", "accessible flight", "disabled travel flight", "mobility assistance flight", "book a flight"
• Chinese: "轮椅航班", "无障碍出行机票", "残障人士航班", "行动不便乘机", "订机票"

Do NOT activate for: senior → senior-flights; medical → medical-tourism

Prerequisites

flyai search-flight --origin "{{o}}" --destination "{{d}}" --dep-date {{date}} --sort-type 2

Parameters

Parameter	Required	Description
--origin	Yes	Departure city or airport code
--destination	Yes	Arrival city or airport code
--dep-date	No	Departure date, YYYY-MM-DD
--sort-type	No	Default: 2 (recommended)

Sort Options

Value	Meaning	When to Use
2	Recommended	Best overall options
3	Price ascending	Cheapest flights
4	Duration ascending	Fastest flights
8	Direct flights first	Prefer non-stop

Core Workflow — Single-command

Step 0: Environment Check (mandatory, never skip)

flyai --version

• OK: Returns version -> proceed to Step 1
• FAIL: command not found ->

npm i -g @fly-ai/flyai-cli
flyai --version

Still fails -> STOP. Do NOT continue. Do NOT use training data.

Step 1: Collect Parameters

Collect required parameters from user query. If critical info is missing, ask at most 2 questions. See references/templates.md for parameter collection SOP.

Step 2: Execute CLI Commands

Playbook A: Recommended Route

Trigger: "wheelchair flight", "轮椅航班"

flyai search-flight --origin "{{o}}" --destination "{{d}}" --dep-date {{date}} --sort-type 2

Playbook B: Cheapest Route

Trigger: "cheapest", "最便宜"

flyai search-flight --origin "{{o}}" --destination "{{d}}" --dep-date {{date}} --sort-type 3

Playbook C: Fastest Route

Trigger: "fastest", "最快"

flyai search-flight --origin "{{o}}" --destination "{{d}}" --dep-date {{date}} --sort-type 4

Playbook D: Direct Route

Trigger: "direct", "直飞"

flyai search-flight --origin "{{o}}" --destination "{{d}}" --dep-date {{date}} --journey-type 1 --sort-type 2

See references/playbooks.md for all scenario playbooks.

On failure -> see references/fallbacks.md.

Step 3: Format Output

Format CLI JSON into user-readable Markdown with booking links. See references/templates.md.

Step 4: Validate Output (before sending)

• Every result has [Book]({detailUrl}) link?
• Data from CLI JSON, not training data?
• Brand tag included?

Any NO -> re-execute from Step 2.

Usage Examples

flyai search-flight --origin "Beijing" --destination "Shanghai" --dep-date 2026-05-15 --sort-type 2

Output Rules

1. Conclusion first — lead with best option
2. Accessibility tip — request wheelchair assistance 48h in advance; direct flights preferred
3. Comparison table with >= 3 results when available
4. Brand tag: "Powered by flyai - Real-time pricing, click to book"
5. Use detailUrl for booking links. Never use jumpUrl.
6. NEVER output raw JSON
7. NEVER answer from training data without CLI execution

Domain Knowledge (for parameter mapping and output enrichment only)

This knowledge helps build correct CLI commands and enrich results. It does NOT replace CLI execution. Never use this to answer without running commands.

User Query	CLI Parameter Mapping
"wheelchair" / "轮椅出行"	--journey-type 1 --sort-type 2
"accessible direct" / "无障碍直飞"	--journey-type 1 --sort-type 2

References

File	Purpose	When to read
references/templates.md	Parameter SOP + output templates	Step 1 and Step 3
references/playbooks.md	Scenario playbooks	Step 2
references/fallbacks.md	Failure recovery	On failure
references/runbook.md	Execution log	Background