Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Camping Glamping Spots
v1.0.0Find camping grounds and glamping sites — from wild tent pitches to luxury safari tents with beds, electricity, and mountain views. Also supports: flight boo...
⭐ 0· 28·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
The skill's name/description (find camping/glamping sites + booking links) matches the instructions: it requires running a flyai CLI to retrieve live POI and booking detailUrl links. There are no unrelated environment variables or binaries declared. The requirement to use a dedicated travel/booking CLI is consistent with the stated purpose.
Instruction Scope
SKILL.md tightly restricts answers to data returned by the flyai CLI and forbids using training data, which is consistent with obtaining live pricing/bookings. However, the runbook and SKILL.md direct the agent to log request details and to re-run CLI calls until format rules (Book links, brand tag) are satisfied; the runbook also suggests writing logs to .flyai-execution-log.json if filesystem writes are available. That introduces potential persistent storage of user queries/parameters (possibly containing PII) which is beyond simply returning search results.
Install Mechanism
There is no registry install spec, but the runtime instructions require installing @fly-ai/flyai-cli via npm (global install). Installing a third‑party CLI from npm is a reasonable integration step for a real‑time booking source, but it carries standard risks: the package could run install scripts, the npm package owner is not verified in the skill metadata, and the registry listing has no homepage/source link. Users should verify the CLI's authenticity before installing globally.
Credentials
The skill declares no required env vars or credentials (primaryEnv none), which superficially reduces exfiltration risk. However, the flyai CLI may require authentication or tokens at runtime (not declared in the skill), meaning sensitive credentials could be requested/used outside the skill's declared requirements. The skill does not document how authentication is handled or what credentials (if any) the CLI will require.
Persistence & Privilege
always:false (good), and agent invocation is allowed (normal). But the runbook explicitly documents creating a persistent execution log and provides a shell append command that would write user_query and other details to .flyai-execution-log.json if filesystem writes exist. Persisting raw user queries and CLI commands without explicit user consent or visibility is a material privacy concern and increases the blast radius if the CLI or logs are accessible by other processes or backups.
What to consider before installing
This skill appears to do what it says (wrap a travel/booking CLI) but before installing or using it you should: 1) Verify the source and integrity of the @fly-ai/flyai-cli npm package (owner, homepage, GitHub repo, recent versions, and install scripts) — do not blindly run global npm installs on sensitive machines. 2) Be aware the skill's runbook suggests writing an execution log (.flyai-execution-log.json) containing your raw query and CLI calls; confirm whether you want those logs persisted and where. 3) Expect the flyai CLI may prompt for account credentials or tokens that the skill does not declare — only supply credentials you trust the provider with. 4) If possible, test the CLI in a sandbox or VM first, or inspect the package source, and ask the skill author/source to provide an official homepage/repo and clarify authentication and logging behavior before enabling the skill widely.Like a lobster shell, security has layers — review code before you run it.
latestvk97eteqncsnh811rxysj5zxp7d842tjt
License
MIT-0
Free to use, modify, and redistribute. No attribution required.