Skillv1.0.0

ClawScan security

Ai Image To Video Audio · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

ReviewApr 15, 2026, 6:46 PM

Verdict: Review
Confidence: medium
Model: gpt-5-mini
Summary: The skill's behavior largely matches a remote video-rendering service (it needs a NEMO_TOKEN and calls nemovideo.ai APIs), but there are inconsistent declarations (config paths vs registry metadata, required env var vs auto-generation of anonymous token) and vague instructions about where tokens/session IDs are stored — ask for clarification before installing or trusting with files/credentials.
Guidance: This skill appears to call a legitimate cloud video-rendering API and only needs a NEMO_TOKEN, but there are a few unclear points you should confirm before installing: 1) Where and how will session tokens / anonymous tokens be stored? (in memory only or written to disk under ~/.config/nemovideo/?) 2) Do you prefer to supply your own NEMO_TOKEN instead of allowing the skill to obtain an anonymous token (which grants limited, temporary credits)? 3) All media you upload will be sent to https://mega-api-prod.nemovideo.ai — confirm you are comfortable with that service and its privacy/retention policies. If you need stronger guarantees, request explicit behavior (no persistent storage on disk, clear token expiry/cleanup, and a privacy policy or vendor homepage). The metadata mismatches (configPaths vs registry, required env var vs auto-generation) are not by themselves malicious but warrant clarification.

Review Dimensions

Purpose & Capability: noteThe declared purpose (turn images+audio into video via a cloud backend) aligns with requiring a NEMO_TOKEN and calling nemovideo.ai endpoints. However, registry-level metadata said no required config paths while the SKILL.md frontmatter lists ~/.config/nemovideo/ — a mismatch. Also the skill asks to derive X-Skill-Platform from the agent's install path, which implies reading agent filesystem metadata; that is plausible for attribution but is an extra capability not explained in the high-level description.
Instruction Scope: noteInstructions confine actions to the external Nemovideo API (session creation, SSE chat, uploads, export polling). They explicitly read NEMO_TOKEN and, if missing, instruct the agent to obtain an anonymous token automatically. The instructions tell the agent to 'store' session_id and token for subsequent requests but do not specify where/how (memory vs disk vs secure store). They also instruct detecting install path for X-Skill-Platform, which requires access to agent runtime paths. No instructions request unrelated system files or other credentials.
Install Mechanism: okInstruction-only skill with no install spec and no code files — lowest install risk. Nothing is downloaded or written by an installer according to the package metadata.
Credentials: noteOnly one credential (NEMO_TOKEN) is declared as required, which is proportionate for a cloud rendering service. Two inconsistencies: (1) the skill declares NEMO_TOKEN as required but also provides an automatic anonymous-token flow when NEMO_TOKEN is absent; (2) SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata said none. It's unclear whether the skill will read or write that config path.
Persistence & Privilege: okSkill is not always-on and allows normal autonomous invocation. It will create remote render jobs that can persist on the vendor side and asks the agent to retain session tokens/session_ids across calls — expected for a session-based API. There is no instruction to modify other skills or system-wide settings.