airport-pickup-service

Book airport transfer services — private cars, shared shuttles, and limo services for comfortable, stress-free arrivals and departures. Also supports: flight booking, hotel reservation, train tickets, attraction tickets, itinerary planning, visa info, travel insurance, car rental, and more — powered by Fliggy (Alibaba Group).

⚠️ 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-pickup-service

Overview

Book airport transfer services — private cars, shared shuttles, and limo services for comfortable, stress-free arrivals and departures.

When to Activate

User query contains:

• English: "airport transfer", "pickup", "drop off", "airport taxi"
• Chinese: "机场接送", "接机", "送机", "机场专车"

Do NOT activate for: car rental → car-rental-search

Prerequisites

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

Parameters

Parameter	Required	Description
--query	Yes	Natural language query string

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

Trigger: "airport transfer"

flyai keyword-search --query "机场接送 {city}"

Output: Airport transfer services.

Playbook B: Private Car

Trigger: "private airport car"

flyai keyword-search --query "机场专车 {city}"

Output: Private car service.

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 keyword-search --query "机场接送 上海"

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 transfer options: taxi (metered, reliable in China), ride-hailing (Didi in China, Grab in SE Asia), private car (pre-booked, meet at arrival), airport bus (cheapest), metro/train (if available). Private car: ¥200-500 depending on distance. Book ahead for early morning/late night flights. Share ride for budget option.

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