Skill flagged — suspicious patterns detected

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

Video To

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — convert this video to a vertical format with captions for Instagram Reels...

0· 57·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/video-to.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Video To" (dsewell-583h0/video-to) from ClawHub.
Skill page: https://clawhub.ai/dsewell-583h0/video-to
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 video-to

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-to
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The requested credential (NEMO_TOKEN) and the described API calls align with a cloud video-conversion service. However, the registry metadata (top-level) reported no required config paths, while the SKILL.md frontmatter includes a config path (~/.config/nemovideo/). This discrepancy is unexplained and reduces confidence in metadata accuracy.
!
Instruction Scope
Runtime instructions explicitly tell the agent to upload user files, call external endpoints, create an anonymous token via a POST, and save session_id. They also instruct deriving headers from local install paths (checking ~/.clawhub/ and ~/.cursor/skills/), which requires reading the user's filesystem. Uploading user videos to an external service is expected for this skill but is privacy-sensitive; the SKILL.md does not state retention, encryption, or deletion policies for uploaded content.
Install Mechanism
This is an instruction-only skill with no install spec and no bundled code — it does not write new binaries or download archives. That keeps the install risk low.
Credentials
Only one credential is requested: NEMO_TOKEN (declared as primary). That is proportional for a third-party API. Still, the skill suggests generating an anonymous token and making it the NEMO_TOKEN, and the SKILL.md references a config path for nemovideo; it's unclear whether the token/session will be persisted to disk or kept in memory. Absence of other unrelated secrets is good.
Persistence & Privilege
The skill is not always-enabled and does not request broad system privileges. It does instruct the agent to save session_id and to use or set NEMO_TOKEN; where and how those are stored is unspecified. The SKILL.md also indicates inspecting install paths to set a header, which implies reading some user filesystem locations.
What to consider before installing
What to consider before installing/using this skill: - Understand data flow: this skill uploads your video files to mega-api-prod.nemovideo.ai for processing. Do not upload sensitive or confidential videos unless you trust the service's policies. - Token handling: the skill needs a NEMO_TOKEN. Prefer using a throwaway/anonymous token (it documents an anonymous-token endpoint) rather than a long-lived personal account token. Confirm whether the skill writes tokens or session IDs to disk (the SKILL.md mentions a config path) and where. - Metadata inconsistency: ask the publisher to clarify the config path usage (~/.config/nemovideo/ appears only in SKILL.md) and provide a homepage/privacy policy and data-retention info. - Filesystem reads: the skill will attempt to detect install paths to set headers; verify you are comfortable with that filesystem access. - If you must proceed: run with a temporary/limited token, avoid uploading private content, and request explicit answers from the author about token/session persistence, logs, retention, and encryption.

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

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk976erzxbqfh167ce0b62rcfyx851vc4
57downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Getting Started

Send me your video files and I'll handle the AI video conversion. Or just describe what you're after.

Try saying:

  • "convert a 2-minute MP4 tutorial recording into a 1080p MP4"
  • "convert this video to a vertical format with captions for Instagram Reels"
  • "converting videos to different formats or aspect ratios for social platforms for content creators"

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.

Video To — Convert and Export Video Files

This tool takes your video files and runs AI video conversion through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-minute MP4 tutorial recording and want to convert this video to a vertical format with captions for Instagram Reels — the backend processes it in about 30-90 seconds and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster and use fewer credits.

Matching Input to Actions

User prompts referencing video to, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-to, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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.

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

  • "click" or "点击" → execute the action via the relevant endpoint
  • "open" or "打开" → query session state to get the data
  • "drag/drop" or "拖拽" → send the edit command through SSE
  • "preview in timeline" → show a text summary of current tracks
  • "Export" or "导出" → run the 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 → "convert this video to a vertical format with captions for Instagram Reels" → Download MP4. Takes 30-90 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 "convert this video to a vertical format with captions for Instagram Reels" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the widest compatibility across platforms.

Comments

Loading comments...