Skillv1.0.0

ClawScan security

Video Generation Chinese · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

BenignApr 29, 2026, 5:03 PM

Verdict: benign
Confidence: medium
Model: gpt-5-mini
Summary: The skill appears to do what it says (cloud video generation) and only requests a single service token, but there are small metadata/instruction inconsistencies and no public source or homepage — exercise caution before providing credentials or private media.
Guidance: This skill is broadly consistent with its stated purpose: it needs a NEMO_TOKEN to call a remote video-generation API and will upload media you provide. Before installing or using it: (1) verify you trust the nemovideo.ai service (no homepage or source repository is provided), (2) avoid sending sensitive private data or secrets other than the NEMO_TOKEN, (3) expect the agent to make network calls (including an anonymous-token endpoint if no token is present) and to read install path(s) or a config path for attribution headers, and (4) ask the maintainer to clarify the small metadata inconsistencies (declared configPaths vs registry metadata, session language default, and the error-code wording) if you need strict guarantees. If you have concerns about confidentiality of uploaded media, don't use this skill until you confirm the provider's privacy/security policies.

Review Dimensions

Purpose & Capability: okThe skill's name/description (generate Chinese-language videos) aligns with the runtime instructions: it calls a nemo video API, uploads media, starts render jobs, and returns download URLs. Requesting a single NEMO_TOKEN to authorize API calls is proportionate to the stated purpose.
Instruction Scope: noteSKILL.md contains concrete API endpoints and a session-based workflow that stay within the video-generation scope. Minor issues: SKILL.md instructs deriving X-Skill-Platform from install paths (which implies checking local paths like ~/.clawhub/ or ~/.cursor/skills/), and it defaults the session language to "en" in the example despite being a Chinese-video skill. Also the document's error-code mapping is slightly inconsistent (402 is described both as 'subscription tier issue' and as the failure code when attribution headers are missing). These are implementation details rather than direct scope creep, but they are worth noting.
Install Mechanism: okThis is an instruction-only skill with no install spec and no code files, so nothing is written to disk by the skill itself. That is the lowest-risk installation model.
Credentials: noteThe skill declares a single required environment variable (NEMO_TOKEN) which matches the API-auth pattern in SKILL.md. However, there's a small metadata mismatch: the registry metadata lists no required config paths, whereas the SKILL.md frontmatter claims a config path (~/.config/nemovideo/). The SKILL.md also asks the agent to detect install paths to set X-Skill-Platform, which implies reading local path information. These filesystem checks and the config path declaration are not unusual for attribution/telemetry, but they are additional local-scope accesses the user should be aware of.
Persistence & Privilege: okThe skill is not always-included and allows user invocation; it does not request elevated platform-wide privileges or persistent installation. It uses session tokens for renders and does not request permanent host access.