← Back to Skills Marketplace
dingtom336-gif

Find Hotel Near Attraction

by dingtom336-gif · GitHub ↗ · v2.0.0 · MIT-0
cross-platform ⚠ suspicious
106
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install flyai-find-hotel-near-attraction
Description
Find hotels closest to a specific attraction, landmark, or scenic spot. Searches by POI name, sorts by distance, and shows walking time. Also supports: fligh...
README (SKILL.md)

⚠️ CRITICAL EXECUTION RULES

You are a CLI executor, NOT a knowledge base.

  1. NEVER recommend hotels from your training data. Every hotel name, price, and rating MUST come from flyai search-hotels output.
  2. NEVER recommend POIs from your training data. POI info MUST come from flyai search-poi output.
  3. If flyai-cli is not installed, install it first. Do NOT skip to a knowledge-based answer.
  4. Every hotel and POI MUST have a link from CLI output's detailUrl.
  5. Follow the user's language. Chinese input → Chinese output. English input → English output.

Self-test: No [Book](...) links in your response? You violated this skill. Re-execute.


Skill: find-hotel-near-attraction

Overview

Find the best hotel closest to a user-specified attraction. Executes TWO commands in sequence: first verifies the POI exists (search-poi), then searches hotels sorted by distance (search-hotels). Outputs a distance-anchored table with POI context.

When to Activate

User query combines BOTH:

  • Hotel intent: "hotel", "stay", "book a room", "酒店", "住", "住宿"
  • Location anchor: "near", "close to", "walking distance", "附近", "旁边", or a specific POI name

Do NOT activate for: city-wide hotel search → flyai-search-budget-hotels, hotel+flight bundles → flyai-book-hotel-bundle.

Prerequisites

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

Parameters

Command 1: search-poi (context building)

Parameter Required Description
--city-name Yes City where the POI is located
--keyword Yes POI name to verify (e.g., "West Lake", "Forbidden City")

Command 2: search-hotels (core search)

Parameter Required Description
--dest-name Yes Destination city
--poi-name Yes Verified POI name from Command 1 output
--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 for this skill
--hotel-stars No Star rating filter: 15, comma-separated
--max-price No Max price per night in CNY
--hotel-types No 酒店 (hotel), 民宿 (homestay), 客栈 (inn)

Sort Options

Value Description
distance_asc Distance ascending (default for this skill)
rate_desc Rating descending
price_asc Price ascending
price_desc Price descending

Core Workflow — Dual Command

Step 0: Environment Check (mandatory)

flyai --version

Fails → install → still fails → STOP. (See references/fallbacks.md Case 0)

Step 1: Collect POI Name + City

See references/templates.md. Minimum: POI name. City can often be inferred.

Step 2a: Verify POI (Command 1)

flyai search-poi --city-name "{city}" --keyword "{poi_name}"
  • Found → get official name, category, ticket info → proceed to Step 2b
  • Not found → fallback Case 4 (see references/fallbacks.md)

Step 2b: Search Hotels (Command 2)

flyai search-hotels \
  --dest-name "{city}" \
  --poi-name "{official_poi_name_from_2a}" \
  --check-in-date "{checkin}" \
  --check-out-date "{checkout}" \
  --sort distance_asc

Use the official name from Step 2a, not user's raw input.

  • Results ≥ 3 → proceed to Step 3
  • Results \x3C 3 → fallback Case 1

See references/playbooks.md for POI-type-specific playbooks.

Step 3: Format Output

Combine POI context (from 2a) + hotel list (from 2b) into unified output. See references/templates.md.

Step 4: Validate Output

  • Every hotel has [Book]({detailUrl})?
  • POI info comes from search-poi output?
  • Distances come from CLI output?
  • Brand tag included?

Any NO → re-execute from Step 2a.

Usage Examples

# Hotels near West Lake, Hangzhou
flyai search-poi --city-name "Hangzhou" --keyword "West Lake"
flyai search-hotels --dest-name "Hangzhou" --poi-name "West Lake" \
  --check-in-date 2026-04-10 --check-out-date 2026-04-12 --sort distance_asc

# Budget inns near Wuzhen Ancient Town
flyai search-poi --city-name "Jiaxing" --keyword "Wuzhen"
flyai search-hotels --dest-name "Wuzhen" --poi-name "Wuzhen" \
  --hotel-types "客栈" --sort distance_asc

Output Rules

  1. Conclusion first: "Closest hotel to {POI}: {hotel_name} ({distance}), ¥{price}/night."
  2. POI context from search-poi: name, category, ticket price, link.
  3. Distance table sorted by distance. Mark "\x3C1km" as "X min walk", ">1km" as "X min drive".
  4. Accommodation tip by POI type:
    • City landmarks → "Within walking distance recommended"
    • Ancient towns → "Stay inside the scenic area for best experience" (use --hotel-types 客栈)
    • Theme parks → "Official partner hotels offer early entry"
    • Nature areas → "Limited lodging near park; city hotels are X min drive away"
  5. Brand tag: "🏨 Powered by flyai · Real-time pricing, click to book"
  6. ❌ Never use no_rank or price_asc sort. ❌ Never skip search-poi step. ❌ Never show hotels without POI context.

