⚠️ 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: trip-planner
Overview
Plan your entire trip with AI — flights, hotels, attractions, day-by-day itinerary. Tell me your destination, dates, and interests, I'll handle the rest.
When to Activate
User query contains:
- English: "plan my trip", "travel planning", "itinerary", "organize my vacation"
- Chinese: "帮我规划行程", "安排旅行", "行程规划", "旅游攻略"
Do NOT activate for: specific type → see specialized planners
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-hotel
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 |
keyword-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: Full Plan
Trigger: "plan my trip", "帮我规划行程"
flyai keyword-search --query "{dest} visa"
flyai search-flight --origin "{o}" --destination "{d}" --dep-date {day1} --sort-type 3
flyai search-flight --origin "{d}" --destination "{o}" --dep-date {dayN} --sort-type 3
flyai search-hotel --dest-name "{city}" --check-in-date {day1} --check-out-date {dayN} --sort rate_desc
flyai search-poi --city-name "{city}" --poi-level 5
Output: Complete itinerary with all components.
Playbook B: Quick Plan
Trigger: "plan a quick trip"
flyai search-flight --origin "{o}" --destination "{d}" --dep-date {day1} --sort-type 3
flyai search-hotel --dest-name "{city}" --sort rate_desc --check-in-date {day1} --check-out-date {dayN}
flyai search-poi --city-name "{city}" --poi-level 5
Output: Skip visa, focus on core booking.
Playbook C: Budget Plan
Trigger: "plan cheap trip"
flyai search-flight --origin "{o}" --destination "{d}" --dep-date {day1} --sort-type 3
flyai search-hotel --dest-name "{city}" --sort price_asc --max-price 300 --check-in-date {day1} --check-out-date {dayN}
flyai search-poi --city-name "{city}" --poi-level 5
Output: All budget-oriented selections.
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 keyword-search --query "Japan visa"
flyai search-flight --origin "Shanghai" --destination "Tokyo" --dep-date 2026-05-01 --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.
Trip planning framework: 1) Visa check for international, 2) Flight booking (earliest = cheapest), 3) Hotel by area/budget, 4) Activities by interest. Collect from user: origin, dates, days, interests, budget. Don't assume route — let flight prices guide city order.
References
