Skillv1.0.5

ClawScan security

Dlazy Wan2.7 · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

SuspiciousApr 29, 2026, 2:36 AM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The skill largely matches its stated purpose (a thin CLI client for a video-generation SaaS) but there are small inconsistencies and a missing declaration around credentials and installation that you should review before installing or using it.
Guidance: This skill appears to be a thin CLI wrapper for dlazy's video-generation service and is coherent with that purpose, but take these precautions before using it: 1) Verify the CLI source on GitHub and the npm package version (@dlazy/cli@1.0.8) before running npm install -g; prefer using npx to avoid globally installing unfamiliar code. 2) Be aware that any local images/videos you provide will be uploaded to dlazy's OSS (oss.dlazy.com) — do not send sensitive or private media unless the service and your organization allow it. 3) The skill requires an API key (DLAZY_API_KEY or dlazy auth set), but the registry metadata did not declare this; confirm how the key is stored (~/.dlazy/config.json) and ensure it is scoped and revocable. 4) Check billing/credits and the referenced dlazy dashboard links before running the skill to avoid unexpected charges. 5) If you need higher confidence, ask the publisher for a signed release, checksum for the npm package, or an explicit install spec in the registry, and inspect the CLI repository for malicious behaviors (network calls to unexpected endpoints, secret exfiltration, or post-install scripts).

Review Dimensions

Purpose & Capability: noteName/description match the behavior described: it is a thin client that sends prompts and media to dlazy's API and stores results on oss.dlazy.com. Required binaries (npm, npx) are reasonable given the SKILL.md recommends using the @dlazy/cli npm package. No unrelated services or credentials are requested in the registry metadata.
Instruction Scope: noteRuntime instructions are narrowly focused on invoking the dlazy CLI (dlazy wan2.7). They explicitly state that local files you pass will be uploaded to dlazy's OSS endpoint and that an API key must be configured. The instructions do not ask the agent to read arbitrary system files beyond the user's provided media and the CLI config (~/.dlazy/config.json), which is consistent with the service's purpose. The agent is also instructed to surface billing/auth errors and links to the dlazy dashboard.
Install Mechanism: noteThe registry lists no formal install spec (the skill is instruction-only), but the SKILL.md metadata includes a pinned npm install command and npx alternative. Installing an npm package (npm install -g @dlazy/cli@1.0.8) is a standard but nontrivial action because npm packages can run arbitrary code during install. The presence of a pinned version is good; prefer on-demand npx usage and review the GitHub repo before global installation.
Credentials: concernThe SKILL.md clearly requires an API key (DLAZY_API_KEY or stored via dlazy auth set into ~/.dlazy/config.json), but the registry metadata lists no required environment variables. This mismatch (declared requires.env: none vs. instructions requiring an API key) is an inconsistency to resolve. Also note the CLI stores your key in a user config file in your home directory — the doc claims file permissions are restricted, but you should verify this and prefer scoped API keys that can be rotated/revoked.
Persistence & Privilege: okalways:false and no OS restrictions — the skill does not request forced global presence or elevated privileges. It writes its own config under the user's home directory (expected) and does not claim to modify other skills or system-wide agent settings.