Motion Video Skill Online

Get motion-enhanced videos ready to post, without touching a single slider. Upload your video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "a...

Security Scan

The skill's requests and runtime instructions are coherent with a cloud-based video rendering service: it only needs a single service token, uploads user media to that service, and contains no installer or unrelated credential requests.

Purpose & Capability

The skill's name and description promise cloud motion/video editing and the SKILL.md exclusively describes talking to a remote rendering API (upload, session, render, export). Requesting a NEMO_TOKEN bearer token is appropriate for that purpose.

Instruction Scope

Runtime instructions are focused on creating a session, streaming SSE messages, uploading user video files, polling render status, and returning download URLs. The skill documents generating an anonymous token if NEMO_TOKEN is not present and instructs not to expose tokens. It also derives attribution headers from install paths (looks at common skill install locations). This is within scope, but important: the agent will upload user media and metadata to an external API and will fetch/store short-lived anonymous tokens if none are provided.

Install Mechanism

No install spec and no code files are present (instruction-only). That minimizes filesystem/writing risk; nothing is downloaded or installed by the skill itself.

Credentials

Only a single service credential (NEMO_TOKEN) is declared as required and used as Bearer auth for API calls, which is proportionate. The SKILL.md also supports obtaining an anonymous token from the service when a token is absent. Minor metadata inconsistency: the file-level YAML lists a configPaths entry (~/.config/nemovideo/) while the registry metadata reported no required config paths—this is a small discrepancy worth noting but not necessarily malicious.

Persistence & Privilege

always:false and default autonomous invocation are set (normal). The skill does not request permanent system-wide privileges or to modify other skills. It stores session tokens only for the session lifetime per the instructions.

Assessment

This skill appears to do what it claims: it uploads your video files to a remote service (mega-api-prod.nemovideo.ai) for cloud rendering and returns a download link. Before installing or using it: (1) Be aware that any media you send will be transmitted to and stored/processed by that external service—do not upload sensitive or private footage unless you trust the provider and have read their privacy/terms. (2) The skill can obtain a short-lived anonymous token (100 free credits, 7-day expiry) if you don't supply NEMO_TOKEN; supplying your own token grants access tied to your account. (3) There is a small metadata mismatch about a config path in the file header—this is likely benign but worth double-checking. (4) Verify the service domain and organization if you require stronger assurance (company homepage is missing). If you are comfortable with those privacy and trust considerations, the skill is internally consistent with its stated purpose.

Getting Started

Ready when you are. Drop your video clips here or describe what you want to make.

Try saying:

• "create a 60-second screen recording with static transitions into a 1080p MP4"
• "add smooth motion effects and animate the text overlays"
• "adding motion effects and animations to video clips for content creators"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Motion Video Skill Online — Add Motion Effects to Videos

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

A quick example: upload a 60-second screen recording with static transitions, type "add smooth motion effects and animate the text overlays", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter clips under 30 seconds render motion effects significantly faster.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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 motion-video-skill-online, 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).

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

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "add smooth motion effects and animate the text overlays" — 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 widest platform compatibility.

Common Workflows

Quick edit: Upload → "add smooth motion effects and animate the text overlays" → 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.