Skillv1.0.0

ClawScan security

Ai Video Maker From Script · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

SuspiciousApr 16, 2026, 4:42 PM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The skill's requirements and runtime instructions mostly match a cloud video-rendering tool, but small inconsistencies (local config path mention, explicit multipart file-path upload instructions, and a mismatch between frontmatter and registry metadata) leave ambiguity about what local data the agent may access and whether the claimed config path will be read.
Guidance: This skill appears to be a remote video-rendering front-end and only needs a NEMO_TOKEN to call the service; that is reasonable. Before installing, consider: 1) If you provide a real NEMO_TOKEN, it grants the skill access to your account — ensure the token's scope and trust in the nemo domain. 2) The instructions mention uploading files by local path and reference a local config directory (~/.config/nemovideo/). Confirm whether the agent will access files from your machine or only user-supplied attachments; if you don't want local files read, avoid granting filesystem access or remove local files from the agent context. 3) The skill will create an anonymous token automatically if none is present — understand that creates a short-lived credential tied to the external API. 4) If you need higher assurance, ask the publisher for clarification about file-upload behavior and the claimed config path, and verify the API domain (mega-api-prod.nemovideo.ai) is the official service. Because of these small inconsistencies, proceed cautiously and avoid providing high-privilege or unrelated credentials.

Review Dimensions

Purpose & Capability: okName/description describe converting scripts to videos and the SKILL.md documents an API-based cloud render pipeline that aligns with that purpose (session creation, SSE for edits, upload, export endpoints). Requesting a NEMO_TOKEN credential is coherent for a hosted service.
Instruction Scope: concernMost instructions stay within the video-rendering domain, but the doc explicitly shows a multipart upload form using a local path (-F "files=@/path") and the frontmatter metadata lists a config path (~/.config/nemovideo/). The registry metadata reported no required config paths. This creates ambiguity about whether the agent will read local files/configs beyond user-provided attachments.
Install Mechanism: okInstruction-only skill with no install spec and no code files — lowest install risk. Nothing is downloaded or written to disk by an install step.
Credentials: noteOnly one credential is requested (NEMO_TOKEN), which fits a remote API. The SKILL.md also describes obtaining an anonymous token from https://mega-api-prod.nemovideo.ai when NEMO_TOKEN is absent; this is plausible but means the skill will create and use temporary credentials if a permanent token isn't provided. The frontmatter's configPaths entry (~/.config/nemovideo/) is not reflected in the registry's required configPaths, creating a small proportionality mismatch.
Persistence & Privilege: okalways is false and the skill does not request persistent system-wide privileges. It does not declare actions that modify other skills or global agent config.