⚠️ 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: airport-transit-hotel

Overview

Find hotels near airports for layovers, early morning flights, or late-night arrivals. Sorted by distance to terminal with shuttle info.

When to Activate

User query contains:

• English: "airport hotel", "near airport", "layover hotel", "transit stay"
• Chinese: "机场酒店", "机场附近住", "中转住宿", "航站楼附近"

Do NOT activate for: city center → budget-hotel-finder

Prerequisites

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

Parameters

Sort Options

Core Workflow — Single-command

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: Near Airport

Trigger: "airport hotel", "机场酒店"

flyai search-hotel --dest-name "{city}" --key-words "机场" --sort distance_asc --check-in-date {in} --check-out-date {out}

Output: Hotels near airport, closest first.

Playbook B: Transit Capsule

Trigger: "transit hotel", "中转休息"

flyai search-hotel --dest-name "{city}" --key-words "机场 太空舱" --sort price_asc --check-in-date {in} --check-out-date {out}

Output: Capsule/pod hotels near airport for short stays.

Playbook C: Pre-Flight Stay

Trigger: "early morning flight", "早班机前一晚"

flyai search-hotel --dest-name "{city}" --key-words "机场" --sort distance_asc --check-in-date {tonight} --check-out-date {tomorrow}

Output: One night before early departure.

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

flyai search-hotel --dest-name "Shanghai" --key-words "浦东机场" --sort distance_asc --check-in-date 2026-05-01 --check-out-date 2026-05-02

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.

Airport hotels tip: check shuttle service (many offer free shuttle every 15-30 min). Some airports have in-terminal transit hotels (e.g., PVG, CAN). Capsule hotels near airports cost ¥100-200 for 4-8 hours. For layovers >8h, a proper hotel room is more restful than a lounge.

References