Video Editor With Ai Effects

Turn a 90-second smartphone recording into 1080p AI-enhanced videos just by typing what you need. Whether it's applying AI visual effects to raw footage for...

Security Scan

The skill's behavior mostly matches a cloud video-editing service, but there are small inconsistencies (missing provenance, a mismatched configPath declaration in the skill text vs registry metadata) and it will upload your raw video to an external API and may mint anonymous tokens — review before installing or sending sensitive videos.

Purpose & Capability

Name/description (AI video editing) align with the instructions: the skill calls a cloud render API, uploads video, creates sessions, and exports rendered MP4s. Requesting a single API token (NEMO_TOKEN) is coherent. However, SKILL.md frontmatter references a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch is unexplained and should be clarified.

Instruction Scope

The SKILL.md gives explicit runtime steps: use NEMO_TOKEN if present or POST an anonymous-token endpoint, create sessions, upload videos, use SSE for edits, poll exports, and include specific attribution headers. These instructions stay within the editing use-case, but they require uploading user video/audio to https://mega-api-prod.nemovideo.ai and creating or using tokens automatically. The skill also instructs the agent to 'keep technical details out of the chat' (user-facing obfuscation) and to auto-detect platform from install path — both are minor flags to review.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. Nothing is written to disk by an installer here (the frontmatter's configPath mention is informational rather than an installer).

Credentials

Only one credential (NEMO_TOKEN) is required, which is proportionate for a cloud API. However, the skill will self-provision an anonymous token via the external API if NEMO_TOKEN is not present, which means the agent will perform network calls that obtain credentials automatically. Also note the frontmatter in SKILL.md declares a config path (~/.config/nemovideo/) not listed in the registry metadata — this inconsistency is unexplained and could imply additional local config expectations.

Persistence & Privilege

always is false and the skill does not request to be force-enabled. It does not request system-wide configuration changes or other skills' credentials. Autonomous invocation is allowed (platform default) but not compounded by elevated persistent privileges.

What to consider before installing

This skill appears to be a front-end to a third-party cloud video-editing API (mega-api-prod.nemovideo.ai). Before installing or using it: 1) Understand that any video you send will be uploaded to that external service — do not send sensitive or private footage unless you trust the service and have read its terms/privacy policy. 2) If you have an account token (NEMO_TOKEN), it will be used; if not, the skill will request an anonymous token automatically (it will POST a UUID to the service). 3) Ask the publisher to clarify the mismatched configPath: SKILL.md references ~/.config/nemovideo/ while registry metadata does not — confirm whether the skill will read local config files. 4) Prefer skills with a known source/homepage; this skill has no published homepage or owner info beyond an ID. If you proceed, monitor and revoke any token you provide, and avoid uploading highly sensitive content until provenance is confirmed.

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 effects editing.

Try saying:

• "edit a 90-second smartphone recording into a 1080p MP4"
• "add cinematic color grading and apply AI motion blur to fast cuts"
• "applying AI visual effects to raw footage for social media for content creators"

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.

Video Editor with AI Effects — Apply AI Effects to Videos

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

Here's a typical use: you send a a 90-second smartphone recording, ask for add cinematic color grading and apply AI motion blur to fast cuts, 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 — clips under 60 seconds render faster and give AI effects more precision.

Matching Input to Actions

User prompts referencing video editor with ai effects, 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-editor-with-ai-effects
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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)

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

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 "add cinematic color grading and apply AI motion blur to fast cuts" — 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 cinematic color grading and apply AI motion blur to fast cuts" → 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.