Skillv1.0.0

ClawScan security

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

Scanner verdict

BenignApr 19, 2026, 9:40 PM

Verdict: benign
Confidence: medium
Model: gpt-5-mini
Summary: The skill's requests and runtime instructions are generally consistent with a cloud video-generation integration, but there are a few small mismatches (declared config paths vs registry, filesystem/install-path checks, and automatic anonymous token provisioning) you should be aware of before installing.
Guidance: This skill appears to do what it says: call a cloud video API, create sessions, upload files, and return download URLs. Before installing: (1) confirm you trust the domain mega-api-prod.nemovideo.ai and review its privacy/terms, (2) be aware the skill will try to auto-provision an anonymous NEMO_TOKEN if none is provided (it makes a network POST and receives a temporary token), (3) note the skill may read its own SKILL.md frontmatter and check install/config paths (it references ~/.config/nemovideo/ and install-path detection) — if you’re uncomfortable with filesystem access, avoid installing or restrict the agent’s filesystem permissions, (4) do not provide sensitive files unless you understand how uploads are used, and (5) monitor network activity and any stored tokens after first use. If you want higher assurance, ask the skill author to clarify where (if anywhere) tokens are persisted and to remove any unnecessary filesystem/install-path checks.

Review Dimensions

Purpose & Capability: okThe skill is a cloud video-generation frontend and only requests a single service credential (NEMO_TOKEN) that matches that purpose. No unrelated binaries or extra credentials are requested. One inconsistency: the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths.
Instruction Scope: noteRuntime instructions are focused on creating a session, uploading media, sending messages via SSE, polling renders, and returning download URLs — all consistent with a video API. However, the instructions also tell the agent to: (1) read YAML frontmatter and detect the agent's install path to set attribution headers (requires filesystem/installation-path access), and (2) upload arbitrary local files when the user provides them. These filesystem and install-path reads go slightly beyond a purely API-only integration and aren’t reflected in the registry metadata.
Install Mechanism: okThis is an instruction-only skill with no install spec or downloadable code, so nothing is written to disk by an installer. That is the lowest-risk install model.
Credentials: noteThe skill requests a single credential (NEMO_TOKEN) which is proportionate for a cloud API integration. It will also automatically obtain an anonymous token from https://mega-api-prod.nemovideo.ai if NEMO_TOKEN is absent — this behavior is reasonable but worth noting because it involves network calls to provision temporary credentials and may result in the agent holding/storing a token for future calls.
Persistence & Privilege: okThe skill is not always-enabled and does not request system-wide privileges. It does instruct the agent to use session tokens and mentions a config directory in the frontmatter; the SKILL.md does not explicitly instruct persisting tokens to disk, but the combination of configPaths in the frontmatter and filesystem reads suggests the agent might read or write local config if implemented. This is not an elevated privilege by itself, but verify where tokens are stored.