Back to skill
Skillv1.0.0
ClawScan security
Video To Text Converter Online · ClawHub's context-aware review of the artifact, metadata, and declared behavior.
Scanner verdict
SuspiciousApr 11, 2026, 8:19 AM
- Verdict
- suspicious
- Confidence
- medium
- Model
- gpt-5-mini
- Summary
- The skill largely matches a cloud-based video→text service, but there are inconsistent metadata/config declarations and runtime instructions that read local paths and send files/headers to an external API — these mismatches and data-exfiltration surface should be clarified before use.
- Guidance
- This skill will upload any videos you give it to mega-api-prod.nemovideo.ai and will send an Authorization header (NEMO_TOKEN or an anonymous token it fetches) plus extra 'X-Skill-*' attribution headers. Before installing or using it: 1) Confirm you trust nemovideo.ai and its privacy/retention policies for potentially sensitive video content. 2) Note the skill can automatically acquire an anonymous token and run without your personal token — if you want explicit control, avoid letting it fetch tokens for you. 3) Ask the developer to explain the mismatch between registry metadata (no config paths) and SKILL.md frontmatter (~/.config/nemovideo/), and why the skill needs to probe install paths to set X-Skill-Platform. 4) If you handle confidential video, prefer a local transcription tool or a vendor with clear contractual protections. If you proceed, limit the videos you upload and consider rotating any long-lived NEMO_TOKEN you provide.
Review Dimensions
- Purpose & Capability
- noteThe name/description (video→text transcription) aligns with the runtime instructions that call a remote nemo-video API and upload video files. Requiring a single API token (NEMO_TOKEN) is proportionate. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata shows no required config paths — this inconsistency is unexplained.
- Instruction Scope
- concernThe instructions direct the agent to upload user video files and metadata to https://mega-api-prod.nemovideo.ai, create sessions, use SSE, poll for exports, and possibly acquire an anonymous token if NEMO_TOKEN is missing. They also instruct the agent to read skill frontmatter and probe user home paths (~/.clawhub/, ~/.cursor/skills/) to set X-Skill-Platform — reading install paths and frontmatter is out-of-band for a simple transcribe action and raises privacy/consent concerns. The skill will send user content and attribution headers to a third-party endpoint; users should expect that their videos and derived transcripts are transmitted externally.
- Install Mechanism
- okNo install spec and no code files (instruction-only). This minimizes on-disk persistence and arbitrary code execution risk.
- Credentials
- noteOnly NEMO_TOKEN is declared as required and is the primary credential — this matches the described remote API use. However, the SKILL.md also references a config path (~/.config/nemovideo/) in frontmatter but the registry lists none; plus the instructions allow obtaining an anonymous token automatically if NEMO_TOKEN is absent. The latter is convenient but means the skill can operate (and upload files) without an explicit user API key.
- Persistence & Privilege
- okalways:false and normal autonomous invocation are set. The skill does not request permanent 'always' inclusion or modifications to other skills. Autonomous network calls are expected for a cloud transcription service, but combined with the instruction-scope issues this increases exposure.