Video Editor Simple

Skip the learning curve of professional editing software. Describe what you want — trim the rough parts, add transitions, and export a clean video — and get...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-based video editing integration (it needs a NEMO_TOKEN and uses a nemo video API); nothing requested appears unrelated, but there are a few minor inconsistencies and privacy considerations you should review before uploading content.

Purpose & Capability

The name/description describe a cloud AI video editor and the SKILL.md instructs calls to a nemo video API using an Authorization bearer token (NEMO_TOKEN). Requiring NEMO_TOKEN is appropriate for this purpose. Minor inconsistency: the SKILL.md frontmatter metadata references a config path (~/.config/nemovideo/) but the registry metadata listed no required config paths.

Instruction Scope

Instructions stay within the editing/export workflow (session creation, SSE for editing, upload, export polling). Two things to note: (1) the skill instructs detecting the install path to set an X-Skill-Platform header (this requires reading/inspecting typical install directories), and (2) it instructs generating and using an anonymous token automatically if no NEMO_TOKEN is present and explicitly tells the agent not to display raw API responses or token values. Both are explainable for UX/privacy purposes but worth verifying.

Install Mechanism

Instruction-only skill with no install spec or downloads; nothing is written to disk by an installer. This is the lowest install risk.

Credentials

Only one credential is required: NEMO_TOKEN (primary). That matches the stated cloud API integration. The skill also describes obtaining an anonymous token if none is provided, which is consistent with needing a credential for API calls. No unrelated credentials or secrets are requested.

Persistence & Privilege

The skill does not request always:true and uses session IDs for job state (normal). It instructs storing the returned session_id for subsequent requests, which is appropriate. It does not instruct modifying other skills or global agent settings.

Assessment

This skill appears to be a straightforward cloud-based video editor that uses a single service token (NEMO_TOKEN). Before installing or using it: (1) confirm you trust the service domain (mega-api-prod.nemovideo.ai) — uploaded video files will be sent to that backend; (2) verify where the agent will store the session token/session_id and how long it persists; (3) if you have sensitive footage, avoid uploading it until you review the provider's privacy/storage policy; (4) note the SKILL.md will auto-generate an anonymous token if none is provided — if you prefer control, supply your own NEMO_TOKEN; (5) the skill determines an install path to set an attribution header — if your environment restricts reading your home dirs, ensure the agent's filesystem access policy is acceptable. These checks will reduce privacy and operational risk.

Getting Started

Got raw video clips to work with? Send it over and tell me what you need — I'll take care of the AI simple editing.

Try saying:

• "edit a 2-minute smartphone recording into a 1080p MP4"
• "trim the rough parts, add transitions, and export a clean video"
• "quickly trimming and cleaning up casual video recordings for casual creators and beginners"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Video Editor Simple — Edit and Export Clean Videos

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

Say you have a 2-minute smartphone recording and want to trim the rough parts, add transitions, and export a clean video — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 3 minutes process significantly faster.

Matching Input to Actions

User prompts referencing video editor simple, 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: video-editor-simple
• 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.

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.

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 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 → "trim the rough parts, add transitions, and export a clean video" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the rough parts, add transitions, and export a clean video" — 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 all platforms.