Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Surfing Diving
v3.2.0Find surfing beaches, diving sites, and underwater adventures — wave forecasts, dive depth, marine life info, and equipment rental. Also supports: flight boo...
⭐ 0· 43·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 explicitly requires the third‑party CLI 'flyai' (instructions: npm i -g @fly-ai/flyai-cli and many flyai commands), but the registry metadata lists no required binaries or install steps. That mismatch is incoherent: a travel/booking skill legitimately needs a provider CLI, so requiring a CLI is expected, but the metadata failing to declare it reduces transparency and is unexpected.
Instruction Scope
SKILL.md forces every answer to come from flyai CLI output and forbids using training data. It also contains a runbook that (optionally) writes an execution log including the raw user query and commands to '.flyai-execution-log.json' if filesystem writes are available. Persisting raw user queries and command outputs to disk is outside the normal scope of simply returning POI results and raises data‑persistence/privacy concerns.
Install Mechanism
There is no install spec in the registry, yet the instructions demand a global npm install (-g) of @fly-ai/flyai-cli. Global npm installs execute maintainer-supplied code and can modify the system PATH; combined with the package being from an unknown source (no homepage/repo provided), this is a risk. The skill provides no checksum/release provenance for the CLI.
Credentials
No environment variables or credentials are requested — which is plausible if the flyai CLI handles authentication internally — but the runbook's logging of raw user queries and CLI calls means sensitive input could be persisted. Also, the SKILL.md enforces including booking links and relies entirely on CLI output rather than declaring any required auth, which is unusual but not impossible.
Persistence & Privilege
always:false and no special platform privileges are declared, but the instructions instruct a global npm install and optionally appending execution logs to a local file. Both actions modify the host environment (global packages and local files). The skill does not request explicit permission or document where logs may be stored or transmitted.
What to consider before installing
Before installing or enabling this skill, consider the following: (1) The skill requires installing a global npm package (@fly-ai/flyai-cli) but the registry metadata doesn't declare this — verify the package source and inspect its code or repository on npm/GitHub. Global npm installs run maintainer code and can alter your system PATH. (2) The skill's runbook suggests writing execution logs that include raw user queries to .flyai-execution-log.json — decide whether you want those query histories written to disk and confirm whether they are kept locally or transmitted elsewhere. (3) Ask the publisher for the CLI's homepage/repo, package checksum, and a privacy statement describing how booking requests and logs are handled. (4) If you must try it, run the CLI in a sandbox/container or avoid global install (use a VM or isolated environment), and audit the npm package first. Providing the skill author’s source repo or the flyai-cli project page would raise confidence; without that, proceed cautiously.Like a lobster shell, security has layers — review code before you run it.
latestvk9772gzjw4zca192st4agvma9184mwck
License
MIT-0
Free to use, modify, and redistribute. No attribution required.