Skillv1.0.0

ClawScan security

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

Scanner verdict

BenignApr 16, 2026, 5:49 PM

Verdict: Benign
Confidence: high
Model: gpt-5-mini
Summary: The skill's requested access and runtime instructions are consistent with a text-to-video cloud service: it needs a single service token, calls a remote API to upload/render videos, and has no installer or unrelated credential requests.
Guidance: This skill appears to do what it says: it will call nemo's cloud API, upload files you give it, and return rendered videos. Before installing, consider: (1) Privacy — uploads and prompt text are sent to an external service (https://mega-api-prod.nemovideo.ai). Do not upload sensitive data you wouldn't want shared. (2) Anonymous token behavior — if you don't set NEMO_TOKEN the skill will request an anonymous token from the service automatically (100 free credits, 7-day expiry). (3) Verify the service/owner — source is unknown; if you need stronger assurance, ask the publisher for a homepage, privacy policy, or use your own service token. (4) Clarify the config-path discrepancy in the SKILL.md frontmatter (~/.config/nemovideo/) if you are concerned about local config access. Other than those privacy/operational cautions, the skill's requirements and instructions are proportionate to its stated purpose.

Review Dimensions

Purpose & Capability: noteThe name/description (text→video) match the instructions (create session, upload media, render/export). One minor inconsistency: the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this is likely benign but worth clarifying.
Instruction Scope: okRuntime instructions are limited to contacting the listed nemo API, creating sessions, streaming SSE, uploading user-supplied files, polling render status, and returning download URLs. The skill does not instruct arbitrary filesystem reads or accessing unrelated system secrets. It does instruct multipart uploads from local file paths (user-provided files) which is expected for an upload feature.
Install Mechanism: okNo install spec or code is present (instruction-only). Nothing is written to disk or downloaded during install, which minimizes supply-chain risk.
Credentials: noteOnly a single credential (NEMO_TOKEN) is required — appropriate for calling the described cloud service. The SKILL.md also documents a self-bootstrap flow that will request an anonymous token from the external API if NEMO_TOKEN is absent; this is coherent with the skill's behavior but means the skill will contact the external domain even without a preconfigured token. The presence of a declared config path in the frontmatter (see purpose_capability) could imply optional config use; instructions do not require reading those files.
Persistence & Privilege: okSkill does not request always:true or any elevated/always-present privilege. It stores/uses a session token for its own operations only and makes API calls to the service; it does not modify other skills or global agent configuration.