Back to skill
Skillv1.0.0
ClawScan security
Video Maker Free Download App · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
SuspiciousApr 19, 2026, 9:36 PM
- Verdict
- suspicious
- Confidence
- medium
- Model
- gpt-5-mini
- Summary
- The skill mostly behaves like a cloud video-upload-and-render helper (which matches its description) but has internal inconsistencies and some vague instructions about where and how it gets credentials and install-path metadata that warrant caution before installing.
- Guidance
- What to consider before installing: - The skill concept is coherent: it uploads media to a cloud renderer and returns a download link. Asking for a service token (NEMO_TOKEN) is expected. - Inconsistencies to watch: the registry metadata asserts no config paths and a required env var, but the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) and the text makes NEMO_TOKEN optional (the skill will obtain an anonymous token if none is present). Ask the publisher to clarify whether NEMO_TOKEN is truly required and why a config path is listed. - Privacy/security: using the skill will upload whatever files you give it to https://mega-api-prod.nemovideo.ai. Don’t send sensitive or private videos unless you trust that domain/operator and you’ve reviewed their privacy/retention policy. - Attribution headers: the skill requires special headers (including an X-Skill-Platform value derived from an install path). That could cause the agent to inspect its environment or reveal installation context — ask the author to confirm exactly how X-Skill-Platform is derived and whether it will read local paths. - If you want to test safely: try with non-sensitive, low-value media and monitor network requests; prefer providing your own NEMO_TOKEN (if you can get one) rather than letting the skill obtain anonymous tokens automatically. - Additional useful info to request from the publisher: an official homepage or privacy policy, who operates mega-api-prod.nemovideo.ai, token scope and lifetime docs, and confirmation of whether the listed config path is actually used. Without that, proceed with caution.
Review Dimensions
- Purpose & Capability
- noteThe skill's stated purpose (cloud video creation and export) matches the actions described (upload media, create a session, render, return download URL). Requesting a service token (NEMO_TOKEN) is reasonable. However, the registry metadata claims no required config paths while the SKILL.md frontmatter lists a config path (~/.config/nemovideo/)—this mismatch is unexplained and unexpected.
- Instruction Scope
- concernSKILL.md instructs the agent to: use NEMO_TOKEN if present, otherwise obtain an anonymous token by POSTing to https://mega-api-prod.nemovideo.ai, create sessions, upload user files, and perform SSE interactions. Those network calls are coherent with the skill's purpose, but the instructions also say to 'auto-detect' an install path for X-Skill-Platform attribution (which implies the agent may inspect its environment/install path) and to keep technical details out of the chat (reduces transparency). The skill will upload user media to an external domain and require attribution headers; these behaviors are within scope but the install-path auto-detection and undisclosed configPath are vague and grant extra agent discretion.
- Install Mechanism
- okThis is an instruction-only skill with no install spec and no code files, so nothing is written to disk at install time. That is the lowest-risk install mechanism.
- Credentials
- concernThe skill declares a single primary credential (NEMO_TOKEN), which is proportionate. But the registry metadata marks NEMO_TOKEN as required while SKILL.md treats it as optional (it will request an anonymous token if missing). Also SKILL.md references a config path (~/.config/nemovideo/) that the registry metadata did not list. These inconsistencies (required vs optional credential, undeclared config path) are unexpected and reduce trust.
- Persistence & Privilege
- okalways:false and no install-time persistence are set. The skill does not request special system privileges or modify other skills' configurations in its instructions.