Skillv1.0.0

ClawScan security

Photo Video Youtube · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

BenignApr 11, 2026, 8:08 PM

Verdict: benign
Confidence: high
Model: gpt-5-mini
Summary: The skill's requirements and runtime instructions align with its stated purpose (remote cloud video rendering) and do not request unrelated secrets or install code, but it will send user photos and token-bearing requests to an external service (nemovideo.ai).
Guidance: This skill will upload whatever photos or media you provide to mega-api-prod.nemovideo.ai and will use a NEMO_TOKEN (or obtain an anonymous short-lived token) to perform rendering on remote GPU nodes. Before installing or using it: (1) confirm you trust nemovideo.ai and are comfortable uploading the images you give it (no sensitive/private content); (2) avoid supplying any unrelated credentials — only provide a NEMO_TOKEN if you understand its scope; (3) note the skill may store a session_id/token for the session lifecycle — prefer anonymous tokens or limited-scope tokens if available; (4) if you want to avoid external uploads, do not use this skill. If you want deeper assurance, ask the publisher for a privacy/data-retention policy and for clarification why ~/.config/nemovideo/ is declared in metadata.

Review Dimensions

Purpose & Capability: okName and description (turn photos into YouTube-ready videos) match the instructions: uploads, session creation, SSE-driven generation, and export endpoints for a cloud rendering backend. Requesting a NEMO_TOKEN (primary credential) is coherent for a hosted API.
Instruction Scope: noteInstructions are focused on API calls, uploads, SSE handling, and exports. They instruct obtaining an anonymous token if none exists and to keep session_id for operations. Minor scope oddity: headers include an X-Skill-Platform value derived from an install path and metadata lists a config path (~/.config/nemovideo/), but the runtime steps do not clearly require reading arbitrary system files beyond checking for NEMO_TOKEN and determining an install path string — this is plausible but worth noting.
Install Mechanism: okNo install spec or code files are present (instruction-only), so nothing is written to disk or downloaded by the skill itself. This is the lowest-risk install surface.
Credentials: noteOnly NEMO_TOKEN is declared as required (primaryEnv). That is proportionate for a cloud API client. The metadata also lists a config path (~/.config/nemovideo/), which may imply optional local config access; the SKILL.md does not explicitly read other environment variables or unrelated credentials.
Persistence & Privilege: okSkill is not always-enabled and uses normal autonomous invocation. It does not request elevated or system-wide persistent privileges in its instructions.