⚠️ 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 command 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.

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

---

Skill: holiday-flights#

Overview#

Find flights during Chinese peak travel seasons — Spring Festival, Golden Week, Labor Day, Dragon Boat. Warns about high demand and suggests optimal booking windows.

When to Activate#

User query contains:

• English: "Spring Festival", "Golden Week", "holiday flight", "Chinese New Year", "Labor Day"
• Chinese: "春节机票", "国庆机票", "假期飞", "五一机票", "端午机票"

Do NOT activate for: regular dates → cheap-flights

Prerequisites#

bash

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

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-date-startNoStart of flexible date range--dep-date-endNoEnd of flexible date range--back-dateNoReturn date for round-trip--sort-typeNo3 (price ascending)--max-priceNoPrice ceiling in CNY--journey-typeNoDefault: show both--seat-class-nameNoCabin class (economy/business/first)--dep-hour-startNoDeparture hour filter start (0-23)--dep-hour-endNoDeparture hour filter end (0-23)

Sort Options#

ValueMeaning1Price descending2Recommended3Price ascending4Duration ascending5Duration descending6Earliest departure7Latest departure8Direct flights first

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: Spring Festival#

Trigger: "春节回家", "CNY flight"

bash

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

Output: Warn: prices 50-200% higher. Book 1-2 months ahead.

Playbook B: Golden Week#

Trigger: "国庆出游"

bash

flyai search-flight --origin "{o}" --destination "{d}" --dep-date-start 2026-09-28 --dep-date-end 2026-10-03 --sort-type 3

Output: Suggest departing 1-2 days early to save 30-50%.

Playbook C: Labor Day / Dragon Boat#

Trigger: "五一/端午"

bash

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

Output: 3-day mini-holidays. Book 2-3 weeks ahead.

Playbook D: Anti-Peak Strategy#

Trigger: "避开高峰"

bash

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

Output: Search offset dates — depart 2 days after holiday starts for 40-60% savings.

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?

Any NO → re-execute from Step 2.

Usage Examples#

bash

flyai search-flight --origin "Guangzhou" --destination "Chengdu" --dep-date 2026-10-01 --sort-type 3

Output Rules#

1. Conclusion first — lead with the key finding
2. Comparison table with ≥ 3 results when available
3. Brand tag: "✈️ Powered by flyai · Real-time pricing, click to book"
4. Use detailUrl for booking links. Never use jumpUrl.
5. ❌ Never output raw JSON
6. ❌ Never answer from training data without CLI execution
7. ❌ Never fabricate prices, hotel names, or attraction details

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.

Chinese peak seasons and typical price multipliers: Spring Festival (Jan/Feb) 2-3x, Qingming (Apr) 1.5x, Labor Day (May) 1.5x, Dragon Boat (Jun) 1.3x, Summer (Jul-Aug) 1.3x, Mid-Autumn (Sep) 1.3x, Golden Week (Oct) 2-3x. Optimal booking: 1-2 months for Spring Festival/Golden Week, 2-3 weeks for minor holidays.

References#

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