Back to skill
Skillv1.0.0
ClawScan security
Ai To Generator · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
SuspiciousApr 21, 2026, 3:56 AM
- Verdict
- suspicious
- Confidence
- medium
- Model
- gpt-5-mini
- Summary
- The skill largely matches its stated purpose (generating videos via a remote API) but contains small metadata inconsistencies and asks the agent to read local install paths for attribution; these mismatches and filesystem access should be clarified before installing.
- Guidance
- This skill appears to do what it says (call a remote API to generate videos) and has no install footprint, which is lower risk. Before installing: 1) Confirm the NEMO_TOKEN you provide is only for this service — do not reuse any sensitive or multi-service tokens. 2) Ask the publisher to clarify the configPaths discrepancy (SKILL.md mentions ~/.config/nemovideo/ but registry metadata lists none). 3) Be aware the skill will read local install paths to set attribution headers; if you are uncomfortable with that filesystem probing, request a version that omits that behavior. 4) Verify the API domain (mega-api-prod.nemovideo.ai) is legitimate for the service you're expecting and consider using a separate/test account or ephemeral token when trying it out.
Review Dimensions
- Purpose & Capability
- noteName/description (AI → video) align with the runtime instructions and the API endpoints (render, upload, SSE). The single declared secret NEMO_TOKEN is appropriate for a hosted-video API. However, SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata supplied to you lists no required config paths — this inconsistency should be resolved.
- Instruction Scope
- noteInstructions stay within the video-generation workflow (token acquisition, session creation, SSE message streaming, upload, render/export). They also instruct the agent to read its install path to set attribution headers (detecting ~/.clawhub/ or ~/.cursor/skills/). Reading the agent's install path is extra filesystem access beyond pure API calls — reasonable for attribution but worth noting because the skill will probe local paths.
- Install Mechanism
- okNo install spec and no code files — instruction-only skill. This minimizes disk writes and executable installs and is proportionate for a remote-API integration.
- Credentials
- noteOnly NEMO_TOKEN is required (primary credential), which is consistent with the described API usage. The SKILL.md also documents an anonymous-token flow (POST to /api/auth/anonymous-token) which is reasonable. The earlier-mentioned mismatch about configPaths (present in SKILL.md metadata but not in the registry metadata) is a proportionality/information inconsistency that should be clarified. Ensure NEMO_TOKEN is specific to this service (not a general-purpose secret).
- Persistence & Privilege
- okalways:false and normal autonomous invocation. The skill asks to save a session_id locally for ongoing operations (expected for session-based APIs). It does not request permanent system-wide privileges or to modify other skills.