Back to skill
Skillv1.0.7
ClawScan security
Dlazy Banana2 · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
BenignApr 29, 2026, 2:46 AM
- Verdict
- benign
- Confidence
- high
- Model
- gpt-5-mini
- Summary
- The skill is an instruction-only wrapper for the dLazy CLI and its requirements (npm/npx, optional DLAZY_API_KEY, and the dlazy endpoints) are coherent with the stated purpose of running the Nano Banana 2.0 image generation CLI.
- Guidance
- This skill is a thin wrapper around the official dLazy CLI and appears internally consistent. Before installing or using it: 1) Prefer npx @dlazy/cli@1.0.8 if you don't want a global install; 2) Review the GitHub repo and the npm package (version pinned to 1.0.8) to ensure you trust the code you will run; 3) Be aware any local image/video paths you pass will be uploaded to oss.dlazy.com and that your API key will be stored in ~/.dlazy/config.json (or provided via DLAZY_API_KEY); 4) Check dLazy's privacy, billing, and content policies and ensure you have sufficient credits (the skill instructs the agent to notify users about insufficient_balance); 5) Use a least-privilege/rotatable API key and rotate/revoke it if you stop using the service. No scanner findings were present, but that is expected for an instruction-only skill — review upstream source before running installs.
Review Dimensions
- Purpose & Capability
- okName/description (Nano Banana 2.0 image generation) match the runtime instructions and metadata: the skill tells the agent to run the @dlazy/cli 'banana2' command, lists api.dlazy.com and oss.dlazy.com as endpoints, and declares npm/npx for installing/invoking the CLI. There are no unrelated credentials, binaries, or config paths requested.
- Instruction Scope
- okSKILL.md directs the agent only to use the dLazy CLI (dlazy banana2), to supply an API key via dlazy auth set or DLAZY_API_KEY, and to upload user-specified local media (which the CLI will send to oss.dlazy.com). It does not instruct reading arbitrary system files, exfiltrating unrelated data, or calling endpoints outside the declared service. Note: the CLI will upload any local file paths you pass, so local files you provide will be transmitted to the dLazy service.
- Install Mechanism
- noteThere is no automatic install spec in the registry (instruction-only), but the metadata and docs recommend npm install -g @dlazy/cli@1.0.8 or using npx @dlazy/cli@1.0.8. Installing from npm is expected for a CLI skill, but it does mean code will be fetched from the public npm registry (moderate risk compared to instruction-only). If you prefer not to persist software, use npx to avoid a global install.
- Credentials
- okThe skill does not require unrelated secrets. It optionally uses DLAZY_API_KEY (or the CLI-managed config at ~/.dlazy/config.json) which is proportionate to the service. The config file location is declared; users should be aware their API key will be stored in that user-scoped file by the CLI.
- Persistence & Privilege
- okThe skill does not request 'always: true' or elevated platform privileges. It is user-invocable and may be invoked autonomously by agents (normal default). It does not modify other skills or system-wide settings beyond the CLI's own config file.
