Skillv1.0.0

ClawScan security

Video Generator Free Credits · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

ReviewApr 13, 2026, 10:28 AM

Verdict: Review
Confidence: medium
Model: gpt-5-mini
Summary: The skill appears to implement a video-generation client against an external NemoVideo API (consistent with its description) but contains small inconsistencies and privacy/scope concerns (unknown source, frontmatter asks to read local config/install paths, and it will upload user media and obtain networked anonymous tokens).
Guidance: This skill implements a client for an external NemoVideo service and will upload your media and create ephemeral (or anonymous) tokens on mega-api-prod.nemovideo.ai. Before installing, consider: 1) The skill's source and homepage are unknown — there's no publisher website or documentation to verify the service or its privacy policy. 2) Uploaded files (videos, images, audio) and prompts are sent to a third party — do not upload sensitive personal or proprietary material. 3) The SKILL.md probes local install paths (~/.clawhub/, ~/.cursor/skills/) and references a local config path (~/.config/nemovideo/) in its frontmatter; ask the author why filesystem checks are needed or request they be removed if unnecessary. 4) You can pre-set your own NEMO_TOKEN (from a trusted account) instead of allowing the skill to auto-obtain an anonymous token. 5) If you need stronger assurance, ask the publisher for a homepage/terms/privacy link, or only enable the skill in a sandboxed environment. These issues are concerning but not definitive proof of malicious intent.

Review Dimensions

Purpose & Capability: noteName/description match the runtime instructions: the SKILL.md drives an external video rendering API and requires a NEMO_TOKEN. Requiring a token for a video service is proportionate. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) and install-path detection logic that was not listed in the registry metadata (which showed no required config paths) — this mismatch is unexpected.
Instruction Scope: concernInstructions tell the agent to call multiple remote endpoints (auth anonymous-token, create session, SSE run, upload, render) and to upload user files to the external API — that is expected for a cloud video service. But the skill also instructs detecting the agent install path (~/.clawhub/, ~/.cursor/skills/) and reading its own frontmatter at runtime to set attribution headers. Reading filesystem paths to determine platform presence is scope-creep and could leak information about the user's environment; the SKILL.md also asks the agent to 'store the returned session_id' without specifying persistence boundaries. Overall the network/file-read behavior is coherent with the service but includes operations (local path probes) that should be explicitly justified.
Install Mechanism: okInstruction-only skill with no install spec or code files; nothing is written to disk by the skill itself during installation. This is the lowest install risk.
Credentials: noteThe skill declares a single primary credential NEMO_TOKEN, which is appropriate for an API-backed video generator. The SKILL.md will also auto-obtain an anonymous token if NEMO_TOKEN is not set. The frontmatter mentions a config path (~/.config/nemovideo/) that would grant broader local access if used — that was not declared in the registry's required config paths (inconsistency). No unrelated credentials are requested.
Persistence & Privilege: okalways:false and no install-time persistence or system-wide config modifications are requested. The skill does ask to retain session_id for subsequent API calls (normal for a client) but does not request permanent privileges or to alter other skills' configurations.