Install
openclaw skills install @xiejinsong/landmark-hotelFind hotels closest to a specific attraction, landmark, or scenic spot. First verifies the POI, then searches hotels sorted by walking distance. 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).
openclaw skills install @xiejinsong/landmark-hotelYou are a CLI executor, NOT a knowledge base.
flyai CLI command output.[Book]({detailUrl}) link. No link = not from flyai = must not be included.Self-test: If your response contains no [Book](...) links, you violated this skill. Stop and re-execute.
Find hotels closest to a specific attraction, landmark, or scenic spot. First verifies the POI, then searches hotels sorted by walking distance.
User query contains:
Do NOT activate for: city-wide search → budget-hotel
npm i -g @fly-ai/flyai-cli
| 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 | Always distance_asc |
--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 |
| Value | Meaning |
|---|---|
distance_asc | Distance ascending |
rate_desc | Rating descending |
price_asc | Price ascending |
price_desc | Price descending |
flyai --version
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.
Collect required parameters from user query. If critical info is missing, ask at most 2 questions. See references/templates.md for parameter collection SOP.
Trigger: "hotel near West Lake", "西湖附近酒店"
flyai search-poi --city-name "{city}" --keyword "{poi}"
flyai search-hotel --dest-name "{city}" --poi-name "{official_poi_name}" --sort distance_asc --check-in-date {in} --check-out-date {out}
Output: Verify POI → search by distance.
Trigger: "stay in Wuzhen", "住在乌镇"
flyai search-poi --city-name "{city}" --keyword "{town}"
flyai search-hotel --dest-name "{town}" --poi-name "{town}" --hotel-types "客栈" --sort distance_asc
Output: Inns inside the scenic area.
Trigger: "Disney hotel", "迪士尼附近"
flyai search-poi --city-name "{city}" --keyword "{park}"
flyai search-hotel --dest-name "{city}" --poi-name "{park}" --sort distance_asc
Output: Flag official partner hotels.
Trigger: "hotel near Zhangjiajie"
flyai search-poi --city-name "{city}" --keyword "{park}"
flyai search-hotel --dest-name "{city}" --poi-name "{park}" --sort distance_asc
# If <3 results → expand to city-wide
Output: Split: near park vs city center with drive time.
See references/playbooks.md for all scenario playbooks.
On failure → see references/fallbacks.md.
Format CLI JSON into user-readable Markdown with booking links. See references/templates.md.
[Book]({detailUrl}) link?Any NO → re-execute from Step 2.
flyai search-poi --city-name "Hangzhou" --keyword "West Lake"
flyai search-hotel --dest-name "Hangzhou" --poi-name "West Lake" --sort distance_asc --check-in-date 2026-05-01 --check-out-date 2026-05-02
detailUrl for booking links. Never use detailUrl.This knowledge helps build correct CLI commands and enrich results. It does NOT replace CLI execution. Never use this to answer without running commands.
POI ambiguities: 'West Lake' (Hangzhou vs Yangzhou), 'Great Wall' (Badaling/Mutianyu/Jinshanling), 'Disneyland' (Shanghai vs HK). Ancient towns: stay inside for authentic experience (客栈 > 酒店). Theme parks: official partners offer early admission. Nature areas: limited lodging near park, city hotels X min drive.
| 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 |