De Video

v1.0.0

Get processed video files ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, WebM, up to 500MB), say something li...

0· 64·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 vynbosserman65/de-video.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "De Video" (vynbosserman65/de-video) from ClawHub.
Skill page: https://clawhub.ai/vynbosserman65/de-video
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 de-video

ClawHub CLI

Package manager switcher

npx clawhub@latest install de-video
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The name/description match the actions in SKILL.md: uploading video, creating sessions, submitting render jobs, and downloading results. Requesting a NEMO_TOKEN (or creating an anonymous token) is appropriate for a cloud-rendering API.
Instruction Scope
Instructions tell the agent to call specific nemovideo endpoints, upload files, poll render status, and manage a session token — all expected. The SKILL.md also describes deriving attribution headers and detecting an install path (e.g., ~/.clawhub/) which requires checking the filesystem; this is not obviously harmful but is broader than strictly necessary for basic API calls. Also the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier indicated no required config paths — this mismatch should be clarified.
Install Mechanism
There is no install spec and no code files; the skill is instruction-only, so it does not pull binaries or write files during installation. This is the lowest-risk install model.
Credentials
Only one credential (NEMO_TOKEN) is declared as required and used by the instructions. The anonymous-token flow is described as a fallback. No unrelated secrets or multiple service credentials are requested.
Persistence & Privilege
The skill is not always-enabled and can be invoked by the user. It stores session_id and tokens for the session-level workflow, which is appropriate for its purpose. There is no instruction to modify other skills or system-wide agent settings.
Assessment
This skill appears to do what it says: it uploads video to a remote renderer and returns processed files, and it needs a NEMO_TOKEN (or will request an anonymous one). Before installing: (1) confirm you trust the domain https://mega-api-prod.nemovideo.ai and the service's privacy policy because uploaded videos are sent off-host; (2) verify what NEMO_TOKEN will grant (access scope, revocation policy) and avoid using high-privilege or unrelated credentials; (3) clarify the metadata mismatch about a config path (~/.config/nemovideo/) and the skill's stated lack of required config paths — ask the publisher whether the skill will read local config directories; (4) avoid uploading sensitive footage to an untrusted or unknown service; and (5) if you rely on anonymous tokens, be aware they expire (per the SKILL.md) and may be rate-limited.

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

Runtime requirements

✂️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk9778de437kxbzzgqq6c1e9b418501jg
64downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Getting Started

Got raw video footage to work with? Send it over and tell me what you need — I'll take care of the AI video removal.

Try saying:

  • "remove a 2-minute interview recording with unwanted segments into a 1080p MP4"
  • "remove the background, cut out silences, and strip the video layer leaving only audio"
  • "removing unwanted elements or segments from videos 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.

De Video — Remove and Process Video Content

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

Say you have a 2-minute interview recording with unwanted segments and want to remove the background, cut out silences, and strip the video layer leaving only audio — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is de-video, 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).

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.

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

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

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

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

Common Workflows

Quick edit: Upload → "remove the background, cut out silences, and strip the video layer leaving only audio" → 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 "remove the background, cut out silences, and strip the video layer leaving only audio" — 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.

Comments

Loading comments...