Video Ai Easy

Turn a 2-minute smartphone recording into 1080p polished edited clips just by typing what you need. Whether it's quickly editing raw videos without manual po...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud-hosted video editing service: it only asks for a single service token and instructs uploading video to that service, but users should understand it will send their media to an external API and may store session data locally.

Purpose & Capability

Name/description (AI video editing) align with the declared env var (NEMO_TOKEN) and the SKILL.md which describes uploading videos and calling a nemovideo.ai API for rendering. The config path (~/.config/nemovideo/) and session storage are plausible for caching tokens/sessions.

Instruction Scope

Instructions are limited to creating/using a NEMO_TOKEN, opening a session, uploading user video files, using SSE for edits, and polling export status. This stays within the stated purpose, but the skill explicitly uploads user media to https://mega-api-prod.nemovideo.ai and saves session_id — users should expect their videos and metadata to be transmitted and possibly retained by that service.

Install Mechanism

Instruction-only skill with no install steps or external downloads, so it writes no code to disk by itself. Low install risk.

Credentials

Only requests one credential (NEMO_TOKEN) which is reasonable for a hosted editing API. Metadata includes a config path for local state; this is plausible but users should be aware session state or tokens may be persisted under ~/.config/nemovideo/ if the agent implements storage.

Persistence & Privilege

always:false and no claims of modifying other skills or system-wide settings. The skill expects to persist its own session_id/token but does not request elevated or global privileges.

Assessment

This skill is coherent for cloud-based video editing, but before installing consider: (1) It will upload whatever video you give it to https://mega-api-prod.nemovideo.ai — do not send sensitive or private footage unless you trust that endpoint and have checked its privacy/retention policy. (2) The skill uses a NEMO_TOKEN (you can supply one or it will create a short-lived anonymous token); avoid giving long-lived or high-privilege credentials. (3) Metadata references ~/.config/nemovideo/ — the agent may store session_id or tokens there; inspect any stored files if you want to verify what is saved. (4) There is no install step (no local binaries), so risk is primarily data exfiltration of uploaded media rather than code execution. If you need stronger guarantees, ask the provider about data retention, encryption, and whether uploads can be restricted or deleted.

Getting Started

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

Try saying:

• "edit a 2-minute smartphone recording into a 1080p MP4"
• "trim the footage, add transitions, and export a clean final cut"
• "quickly editing raw videos without manual post-production for content creators"

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 AI Easy — Edit and Export Videos Fast

Drop your raw video footage in the chat and tell me what you need. I'll handle the AI-assisted video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute smartphone recording, ask for trim the footage, add transitions, and export a clean final cut, 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.

Matching Input to Actions

User prompts referencing video ai easy, 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-ai-easy
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)

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

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 "trim the footage, add transitions, and export a clean final cut" — 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 platforms.

Common Workflows

Quick edit: Upload → "trim the footage, add transitions, and export a clean final cut" → 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.