Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Subtitle Generator Software

v1.0.0

generate video files into captioned video files with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. YouTubers and content creators use it for...

0· 83·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for dsewell-583h0/subtitle-generator-software.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Subtitle Generator Software" (dsewell-583h0/subtitle-generator-software) from ClawHub.
Skill page: https://clawhub.ai/dsewell-583h0/subtitle-generator-software
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install subtitle-generator-software

ClawHub CLI

Package manager switcher

npx clawhub@latest install subtitle-generator-software
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The name/description (subtitle generation, burn-in) aligns with the runtime instructions to call a remote rendering API and upload video files; requiring a NEMO_TOKEN credential is coherent. However, the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) that the registry metadata did not list, an inconsistency that is unexplained.
!
Instruction Scope
The instructions tell the agent to obtain/use NEMO_TOKEN, create sessions, upload user video files, and poll render status at https://mega-api-prod.nemovideo.ai. This is expected for a cloud-based subtitle service, but the skill also instructs auto-detecting the platform from the install path and references a config directory — both imply reading local filesystem state beyond the declared env var. The skill will transmit full video files (potentially sensitive) to a third-party API; the SKILL.md gives no privacy/retention guarantees.
Install Mechanism
This is an instruction-only skill with no install spec or code files, so it doesn't write or execute code locally. That is the lowest-risk install mechanism.
Credentials
Only NEMO_TOKEN is declared as required, which is proportionate for a remote API client. But the discrepancy between registry metadata (no configPaths) and SKILL.md frontmatter (lists ~/.config/nemovideo/) is a red flag: it suggests the skill expects to read additional local configuration that was not declared.
Persistence & Privilege
The skill does not request always: true and does not declare system-wide modifications. It needs the agent to access user-supplied files and an API token (normal for this kind of service). Autonomous invocation is allowed by default but not, by itself, a new risk here.
What to consider before installing
This skill will upload your video files to a third‑party service (mega-api-prod.nemovideo.ai) and requires a NEMO_TOKEN credential. That behavior is expected for cloud subtitle processing, but note: (1) the skill's source/homepage is unknown — verify the service before sending sensitive content; (2) the SKILL.md references a local config path (~/.config/nemovideo/) not declared elsewhere — ask the publisher why the skill needs to read local config; (3) prefer generating a short‑lived or anonymous token rather than storing a long‑lived secret in your environment; (4) test with non-sensitive video first, confirm retention/privacy policies, and consider revoking the token after use. If you need higher assurance, request the skill's source or official documentation and a privacy/retention statement before uploading private content.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

💬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk9719zzwsvajbvtvqrvs5a12k985967w
83downloads
0stars
1versions
Updated 6d ago
v1.0.0
MIT-0

Getting Started

Share your video files and I'll get started on subtitle generation. Or just tell me what you're thinking.

Try saying:

  • "generate my video files"
  • "export 1080p MP4"
  • "add subtitles in English and Spanish"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Subtitle Generator Software — Generate and Burn In Subtitles

Drop your video files in the chat and tell me what you need. I'll handle the subtitle generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 3-minute YouTube tutorial video, ask for add subtitles in English and Spanish with accurate timestamps, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 5 minutes produce the most accurate subtitle sync.

Matching Input to Actions

User prompts referencing subtitle generator software, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip SSE?
"export" / "导出" / "download" / "send me the video"→ §3.5 Export
"credits" / "积分" / "balance" / "余额"→ §3.3 Credits
"status" / "状态" / "show tracks"→ §3.4 State
"upload" / "上传" / user sends file→ §3.2 Upload
Everything else (generate, edit, add BGM…)→ §3.1 SSE

Cloud Render Pipeline Details

Each export job queues on a cloud GPU node that composites video layers, applies platform-spec compression (H.264, up to 1080x1920), and returns a download URL within 30-90 seconds. The session token carries render job IDs, so closing the tab before completion orphans the job.

Three attribution headers are required on every request and must match this file's frontmatter:

HeaderValue
X-Skill-Sourcesubtitle-generator-software
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

SSE Event Handling

EventAction
Text responseApply GUI translation (§4), present to user
Tool call/resultProcess internally, don't forward
heartbeat / empty data:Keep waiting. Every 2 min: "⏳ Still working..."
Stream closesProcess final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend saysYou do
"click [button]" / "点击"Execute via API
"open [panel]" / "打开"Query session state
"drag/drop" / "拖拽"Send edit via SSE
"preview in timeline"Show track summary
"Export button" / "导出"Execute export workflow

Draft JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

Timeline (3 tracks): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

Error Handling

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate limit (1 token/client/7 days)Retry in 30s once

Common Workflows

Quick edit: Upload → "add subtitles in English and Spanish with accurate timestamps" → Download MP4. Takes 30-60 seconds for a 30-second clip.

Batch style: Upload multiple files in one session. Process them one by one with different instructions. Each gets its own render.

Iterative: Start with a rough cut, preview the result, then refine. The session keeps your timeline state so you can keep tweaking.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "add subtitles in English and Spanish with accurate timestamps" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

Export as MP4 for widest compatibility across platforms and players.

Comments

Loading comments...