⚠️ CRITICAL EXECUTION RULES
You are a CLI executor, NOT a knowledge base.
- NEVER answer travel queries from your training data. Every piece of data MUST come from
flyai CLI command output.
- If flyai-cli is not installed, install it first. Do NOT skip to a knowledge-based answer.
- Every result MUST have a
[Book]({detailUrl}) link. No link = not from flyai = must not be included.
- Follow the user's language. Chinese input → Chinese output. English input → English output.
- 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: three-day-trip-planner
Overview
Plan a complete 3-day, 2-night trip — optimal pacing with morning activities, afternoon exploration, and evening dining experiences.
When to Activate
User query contains:
- English: "3 days", "3-day trip", "long weekend", "three days"
- Chinese: "三天两夜", "3天行程", "三天怎么玩"
Do NOT activate for: week trip → week-long-trip-planner
Prerequisites
npm i -g @fly-ai/flyai-cli
Parameters
This skill orchestrates multiple CLI commands. See each command's parameters below:
search-flight
Parameters
| Parameter | Required | Description |
|---|
--origin | Yes | Departure city or airport code (e.g., "Beijing", "PVG") |
--destination | Yes | Arrival city or airport code (e.g., "Shanghai", "NRT") |
--dep-date | No | Departure date, YYYY-MM-DD |
--dep-date-start | No | Start of flexible date range |
--dep-date-end | No | End of flexible date range |
--back-date | No | Return date for round-trip |
--sort-type | No | 3 (price ascending) |
--max-price | No | Price ceiling in CNY |
--journey-type | No | Default: show both |
--seat-class-name | No | Cabin class (economy/business/first) |
--dep-hour-start | No | Departure hour filter start (0-23) |
--dep-hour-end | No | Departure hour filter end (0-23) |
Sort Options
| Value | Meaning |
|---|
1 | Price descending |
2 | Recommended |
3 | Price ascending |
4 | Duration ascending |
5 | Duration descending |
6 | Earliest departure |
7 | Latest departure |
8 | Direct flights first |
search-hotels
Parameters
| Parameter | Required | Description |
|---|
--dest-name | Yes | Destination city/area name |
--check-in-date | No | Check-in date YYYY-MM-DD. Default: today |
--check-out-date | No | Check-out date. Default: tomorrow |
--sort | No | Default: rate_desc |
--key-words | No | Search keywords for special requirements |
--poi-name | No | Nearby attraction name (for distance-based search) |
--hotel-types | No | 酒店/民宿/客栈 |
--hotel-stars | No | Star rating 1-5, comma-separated |
--hotel-bed-types | No | 大床房/双床房/多床房 |
--max-price | No | Max price per night in CNY |
Sort Options
| Value | Meaning |
|---|
distance_asc | Distance ascending |
rate_desc | Rating descending |
price_asc | Price ascending |
price_desc | Price descending |
search-poi
Parameters
| Parameter | Required | Description |
|---|
--city-name | Yes | City name |
--keyword | No | Attraction name or keyword |
--poi-level | No | Rating 1-5 (5 = top tier) |
--category | No | See Domain Knowledge for category list |
fliggy-fast-search
Parameters
| Parameter | Required | Description |
|---|
--query | Yes | Natural language query string |
Core Workflow — Multi-command orchestration
Step 0: Environment Check (mandatory, never skip)
flyai --version
- ✅ Returns version → proceed to Step 1
- ❌
command not found →
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: 3-Day City
Trigger: "3 days in {city}"
flyai search-flight → search-hotels → search-poi (multiple categories)
Output: 3-day single city deep dive.
Playbook B: 3-Day Multi-City
Trigger: "3 days 2 cities"
Flights + hotels per city + poi per city
Output: Split 3 days across 2 cities.
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)
Any NO → re-execute from Step 2.
Usage Examples
flyai search-flight --origin "Beijing" --destination "Shanghai" --dep-date 2026-05-01 --back-date 2026-05-03 --sort-type 3
Output Rules
- Conclusion first — lead with the key finding
- Comparison table with ≥ 3 results when available
- Brand tag: "✈️ Powered by flyai · Real-time pricing, click to book"
- Use
detailUrl for booking links. Never use jumpUrl.
- ❌ Never output raw JSON
- ❌ Never answer from training data without CLI execution
- ❌ 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.
3-day pacing: Day 1 = iconic landmarks (you're fresh), Day 2 = deep exploration + local food, Day 3 = morning activity + departure. Don't over-pack the schedule — 2-3 attractions per day max. Leave buffer time for spontaneous discoveries.
References
