Ai Video Editor Motion Graphics

Turn a 60-second product demo clip into 1080p motion graphics videos just by typing what you need. Whether it's adding animated graphics and titles to video...

Security Scan

The skill's requirements and runtime instructions are coherent with an online video-rendering service, but the skill comes from an unknown source and there are a few small scope/metadata inconsistencies you should be aware of before installing.

Purpose & Capability

The skill claims to call a remote video-rendering API and only requests a single credential (NEMO_TOKEN) and a config path for nemovideo; this is proportionate for a cloud video service. Minor inconsistency: the runtime text also describes detecting the agent install path (~/.clawhub, ~/.cursor/skills) for attribution headers, but those paths are not declared in the metadata configPaths — reading install locations is a small extra permission that isn't fully declared.

Instruction Scope

SKILL.md contains concrete API workflows (auth, session creation, SSE messaging, uploads, polling render status) that stay within the stated purpose. It instructs generating an anonymous token if NEMO_TOKEN is absent and uploading user-provided video files. It does not direct the agent to read unrelated system files or other credentials, though it does instruct inspecting install path for platform attribution.

Install Mechanism

This is an instruction-only skill with no install spec or code to download or write to disk, which is the lowest-risk install model.

Credentials

Only a single API credential (NEMO_TOKEN) is required as the primary credential, which matches the described API usage. Users should confirm the origin and scope of any NEMO_TOKEN they already have (don’t reuse broader or unrelated tokens).

Persistence & Privilege

The skill does not request always:true and uses normal autonomous invocation settings. It does not request system-wide configuration changes or other skills' secrets.

Assessment

This skill looks like a straightforward client for a cloud video-rendering API, but the publisher and homepage are unknown — exercise caution. Before installing: (1) Verify the NEMO_TOKEN provenance — do not supply high-privilege or unrelated tokens; prefer generating an anonymous token per the skill if you don't already have a dedicated token. (2) Understand that your video files are uploaded to mega-api-prod.nemovideo.ai and will be processed remotely — do not upload sensitive content without confirming the service's privacy policy. (3) Note the skill may read your agent install path to set an attribution header; if you are uncomfortable with that, ask the publisher for clarification. (4) If possible, test with temporary/limited-scope credentials and non-sensitive sample videos and confirm behavior before using production assets. If you want greater assurance, request the skill's source or an official homepage from the publisher.

Getting Started

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

Try saying:

• "add a 60-second product demo clip into a 1080p MP4"
• "add animated text overlays and transitions between scenes"
• "adding animated graphics and titles to video clips for marketers"

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

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

A quick example: upload a 60-second product demo clip, type "add animated text overlays and transitions between scenes", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 30 seconds render motion graphics faster and more accurately.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: ai-video-editor-motion-graphics
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

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.

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.

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You 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

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 "add animated text overlays and transitions between scenes" — 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 quality and file size.

Common Workflows

Quick edit: Upload → "add animated text overlays and transitions between scenes" → 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.