Skillv1.0.0

ClawScan security

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

Scanner verdict

BenignApr 16, 2026, 5:08 PM

Verdict: Benign
Confidence: high
Model: gpt-5-mini
Summary: The skill's requests and runtime instructions are coherent with a cloud AI video rendering service: it only needs a NEMO_TOKEN (or obtains an anonymous token), talks to the nemovideo.ai API, and has no install or unrelated credential demands.
Guidance: This skill appears to do what it claims: it will upload your media and interact with mega-api-prod.nemovideo.ai to generate videos. Before installing/using it: (1) Do not upload sensitive videos you wouldn't want sent to an external service; uploads go to the listed domain. (2) Treat NEMO_TOKEN as a service credential — only provide a token you trust, or use anonymous mode if you prefer a short-lived credential. (3) The skill will read its own SKILL.md frontmatter and may inspect its install path for attribution headers; it does not request other local secrets. (4) If you need stronger guarantees, verify the service's privacy policy and trustworthiness of the nemovideo.ai domain, or use an official/trusted provider. If you want, I can highlight exact lines in the SKILL.md that implement any of the behaviors above.

Review Dimensions

Purpose & Capability: okName/description match the declared behavior: creating short edited videos via a remote API. The single required env var (NEMO_TOKEN) and the declared config path (~/.config/nemovideo/) are directly related to authenticating and storing session state for the described backend (mega-api-prod.nemovideo.ai). There are no unrelated credentials or binaries requested.
Instruction Scope: noteThe SKILL.md gives detailed, actionable instructions for acquiring an anonymous token, creating sessions, uploading media, consuming SSE streams, and starting renders — all consistent with the stated purpose. It does request reading the skill's own YAML frontmatter at runtime and detecting install path to populate attribution headers, which requires local file/path access; this is reasonable for attribution but worth noting (the skill does not instruct reading other unrelated local files or additional env vars).
Install Mechanism: okNo install spec and no code files are present (instruction-only), so nothing is written to disk by an installer. This is the lowest-risk install posture.
Credentials: okOnly NEMO_TOKEN is declared as required (and declared as primaryEnv). The skill can fall back to obtaining an anonymous token from the service if no token is provided — behavior consistent with a public/consumer API. No extraneous or unrelated secrets (AWS, GitHub, etc.) are requested.
Persistence & Privilege: okThe skill is not marked always:true and has no install-time persistence. It can be invoked autonomously by the agent (default platform behavior), which is expected for skills that perform network operations; this is not by itself a concern.