Video Motion

Skip the learning curve of professional editing software. Describe what you want — add smooth motion blur and dynamic camera movement to my static footage —...

Security Scan

The skill's instructions match a cloud video-processing tool and mostly align with its description, but there are inconsistencies around required credentials and config paths that you should clear up before installing.

Purpose & Capability

The skill's declared purpose (AI motion enhancement of uploaded videos) matches the runtime instructions (upload endpoints, render/export workflow). However the SKILL.md frontmatter references a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths, and the registry lists NEMO_TOKEN as required even though the instructions include an anonymous-token fallback. These mismatches reduce confidence that metadata accurately reflects runtime needs.

Instruction Scope

The SKILL.md instructs only actions related to the video-processing service: creating/using a session, uploading files, SSE chat, polling export status, and returning download URLs. It does not instruct reading unrelated system files or secrets. It does require including specific attribution headers on every request and instructs not to print tokens or raw JSON.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing will be written to disk by an installer. That minimizes supply-chain/install risk.

Credentials

The registry declares a single credential (NEMO_TOKEN) which is appropriate for an external API. But SKILL.md provides a complete anonymous-token acquisition flow, implying NEMO_TOKEN is optional. Also the frontmatter's config path (~/.config/nemovideo/) suggests the skill may read or write a local config directory despite the registry saying no config paths are required. These inconsistencies mean the declared environment/credential requirements are not fully trustworthy without clarification.

Persistence & Privilege

The skill does ask to 'save session_id' for job tracking and carries session tokens in requests, which is normal for a cloud-render tool. It does not request 'always: true' or other elevated privileges. The mention of a config path suggests the skill might persist credentials or session info to ~/.config/nemovideo/ — confirm whether it will create/read files and whether that's limited to its own directory.

What to consider before installing

What to consider before installing: - This skill will upload user video files to an external service at mega-api-prod.nemovideo.ai and use an API token (NEMO_TOKEN) or an anonymous token it can obtain for you — only install if you trust that service with the videos you plan to upload. - Metadata mismatches: the registry marks NEMO_TOKEN as required but SKILL.md describes an anonymous-token fallback, and the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry said none. Ask the publisher to clarify whether NEMO_TOKEN is mandatory and whether the skill will read/write ~/.config/nemovideo/. - Privacy: confirm retention/processing policies on the service (where files are stored, how long, whether outputs are shared). Avoid uploading sensitive or private footage until you have those answers. - Operational: the skill requires adding specific headers and will store session_id and use bearer tokens for requests; ensure the agent implementation will not log or expose raw tokens. - If you still want to proceed, prefer using an isolated, revokable token (or the anonymous flow) and test with non-sensitive sample clips first. If the publisher cannot clarify the config-path and credential behavior, treat the metadata mismatch as a red flag and refrain from installing.

Getting Started

Share your video clips and I'll get started on AI motion enhancement. Or just tell me what you're thinking.

Try saying:

• "add my video clips"
• "export 1080p MP4"
• "add smooth motion blur and dynamic"

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 Motion — Add Motion Effects to Videos

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

Say you have a 30-second product demo clip and want to add smooth motion blur and dynamic camera movement to my static footage — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster and give more consistent motion results.

Matching Input to Actions

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

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

Header	Value
X-Skill-Source	video-motion
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-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.

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)

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

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.

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 "add smooth motion blur and dynamic camera movement to my static footage" — 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 best balance of motion quality and file size.

Common Workflows

Quick edit: Upload → "add smooth motion blur and dynamic camera movement to my static footage" → 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.