Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Find Hotel Near Attraction

v2.0.0

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...

0· 99·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for dingtom336-gif/flyai-find-hotel-near-attraction.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Find Hotel Near Attraction" (dingtom336-gif/flyai-find-hotel-near-attraction) from ClawHub.
Skill page: https://clawhub.ai/dingtom336-gif/flyai-find-hotel-near-attraction
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install flyai-find-hotel-near-attraction

ClawHub CLI

Package manager switcher

npx clawhub@latest install flyai-find-hotel-near-attraction
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
medium confidence
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.
Assessment
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.

Like a lobster shell, security has layers — review code before you run it.

latestvk97c4nyaswnwtemsj80nq6bpas842jdk
99downloads
0stars
2versions
Updated 3w ago
v2.0.0
MIT-0

⚠️ 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)

ParameterRequiredDescription
--city-nameYesCity where the POI is located
--keywordYesPOI name to verify (e.g., "West Lake", "Forbidden City")

Command 2: search-hotels (core search)

ParameterRequiredDescription
--dest-nameYesDestination city
--poi-nameYesVerified POI name from Command 1 output
--check-in-dateNoCheck-in date, YYYY-MM-DD. Default: today
--check-out-dateNoCheck-out date. Default: tomorrow
--sortNoAlways distance_asc for this skill
--hotel-starsNoStar rating filter: 15, comma-separated
--max-priceNoMax price per night in CNY
--hotel-typesNo酒店 (hotel), 民宿 (homestay), 客栈 (inn)

Sort Options

ValueDescription
distance_ascDistance ascending (default for this skill)
rate_descRating descending
price_ascPrice ascending
price_descPrice 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 < 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 "<1km" 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 < 3 results

References

FilePurposeWhen to read
references/templates.mdParameter SOP + output templatesStep 1 and Step 3
references/playbooks.md4 POI-type playbooksStep 2b
references/fallbacks.md6 failure recovery pathsOn failure
references/runbook.mdExecution log schemaBackground

Comments

Loading comments...