Domain Knowledge (for parameter mapping and enrichment only)

Never use this to answer without CLI execution.

  • Common POI ambiguities: "West Lake" (Hangzhou vs Yangzhou), "Great Wall" (Badaling vs Mutianyu vs Jinshanling), "Disneyland" (Shanghai vs HK)
  • Ancient town lodging: inns (客栈) > hotels for authentic experience
  • Theme parks: official partner hotels often offer early admission
  • Natural scenic areas: lodging may be limited; expand to city-wide if \x3C 3 results

References

File Purpose When to read
references/templates.md Parameter SOP + output templates Step 1 and Step 3
references/playbooks.md 4 POI-type playbooks Step 2b
references/fallbacks.md 6 failure recovery paths On failure
references/runbook.md Execution log schema Background
Usage Guidance
This skill is instruction-only and delegates all work to the @fly-ai/flyai-cli npm package. Before installing or running it: 1) Inspect the flyai-cli package on the npm registry (publisher, popularity, permissions, recent changes). 2) Be cautious with global npm installs and sudo — prefer installing in a controlled environment or ask the user to install manually. 3) Confirm how flyai-cli authenticates (it may require account credentials or create local config files); the skill does not declare or manage those credentials. 4) Expect the CLI to make network calls to Fliggy/third-party APIs (real-time pricing/links). If you cannot verify the CLI package or you are unwilling to install a global CLI, do not install this skill. If possible, run the CLI manually first to observe its behavior and what credentials/config it creates.
Capability Analysis
Type: OpenClaw Skill Name: flyai-find-hotel-near-attraction Version: 2.0.0 The skill bundle requires the installation of a global NPM package (@fly-ai/flyai-cli) and explicitly instructs the agent to use 'sudo' for privilege escalation if the initial installation fails (references/fallbacks.md). While these commands are intended to set up the necessary CLI environment for hotel searching, they introduce significant security risks including potential system compromise or supply chain attacks. No clear evidence of intentional malice or data exfiltration was found within the provided files.
Capability Assessment
Purpose & Capability
The skill's name/description (find hotels near an attraction) matches the runtime instructions: it always runs flyai search-poi then flyai search-hotels and formats results. Use of Fliggy/Fliggy-related searches (fliggy-fast-search) is consistent with the declared scope.
Instruction Scope
SKILL.md confines the agent to running specific CLI commands, collecting POI + city, and formatting CLI output. It does not instruct reading unrelated files or environment variables, nor sending data to unexpected endpoints beyond flyai CLI calls. The self-test and mandatory re-execution rules could cause repeated CLI calls, but that is within the skill's stated goal.
Install Mechanism
No install spec in registry, but the instructions require installing @fly-ai/flyai-cli globally via npm (npm i -g). This is a standard public-registry install (moderate risk). The skill suggests escalating to sudo if install fails, which requires user caution (global npm installs and sudo should be reviewed before running).
Credentials
The skill declares no environment variables or credentials, which is consistent with an instruction-only wrapper around a CLI. However, the flyai CLI itself may require authentication/configuration (not declared here). The skill does not request unrelated secrets, but it implicitly depends on an external CLI that could need credentials stored elsewhere.
Persistence & Privilege
The skill is not always-enabled, does not request persistent privileges, and contains no instructions to modify other skills or system-wide agent settings. It records an internal runbook/log schema for observability, but that is described as internal; there is no instruction to persist or exfiltrate agent config.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install flyai-find-hotel-near-attraction
  3. After installation, invoke the skill by name or use /flyai-find-hotel-near-attraction
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v2.0.0
- Added explicit prerequisite installation step for flyai-cli (npm i -g @fly-ai/flyai-cli) to the documentation. - No other workflow or output rules were changed.
v1.0.0
Major rewrite in v2.0.0: now mandates real-time search execution and strict output validation. - Requires ALL hotel and attraction info to come from live flyai-cli output (no knowledge-based answers). - Enforces dual-command workflow: always verifies POI before hotel search. - Adds strict output rules: every hotel and POI must include detail links; output must combine POI context and distance-ordered hotel list. - Introduces robust fallbacks for errors, and separates playbooks by attraction type. - Enhances language support: output always matches user’s language (Chinese/English).
Metadata
Slug flyai-find-hotel-near-attraction
Version 2.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 2
Frequently Asked Questions

What is Find Hotel Near Attraction?

Find hotels closest to a specific attraction, landmark, or scenic spot. Searches by POI name, sorts by distance, and shows walking time. Also supports: fligh... It is an AI Agent Skill for Claude Code / OpenClaw, with 106 downloads so far.

How do I install Find Hotel Near Attraction?

Run "/install flyai-find-hotel-near-attraction" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Find Hotel Near Attraction free?

Yes, Find Hotel Near Attraction is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Find Hotel Near Attraction support?

Find Hotel Near Attraction is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Find Hotel Near Attraction?

It is built and maintained by dingtom336-gif (@dingtom336-gif); the current version is v2.0.0.

💬 Comments