Skillv1.0.0

ClawScan security

Online Subtitle · ClawHub's context-aware review of the artifact, metadata, and declared behavior.

Scanner verdict

SuspiciousApr 28, 2026, 5:33 PM

Verdict: suspicious
Confidence: medium
Model: gpt-5-mini
Summary: The skill's runtime instructions largely match a cloud subtitle service, but mismatches between the registry metadata and the SKILL.md (required config paths vs none, required env var vs SKILL.md auto-obtaining a token), lack of a public source/homepage, and runtime calls to an unverified backend make the package incoherent enough to warrant caution.
Guidance: This skill mostly behaves like a thin client for an external subtitle-rendering API, but there are metadata mismatches and no public source/homepage to verify the backend. Before installing or enabling it: 1) Ask the publisher for a public repo or homepage and a privacy/security statement about how they store tokens and uploaded video. 2) Clarify whether NEMO_TOKEN is required or optional (SKILL.md says it can obtain an anonymous token). 3) Confirm whether the skill will read or write ~/.config/nemovideo/ and whether tokens are persisted to disk. 4) Limit exposure: do not feed it high-sensitivity videos or system-level secrets (don’t reuse system API keys). 5) If you decide to try it, run it in an isolated environment (sandbox/container) and monitor network requests to the listed domain (mega-api-prod.nemovideo.ai). If the publisher can't provide verifiable details about the service and token handling, avoid granting broad credentials or using it for sensitive content.

Review Dimensions

Purpose & Capability: concernThe declared purpose (add subtitles via a cloud backend) aligns with the API calls and token usage in SKILL.md. However, the registry metadata says no config paths while the SKILL.md frontmatter declares a config path (~/.config/nemovideo/). Also the registry marks NEMO_TOKEN as required, but SKILL.md describes an anonymous-token flow to obtain NEMO_TOKEN if it's not present. Those inconsistencies suggest sloppy packaging or mismatched declarations.
Instruction Scope: noteSKILL.md instructs the agent to create sessions, upload video files, poll SSE endpoints, and POST to specific API endpoints on mega-api-prod.nemovideo.ai — all coherent with the stated feature set. It also requires adding attribution headers and asks the agent to auto-acquire an anonymous token if NEMO_TOKEN is missing. The instructions are fairly specific but include vague items (auto-detecting 'install path' to set X-Skill-Platform) and rely on an external domain with no published homepage or source for verification.
Install Mechanism: okThis is an instruction-only skill with no install spec and no code files, so it does not write code to disk or fetch archives at install time. That minimizes install-time risk.
Credentials: noteOnly NEMO_TOKEN is declared as a required credential, which is appropriate for a cloud API-backed subtitle service. But SKILL.md will generate an anonymous token itself if NEMO_TOKEN is missing, so marking the env var as strictly required in registry metadata is inconsistent. The frontmatter's implied config path (~/.config/nemovideo/) could imply reading or writing local configuration, but the registry metadata did not declare that; this discrepancy is concerning and should be clarified.
Persistence & Privilege: okThe skill does not request always:true and does not include an install script. It keeps session_id in-memory per-session per instructions; there is no explicit instruction to persist tokens or modify other skills or system settings. The only minor concern is the frontmatter-configPath mention (which could permit reading ~/.config/nemovideo/) — that capability is not declared elsewhere, creating ambiguity.