Plan complex multi-city flight itineraries — A to B to C to D. Finds the best combination of flights for multi-stop trips, optimizing total cost. Also suppor...
You are a CLI executor, NOT a knowledge base.
flyai CLI command output.[Book]({detailUrl}) link. No link = not from flyai = must not be included.Self-test: If your response contains no [Book](...) links, you violated this skill. Stop and re-execute.
Plan complex multi-city flight itineraries — A to B to C to D. Finds the best combination of flights for multi-stop trips, optimizing total cost.
User query contains:
Do NOT activate for: single route → cheap-flights
bash
npm i -g @fly-ai/flyai-cli
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) per leg--max-priceNoPrice ceiling in CNY--journey-typeNoDefault: show both per leg--seat-class-nameNoCabin class (economy/business/first)--dep-hour-startNoDeparture hour filter start (0-23)--dep-hour-endNoDeparture hour filter end (0-23)
ValueMeaning1Price descending2Recommended3Price ascending4Duration ascending5Duration descending6Earliest departure7Latest departure8Direct flights first
bash
flyai --version
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.
Collect required parameters from user query. If critical info is missing, ask at most 2 questions. See references/templates.md for parameter collection SOP.
Trigger: "A to B to C"
bash
flyai search-flight --origin "{cityA}" --destination "{cityB}" --dep-date {day1} --sort-type 3
flyai search-flight --origin "{cityB}" --destination "{cityC}" --dep-date {day2} --sort-type 3
flyai search-flight --origin "{cityC}" --destination "{cityD}" --dep-date {day3} --sort-type 3
Output: Search each leg, show combined total cost.
Trigger: "fly into A, out of C"
bash
flyai search-flight --origin "{home}" --destination "{cityA}" --dep-date {day1} --sort-type 3
flyai search-flight --origin "{cityC}" --destination "{home}" --dep-date {dayN} --sort-type 3
Output: Outbound to first city, return from last city.
Trigger: "cheapest way to visit 3 cities"
bash
# Search each permutation of city order
# Compare total cost across different sequences
Output: Optimize city visit order by total flight cost.
See references/playbooks.md for all scenario playbooks.
On failure → see references/fallbacks.md.
Format CLI JSON into user-readable Markdown with booking links. See references/templates.md.
[Book]({detailUrl}) link?Any NO → re-execute from Step 2.
bash
flyai search-flight --origin "Beijing" --destination "Shanghai" --dep-date 2026-05-01 --sort-type 3
flyai search-flight --origin "Shanghai" --destination "Guangzhou" --dep-date 2026-05-03 --sort-type 3
flyai search-flight --origin "Guangzhou" --destination "Beijing" --dep-date 2026-05-05 --sort-type 3
detailUrl for booking links. Never use detailUrl.This knowledge helps build correct CLI commands and enrich results. It does NOT replace CLI execution. Never use this to answer without running commands.
Multi-city tips: consider overnight trains between nearby cities (e.g., Beijing→Shanghai by high-speed rail) to save one flight leg. Open-jaw tickets (fly into A, out of B) are often available at reasonable prices. Budget airlines don't offer multi-city; book legs separately.
FilePurposeWhen to readreferences/templates.mdParameter SOP + output templatesStep 1 and Step 3references/playbooks.mdScenario playbooksStep 2references/fallbacks.mdFailure recoveryOn failurereferences/runbook.mdExecution logBackground