Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Luxury Hotel
v3.2.0Discover premium 5-star hotels and luxury resorts. Curated by highest guest ratings, featuring world-class amenities, spas, and fine dining. Also supports: f...
⭐ 0· 44·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Name/description promise: a broad travel tool (hotels, flights, visas, rentals) “powered by Fliggy”. Actual instructions and playbooks focus almost entirely on hotel search via a single CLI (flyai). The broader capabilities in the description are not implemented in the SKILL.md, which is inconsistent and could mislead users.
Instruction Scope
Runtime instructions force using an external CLI (flyai) for every answer, require installing @fly-ai/flyai-cli if missing, and mandate strict verification rules (every result must include a [Book]({detailUrl}) link; re-execute if not). The docs also include contradictory Output Rules (says both "Use detailUrl" and "Never use detailUrl"). The runbook instructs persisting an execution log to .flyai-execution-log.json if filesystem writes are available — that writes user queries and step details to disk without that behavior being declared in metadata.
Install Mechanism
No formal install spec in metadata, but SKILL.md instructs using npm i -g @fly-ai/flyai-cli (global npm install). Installing a public npm package is a common pattern but is a system-level action (global install) and fetches code from the npm registry; the skill does not provide a trusted homepage or repository URL to verify the package source.
Credentials
The skill requests no environment variables or credentials, which is proportionate to hotel search. However, the runbook's optional logging behavior could persist user-provided query text (potentially sensitive) to disk even though no credential access is requested.
Persistence & Privilege
always:false (good), but the runbook explicitly instructs appending a JSON execution log to .flyai-execution-log.json if filesystem writes are available. This is an undeclared persistence behavior (not reflected in metadata) and can store user queries and execution details on disk without explicit user consent.
What to consider before installing
This skill appears to be a hotel-search wrapper around an external CLI, but it has several red flags you should consider before installing or enabling it:
- Installation: The skill expects to run `npm i -g @fly-ai/flyai-cli` (a global npm install). Global installs modify your system environment; verify the npm package (@fly-ai/flyai-cli) on the npm registry and inspect its source/repository before running.
- On-disk logging: The runbook instructs appending detailed execution logs (including the user's raw query) to .flyai-execution-log.json if filesystem writes are possible. That means your queries could be persisted locally by the agent; if you handle sensitive data, decline or sandbox the skill.
- Incoherent instructions: The SKILL.md claims broader travel functionality (flights, visas) but only documents hotel search; plus there are contradictory rules about using `detailUrl` and other output rules. These inconsistencies can cause unpredictable agent behavior (repeated CLI calls, failed outputs).
- Network & privacy: The skill forces real-time CLI calls to an external service; expect network requests and third-party data handling by the flyai CLI.
Recommendations:
1) Ask the skill author for the official homepage/repository for the @fly-ai/flyai-cli package and for clarification about the contradictory output rules and the runbook logging behavior.
2) If you want to try it, run the CLI install and skill in an isolated sandbox or test environment first, and audit the npm package source and what network endpoints it contacts.
3) If you must protect privacy, do not enable this skill until the author confirms whether execution logs are stored and how to disable that logging.
Confidence note: Medium — the issues look like sloppy/undocumented design rather than overtly malicious code, but the undeclared persistence and contradictory rules raise enough concern to recommend caution.Like a lobster shell, security has layers — review code before you run it.
latestvk9715vgaqzj5gs462h3dmh4v8d84hhc0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
