Ai Video Editor Like Grok

Skip the learning curve of professional editing software. Describe what you want — cut the filler sections, add transitions, and generate a summary caption —...

Security Scan

The skill generally behaves like an AI video editor and asks for a single NEMO_TOKEN, but its runtime instructions ask the agent to read local skill/install files and to upload user videos to a remote API—these file-access instructions are not fully reflected in the declared config/requirements and raise privacy/scope concerns.

Purpose & Capability

Name, description, declared primaryEnv (NEMO_TOKEN), and the endpoints in SKILL.md all align with a cloud-hosted AI video editing service. Requiring a token for the backend is appropriate for the stated purpose.

Instruction Scope

The SKILL.md instructs the agent to upload user-provided videos to https://mega-api-prod.nemovideo.ai (expected for cloud editing), but also tells the agent to read this skill's YAML frontmatter and to detect install paths (~/.clawhub/, ~/.cursor/skills/) to set X-Skill-Platform. Those file-system inspection steps expand the agent's local-scope beyond the single declared config path and could cause the agent to read local files it didn't advertise needing.

Install Mechanism

No install spec and no code files — this is instruction-only. That is the lowest-risk install model and there is no archive download or external package installation.

Credentials

Only NEMO_TOKEN is required, which is proportionate to a remote video-editing service. However, the metadata mentions a config path (~/.config/nemovideo/) and the instructions suggest reading other install paths not declared as required; that mismatch between declared and requested local access is worth noting. Also, uploading arbitrary user video content to a third-party domain is a significant privacy consideration even if functionally expected.

Persistence & Privilege

always:false (no forced inclusion) and there is no install-time persistence. The skill does not request system-wide config changes or elevated privileges.

What to consider before installing

This skill appears to be a coherent cloud video-editor: it will upload user videos to mega-api-prod.nemovideo.ai and use a NEMO_TOKEN (or obtain an anonymous token) to run edits. Before installing/using it, consider: 1) Privacy: your raw videos will be sent to a third‑party service—don’t upload sensitive footage unless you trust the provider and its retention policy. 2) Tokens: prefer using a short‑lived/anonymous token for testing rather than storing a long‑lived NEMO_TOKEN in your environment. 3) Local file access: the skill’s instructions ask the agent to read this skill file’s frontmatter and probe install paths (~/.clawhub/, ~/.cursor/skills/), which weren’t listed in declared configPaths—if you want to restrict the agent’s filesystem access, block or review those reads. 4) Verification: there is no homepage or source listed; verify the legitimacy of the nemovideo.ai domain and the API before sending valuable content. If you want a stronger assurance, request the skill author to (a) list exactly which local paths the skill will read, (b) provide an official homepage or API docs, and (c) document how uploaded media and generated outputs are stored and deleted.

Getting Started

Send me your raw video footage and I'll handle the AI-powered video editing. Or just describe what you're after.

Try saying:

• "edit a 2-minute unedited screen recording into a 1080p MP4"
• "cut the filler sections, add transitions, and generate a summary caption"
• "automatically editing raw footage into a polished video using AI prompts for content creators and marketers"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

AI Video Editor Like Grok — Edit Videos With AI Prompts

Drop your raw video footage in the chat and tell me what you need. I'll handle the AI-powered video editing 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 cut the filler sections, add transitions, and generate a summary caption, 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 and yield more precise AI edits.

Matching Input to Actions

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

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

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

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 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)

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

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 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

Common Workflows

Quick edit: Upload → "cut the filler sections, add transitions, and generate a summary caption" → 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 "cut the filler sections, add transitions, and generate a summary caption" — 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 widest compatibility across platforms.