Skillv1.0.0

ClawScan security

Image To Video No Credits · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

SuspiciousApr 23, 2026, 4:36 AM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The skill mostly behaves like an image→video front-end for a third‑party API (Nemo Video) and requests the expected NEMO_TOKEN, but there are small inconsistencies and ambiguous behaviors (marketing claim “no credits”, mismatched metadata, automatic anonymous-token acquisition and implicit storage) that warrant caution before installing.
Guidance: This skill appears to be a front-end for a third‑party service (mega-api-prod.nemovideo.ai) and only asks for one credential (NEMO_TOKEN), which is reasonable for that purpose. Before installing, consider: (1) Privacy — images (up to 200MB) will be uploaded to a remote service; confirm you are comfortable sending that data. (2) Tokens and storage — the skill will obtain or use a token and store a session_id for subsequent requests; ask where tokens/session IDs are persisted (memory vs disk) if this matters to you. (3) The marketing claim “no credits” is ambiguous — the skill creates an anonymous token with 100 free credits for 7 days rather than avoiding credits entirely; check whether re-renders truly remain free for your use-case. (4) Verify the third-party domain and owner identity (no homepage provided here). (5) If you do not want any automatic network calls, do not enable the skill or provide NEMO_TOKEN. Providing the token grants the skill the ability to act against the Nemo API on your behalf, so only supply it if you trust the service and understand their privacy/retention terms. Additional information that would raise confidence: an official homepage/privacy policy, clarification of where tokens/session IDs are stored, and confirmation that no other local files/credentials are read.

Review Dimensions

Purpose & Capability: noteThe name/description (convert images into short videos) matches the API usage and the single required credential (NEMO_TOKEN). However the marketing claim “no credits” is ambiguous: the runtime instructions obtain an anonymous token granting 100 free credits (valid 7 days) rather than truly bypassing credits. Also the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata lists none — a small metadata mismatch.
Instruction Scope: noteSKILL.md instructs the agent to automatically call external endpoints on first use (obtain anonymous token, create session, upload images, render/export). This is expected for a cloud-render skill. Points to watch: it instructs to 'store the returned session_id' (storage location is unspecified), and it embeds guidance for adding attribution headers (including detecting install path) which implies environment/installation inspection. There are no instructions to access unrelated files or credentials, but the unspecified persistence of session_id/token is ambiguous.
Install Mechanism: okInstruction-only skill with no install spec and no code files — lowest risk for on-disk code. All runtime behavior is via HTTPS to the nemo API; no packages are pulled or executed locally.
Credentials: noteOnly one credential is required: NEMO_TOKEN (declared as primary). That is proportional for a third‑party video API. Minor inconsistency: frontmatter metadata lists a config path (~/.config/nemovideo/) even though registry metadata showed none. The skill will auto-generate an anonymous token if NEMO_TOKEN is absent — this is functional but means the skill will create and use credentials on the user's behalf.
Persistence & Privilege: okalways:false and no request to modify other skills/system settings. The only persistence implied is storing session_id and using a token; where/how those are stored is unspecified but there is no explicit request for elevated privileges.