De Video Con

Turn a 2-minute interview recording into 1080p compiled video files just by typing what you need. Whether it's creating edited videos from raw footage or qui...

Security Scan

The skill's functionality (remote video composition) is coherent with its requests (a NEMO_TOKEN and file uploads), but there are small metadata inconsistencies and some instruction choices that could expose local environment details or cause automatic uploads to a third-party service—worth reviewing before installing.

Purpose & Capability

Name/description match the declared runtime behavior: remote GPU-based video rendering and export. Requesting a NEMO_TOKEN is appropriate for calling the nemo API. However, SKILL.md metadata includes a configPath (~/.config/nemovideo/) while the registry metadata earlier listed no required config paths — this discrepancy should be clarified.

Instruction Scope

Runtime instructions ask the agent to upload local files (multipart -F "files=@/path"), create sessions, and poll SSE endpoints — all expected for a remote render service. Concerns: (1) the instructions derive an 'X-Skill-Platform' header by inspecting install paths (e.g., ~/.clawhub/, ~/.cursor/skills/), which implies filesystem checks and leaks local environment details to the remote API; (2) the skill auto-generates an anonymous token and connects automatically if NEMO_TOKEN isn't set, meaning it can begin network activity without the user manually providing credentials; (3) the skill advises storing session_id but does not specify storage location or lifecycle, which could lead to orphaned jobs or tokens retained longer than expected.

Install Mechanism

Instruction-only skill with no install spec and no code files present. No packages or remote archives are downloaded by the install process (lowest install risk).

Credentials

Only one credential is declared (NEMO_TOKEN), which is proportional for a remote service. The SKILL.md also references a config path in its YAML frontmatter (~/.config/nemovideo/), which wasn't listed in the registry metadata — this mismatch should be resolved. Otherwise the skill does not request unrelated credentials.

Persistence & Privilege

always:false (not force-included) and autonomous invocation is allowed (default). Autonomous invocation combined with the ability to obtain an anonymous token means the skill could call the remote service without explicit, per-use user-supplied credentials — this is normal for many skills but worth noting as a privacy/operational tradeoff. The skill does not request system-wide configuration changes or other skills' credentials.

What to consider before installing

This skill will upload the video files you provide to a third-party API (mega-api-prod.nemovideo.ai) and can auto-generate an anonymous token if you don't set NEMO_TOKEN. Before installing: (1) confirm you are comfortable having your video content sent to that domain and review its privacy/retention practices; (2) if you prefer explicit control, provide your own NEMO_TOKEN rather than allowing anonymous token creation; (3) ask the author to explain the registry/SKILL.md mismatch about config paths and to remove or document any filesystem checks that set X-Skill-Platform headers (these can leak local environment details); (4) consider disabling autonomous invocation for this skill if you do not want it to run network operations without an explicit prompt. If any of these points are unacceptable, do not install/use the skill.

Getting Started

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

Try saying:

• "create a 2-minute interview recording into a 1080p MP4"
• "create a highlight video with music and transitions"
• "creating edited videos from raw footage for content creators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

De Video Con — Create and Export Compiled Videos

Send me your video clips and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute interview recording, type "create a highlight video with music and transitions", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter source clips process faster and give cleaner results.

Matching Input to Actions

User prompts referencing de video con, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...	Action	Skip 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 de-video-con, 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

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process 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 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)

Error Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a highlight video with music and transitions" — 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.

Common Workflows

Quick edit: Upload → "create a highlight video with music and transitions" → Download MP4. Takes 1-2 minutes 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.