Ai Video Helper

Skip the learning curve of professional editing software. Describe what you want — trim the silent parts, add captions, and export as MP4 — and get polished...

Security Scan

The skill appears to do what it says (cloud video editing) and only asks for a single service token, but there are small metadata/instruction inconsistencies you should be aware of before using it.

Purpose & Capability

Name/description, required NEMO_TOKEN, and the SKILL.md runtime instructions all consistently describe a cloud video-editing workflow that uploads user video, creates a session, streams edits, and returns a download URL — the requested token is appropriate for that purpose.

Instruction Scope

The instructions stay within the video-editing domain (session creation, SSE chat, uploads, exports). They explicitly tell the agent to POST to mega-api-prod.nemovideo.ai and to avoid printing tokens. One minor scope creep: the SKILL.md asks the agent to derive an install-path-based X-Skill-Platform header (inspecting known install paths) and the YAML frontmatter includes a config path (~/.config/nemovideo/) — these require checking the agent filesystem, which is reasonable for attribution but should be noted.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing will be written to disk by an installer. This is the lowest-risk install mechanism.

Credentials

Only one credential (NEMO_TOKEN) is required which matches the described cloud API usage. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) that is not listed in the registry metadata; that discrepancy suggests either sloppy metadata or an expectation to read that config folder, so be cautious about filesystem access.

Persistence & Privilege

The skill is not force-enabled (always:false) and does not request permanent elevated privileges. It instructs the agent to create and save session_id for ongoing jobs, which is normal for a session-based cloud service.

Assessment

This skill uploads your videos to an external service (mega-api-prod.nemovideo.ai) and uses a NEMO_TOKEN to authorize requests. Before installing, confirm you trust that service and its privacy policy because files and derived data will leave your device. The skill can generate an anonymous token for short-lived use — prefer anonymous/ephemeral tokens instead of long-lived account tokens if you want to limit risk. Note a small inconsistency: the skill's internal frontmatter references a config path (~/.config/nemovideo/) and asks the agent to detect install-paths for attribution headers; this may require the agent to check certain filesystem locations. If you are uncomfortable with the agent inspecting those paths or uploading sensitive footage, do not install/use the skill. If possible, test with non-sensitive videos and use anonymous tokens first.

Getting Started

Share your raw video footage and I'll get started on AI video assistance. Or just tell me what you're thinking.

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "trim the silent parts, add captions,"

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.

AI Video Helper — Edit and Export Videos Fast

Drop your raw video footage in the chat and tell me what you need. I'll handle the AI video assistance on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute unedited screen recording, ask for trim the silent parts, add captions, and export as MP4, and about 1-2 minutes 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 60 seconds process significantly faster.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

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

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

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)

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

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.

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

Common Workflows

Quick edit: Upload → "trim the silent parts, add captions, and export as MP4" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the silent parts, add captions, and export as MP4" — 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.