honeymoon-trip

⚠️ 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 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: honeymoon-trip

Overview

Plan a dreamy honeymoon — luxury hotels, romantic activities, couples' spa, sunset dinners, and unforgettable experiences for newlyweds.

When to Activate

User query contains:

Do NOT activate for: couple stay → romantic-hotel

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

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: Luxury Honeymoon

Trigger: "honeymoon trip"

Flights (business class option) + 5-star hotels + romantic POIs

Output: Full luxury honeymoon.

Playbook B: Beach Honeymoon

Trigger: "beach honeymoon"

Flights to beach dest + beachfront resort + water activities

Output: Tropical romantic escape.

Playbook C: Budget Honeymoon

Trigger: "affordable honeymoon"

Budget flights + 4-star romantic hotels + free attractions

Output: Romantic but budget-conscious.

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

Full romantic orchestration to Maldives or Bali

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.

Top honeymoon destinations: Maldives (overwater villas), Bali (rice terraces + beaches), Santorini (sunsets), Sanya (domestic luxury), Lijiang (ancient town romance), Paris (classic). Book honeymoon suite 2+ months ahead. Many hotels offer honeymoon packages with champagne, flowers, late checkout.

References

| File | Purpose | When to read | |------|---------|-------------| | references/templates.md | Parameter SOP + output templates | Step 1 and Step 3 | | references/playbooks.md | Scenario playbooks | Step 2 | | references/fallbacks.md | Failure recovery | On failure | | references/runbook.md | Execution log | Background |

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