Skillv1.0.0

ClawScan security

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

Scanner verdict

SuspiciousApr 29, 2026, 4:32 PM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The skill's behavior mostly fits a cloud video-editing tool, but there are mismatches (filesystem attribution checks and a declared config path in the frontmatter) that are unexplained and worth clarifying before installing.
Guidance: This skill appears to be a wrapper for a third-party cloud video editing API and needs an API token (NEMO_TOKEN) to upload your raw footage and get edited videos back. Before installing: (1) confirm the domain https://mega-api-prod.nemovideo.ai is one you trust and review that service's privacy/billing rules — uploaded videos will go to that cloud. (2) Ask the author to explain why the skill needs to 'detect install path' and to read the skill's frontmatter — this implies probing local filesystem paths (e.g., ~/.clawhub/ or ~/.cursor/) that weren't declared in the registry. (3) Verify the frontmatter's config path (~/.config/nemovideo/) — clarify if the skill will read files from that directory and why. (4) Use a temporary or limited-scope token if possible, and avoid uploading sensitive footage until you confirm retention and access policies. If the author cannot justify the filesystem attribution checks or the config-path usage, treat the skill as higher risk and do not install it.

Review Dimensions

Purpose & Capability: noteThe declared purpose (cloud video editing for Chinese creators) matches the API endpoints and workflows in SKILL.md and the single required credential NEMO_TOKEN is appropriate. However, the skill asks the agent to detect the install path (to set X-Skill-Platform) and to read YAML frontmatter for version/metadata — actions that require filesystem access unrelated to the core editing job and are not justified by the description.
Instruction Scope: concernInstructions direct the agent to call third-party endpoints at mega-api-prod.nemovideo.ai, obtain or use NEMO_TOKEN, create sessions, upload user media, and poll render status — all consistent with a cloud editor. Concerning parts: (1) it instructs reading this file's YAML frontmatter and detecting install path on disk to populate attribution headers (implies reading local paths like ~/.clawhub/ or ~/.cursor/skills/), but the skill registry metadata does not declare those filesystem paths or permissions; (2) it tells the agent to save session_id and to persist the token, but does not specify where to store them or how long; (3) the attribution headers requirement (X-Skill-Platform) may force filesystem probes that are outside the stated editing function.
Install Mechanism: okInstruction-only skill with no install spec or code files. This is the lowest-risk install model; nothing is written to disk by an installer. Network calls occur at runtime per SKILL.md, which is expected for a cloud service integration.
Credentials: noteOnly NEMO_TOKEN is required (declared as primaryEnv), which is proportionate for a cloud API. However, the embedded frontmatter metadata also lists a config path (~/.config/nemovideo/) while the registry metadata shows no required config paths — an inconsistency. The SKILL.md's instructions do not request any other env vars, but they do instruct generation of an anonymous token via an API call if NEMO_TOKEN is absent (acceptable but note that the token grants render/ upload privileges).
Persistence & Privilege: okThe skill is not force-included (always: false) and uses normal autonomous invocation semantics. It asks to persist a session_id and store a token (typical for session management) but does not request system-wide privileges or to modify other skills. No 'always' privilege or unexpected persistence mechanism is present.