⚠️ 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: explore-japan

Overview

Your complete Japan travel companion — flights to Tokyo/Osaka/Kyoto, hotels from ryokan to capsule, shrine visits, cherry blossom viewing, ramen tours, JR Pass guidance, and visa help.

When to Activate

User query contains:

• English: "Japan", "Tokyo", "Osaka", "Kyoto", "Hokkaido"
• Chinese: "日本", "东京", "大阪", "京都", "北海道", "去日本"

Do NOT activate for: generic Asia → explore-southeast-asia

Prerequisites

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

Parameters

This skill orchestrates multiple CLI commands. See each command's parameters below:

search-flight

Parameters

Sort Options

search-hotel

Parameters

Sort Options

search-poi

Parameters

keyword-search

Parameters

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: Multi-City Japan

Trigger: "Japan trip"

visa check + flights to Tokyo + hotels per city + POIs per city + JR Pass advice

Output: Full Japan itinerary.

Playbook B: Tokyo Only

Trigger: "Tokyo trip"

Flight to NRT/HND + Tokyo hotel + Tokyo POIs

Output: Tokyo-focused trip.

Playbook C: Kansai

Trigger: "Kyoto Osaka"

Flight to KIX + hotels in Kyoto/Osaka + temples/food POIs

Output: Kansai region deep dive.

Playbook D: Hokkaido

Trigger: "Hokkaido trip"

Flight to CTS + Sapporo/Otaru/Niseko hotels + nature/ski POIs

Output: Hokkaido seasonal trip.

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-flight --origin "Shanghai" --destination "Tokyo" --dep-date 2026-04-01 --sort-type 3

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.

Japan essentials: visa required for Chinese citizens (single/3yr/5yr). Airports: NRT/HND (Tokyo), KIX (Osaka/Kyoto), CTS (Hokkaido), OKA (Okinawa). JR Pass: 7/14/21-day, worthwhile for multi-city. IC cards (Suica/ICOCA) for local transit. Cherry blossom: late Mar-mid Apr. Autumn foliage: mid Nov-early Dec. Ski: Dec-Mar in Hokkaido/Nagano.

References