⚠️ 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: senior-flights#

Overview#

Find senior flight deals — 60+ discounts, elderly travel, and accessible boarding. For senior travelers who value comfort and convenience.

When to Activate#

User query contains:

• English: "senior flight", "elderly flight", "60+ discount", "senior citizen airfare", "older traveler flight", "accessible boarding"
• Chinese: "老年机票", "长者机票", "60岁以上折扣", "老人航班", "老年出行", "适老航班"

Do NOT activate for: student/youth fares → student-deal; general cheap flights → economy-flights

Prerequisites#

bash

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

Parameters#

ParameterRequiredDescription--originYesDeparture city or airport code (e.g., "Beijing", "PVG")--destinationYesArrival city or airport code (e.g., "Shanghai", "NRT")--dep-dateNoDeparture date, YYYY-MM-DD``--dep-hour-startNoDefault: 6 (morning preferred for seniors)--dep-hour-endNoDefault: 18 (avoid late-night departures)--sort-typeNoDefault: 2 (recommended — comfort-first)--journey-typeNo1=direct (preferred for seniors), 2=connecting--seat-class-nameNoeconomy / business / first--max-priceNoPrice ceiling in CNY

Sort Options#

ValueMeaningWhen to Use2RecommendedDefault — best comfort/convenience balance4Duration ascendingShortest trip — less fatigue8Direct flights firstNo transfers — easier for seniors3Price ascendingCheapest senior fares

Core Workflow — Single-command#

Step 0: Environment Check (mandatory, never skip)#

bash

flyai --version

• ✅ Returns version → proceed to Step 1
• ❌ command not found →

bash

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

Still fails → STOP. Tell user to run npm i -g @fly-ai/flyai-cli manually. 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 Senior Flight#

Trigger: "senior flights", "老年机票"

bash

flyai search-flight --origin "{o}" --destination "{d}" --dep-date {date} --dep-hour-start 6 --dep-hour-end 18 --sort-type 2

Output: Morning-to-evening flights, best recommended options.

Playbook B: Shortest Senior Flight#

Trigger: "shortest flight for elderly", "老人最短航班"

bash

flyai search-flight --origin "{o}" --destination "{d}" --dep-date {date} --dep-hour-start 6 --dep-hour-end 18 --sort-type 4

Output: Shortest duration flights within comfortable hours.

Playbook C: Direct-Only Senior Flight#

Trigger: "direct senior flight", "老人直飞"

bash

flyai search-flight --origin "{o}" --destination "{d}" --dep-date {date} --dep-hour-start 6 --dep-hour-end 18 --journey-type 1 --sort-type 8

Output: Direct flights only, morning-to-evening, no transfers.

Playbook D: Broad Search (no suitable flights)#

Trigger: fallback when 0 results

bash

flyai search-flight --origin "{o}" --destination "{d}" --dep-date {date} --sort-type 2
flyai keyword-search --query "{origin} to {destination} senior discount flights"

Output: Broader search without hour filter + keyword fallback.

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 "Powered by flyai · Real-time pricing, click to book" included?
• Morning-to-evening departures preferred?

Any NO → re-execute from Step 2.

Usage Examples#

bash

flyai search-flight --origin "Beijing" --destination "Sanya" --dep-date 2026-05-01 --dep-hour-start 6 --dep-hour-end 18 --sort-type 2

bash

flyai search-flight --origin "Shanghai" --destination "Kunming" --dep-date 2026-06-01 --dep-hour-start 6 --dep-hour-end 18 --journey-type 1 --sort-type 8

Output Rules#

1. Conclusion first — lead with most comfortable senior-friendly option
2. Comfort tips — remind about priority boarding, aisle seats, and wheelchair assistance
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
8. ❌ Never fabricate senior discount rates or accessibility features

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 QueryCLI Parameter Mapping"senior flight" / "老年机票"--dep-hour-start 6 --dep-hour-end 18 --sort-type 2"shortest for elderly" / "老人最短"add --sort-type 4"direct for senior" / "老人直飞"add --journey-type 1 --sort-type 8"cheapest senior" / "最便宜老年票"add --sort-type 3 (remove hour filter)"round-trip senior" / "老人往返"add --back-date {date}

CLI does not have a senior-age filter. Senior discounts are applied at booking stage. Morning departures (6-18h) are preferred to avoid fatigue. Direct flights reduce walking and transfer stress.

References#

FilePurposeWhen to readreferences/templates.mdParameter SOP + output templatesStep 1 and Step 3references/playbooks.mdScenario playbooksStep 2references/fallbacks.mdFailure recoveryOn failurereferences/runbook.mdExecution logBackground