Back to skill
Skillv1.0.0
ClawScan security
Best Demo Video · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
SuspiciousApr 19, 2026, 12:39 PM
- Verdict
- suspicious
- Confidence
- medium
- Model
- gpt-5-mini
- Summary
- The skill largely behaves like a cloud video-editing front end (uploads footage, creates sessions, uses a NEMO token) but there are small inconsistencies (undeclared config path, runtime instructions that imply filesystem detection) and it will upload your media and use API tokens — so review before installing.
- Guidance
- This skill calls an external API (mega-api-prod.nemovideo.ai), uploads user media, and requires a NEMO_TOKEN (you can use an anonymous token flow described in the SKILL.md). Before installing: (1) confirm the skill's publisher and source (homepage is missing); (2) decide whether you trust the nemovideo service to store/process your videos and review its privacy/retention policy; (3) if you prefer, use an anonymous/limited token (as described) rather than a long-lived credential or account token; (4) ask the author to clarify the configPaths discrepancy (~/.config/nemovideo/ appears in SKILL.md but not in registry) and whether the skill will read or write files outside its own data; (5) avoid supplying highly sensitive footage until you verify where and how exports/uploads are stored. The inconsistencies look like packaging sloppiness rather than overt malice, but treat tokens and uploaded media as sensitive.
Review Dimensions
- Purpose & Capability
- noteName/description match the runtime instructions: the SKILL.md describes uploading raw video, creating sessions, editing via SSE, and exporting via a nemovideo cloud API. Requesting a single service token (NEMO_TOKEN) is consistent with this purpose. However, the SKILL.md frontmatter lists a configPaths entry (~/.config/nemovideo/) while the registry metadata lists no required config paths — an inconsistency that should be clarified.
- Instruction Scope
- noteInstructions stay within the video-editing domain: obtain or reuse a NEMO_TOKEN, create a session, upload videos (up to 500MB), drive edits via SSE, and poll for exports. A potentially unexpected runtime step is 'detecting the install path' to set an X-Skill-Platform header (e.g., ~/.clawhub/ or ~/.cursor/skills/), which implies filesystem/environment inspection that isn't declared elsewhere. The skill also instructs deriving headers from the file's YAML frontmatter — reading the SKILL.md itself is expected, but any actions that probe other paths were not clearly authorized in the registry metadata.
- Install Mechanism
- okThis is instruction-only (no install spec, no code files). That minimizes disk-executed code risk; the skill's runtime behavior consists of outbound API calls to the nemovideo endpoints described in SKILL.md.
- Credentials
- noteOnly one credential is requested (NEMO_TOKEN), which is appropriate for a cloud API client. The SKILL.md also includes a configPaths value (~/.config/nemovideo/) in its frontmatter, but the registry lists none — this mismatch may indicate either an omitted declaration or that the skill expects to read/write a local config directory. Confirm whether the skill will access that path and why.
- Persistence & Privilege
- okalways is false and the skill is user-invocable. It asks to save a session_id and to reuse or refresh tokens (normal behavior). It does not request permanent/always-on privileges or modify other skills' configs.
