Skillv1.0.0

ClawScan security

Jpg To Video Maker Free · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

SuspiciousApr 13, 2026, 7:32 PM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The skill's functionality (upload images -> remote render -> return MP4) is coherent, but there are mismatches and privacy risks: it will obtain/store an anonymous token and upload your photos to an external API with no identifiable publisher or homepage, and the manifest/frontmatter disagree about local config usage.
Guidance: This skill appears to do what it says (remote rendering of photos to MP4), but it relies on an external API hosted at an unknown domain and will upload your images there. Before installing, consider: (1) Do you trust the backend operator? There is no homepage or source repository. (2) The skill can auto-generate and store an anonymous token and session ID — find out if and where those are written (frontmatter mentions ~/.config/nemovideo/). (3) Avoid uploading private or sensitive photos until you verify the service's privacy policy and storage practices. (4) If you require more assurance, ask the publisher for source code or an official homepage, or test with non-sensitive images and monitor what files are created under your home directory.

Review Dimensions

Purpose & Capability: noteThe declared purpose (convert images to MP4 via a cloud renderer) aligns with the only required credential (NEMO_TOKEN) and the API endpoints in SKILL.md. However the skill has no listed homepage or source, which reduces transparency and makes it harder to verify the backend's trustworthiness.
Instruction Scope: concernInstructions tell the agent to obtain an anonymous token automatically, create and persist a session_id, and upload user files to https://mega-api-prod.nemovideo.ai. This necessarily transmits user images and metadata to a third party (privacy risk). The runtime also instructs the agent to inspect local install paths and a config directory (~/.config/nemovideo/) to set attribution headers, which involves reading the user filesystem beyond just consuming user-supplied image files.
Install Mechanism: okInstruction-only skill with no install script or downloaded code. This minimizes on-disk persistence and arbitrary code execution risk.
Credentials: noteOnly NEMO_TOKEN is required and fits the described backend usage. However the frontmatter declares a config path (~/.config/nemovideo/) while registry metadata listed no required config paths — that's an inconsistency. The skill's instructions also imply storing tokens/session IDs (potentially to disk), so confirm what gets written and where before installing.
Persistence & Privilege: notealways:false and no explicit privileged flags. Still, the runtime asks to 'store the returned session_id for all subsequent requests' and references a config directory; that suggests the skill may persist tokens/session info locally. There is no 'always:true' or other elevated privilege requested.