Ai Video Editor Or Maker

edit video clips or images into polished edited videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators and marketers use...

Security Scan

The skill generally matches an AI video-editing purpose, but there are small inconsistencies and a few runtime behaviors (filesystem probing, external anonymous-token calls, unknown upstream service) that you should review before installing.

Purpose & Capability

Name/description match the runtime instructions: it uploads media, sends editing requests, and exports rendered MP4s via a cloud API that uses a single NEMO_TOKEN. However the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) that was not listed in the registry requirements provided to you earlier — a minor metadata inconsistency to verify.

Instruction Scope

The instructions direct the agent to call external endpoints (mega-api-prod.nemovideo.ai) to obtain anonymous tokens and manage sessions, and to upload user files there. They also instruct the agent to read its own SKILL.md frontmatter and probe install paths (e.g., ~/.clawhub/, ~/.cursor/skills/) to set X-Skill-Platform attribution. That filesystem probing and unconditional inclusion of attribution headers is beyond simple request handling and should be expected and reviewed.

Install Mechanism

Instruction-only skill with no install spec or downloaded code; nothing is written to disk by an installer. This is lower risk than remote installs.

Credentials

Only one required credential is declared (NEMO_TOKEN), which is appropriate for a cloud video service. The skill will also generate and use an anonymous token by POSTing to the vendor API if no token is present. Verify you are comfortable with uploads of media to the unknown third‑party service and that NEMO_TOKEN scope is limited.

Persistence & Privilege

No 'always: true' or other elevated persistence requested. The skill only asks to read its own metadata and probe likely install paths for attribution; it does not request system-wide configuration changes.

What to consider before installing

This skill behaves like a normal cloud-based video editor: it needs a NEMO_TOKEN (or it will obtain a short-lived anonymous token) and it uploads your media to mega-api-prod.nemovideo.ai for processing. Before installing: 1) Confirm you trust the nemovideo endpoint — the skill's source and homepage are unknown. 2) Prefer using a scoped/test token (not a high-privilege credential or corporate credential). 3) Expect the skill to read its SKILL.md and probe common install paths and ~/.config/nemovideo/ for attribution — if you dislike filesystem probes, avoid installing. 4) If you plan to upload sensitive video, validate the vendor's privacy and retention policies. If anything is unclear, ask the skill author for the service documentation or consider running the skill in an isolated/sandboxed environment.

Getting Started

Share your video clips or images and I'll get started on AI video editing and creation. Or just tell me what you're thinking.

Try saying:

• "edit my video clips or images"
• "export 1080p MP4"
• "trim the pauses, add background music,"

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 or Maker — Edit and Export Polished Videos

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

Say you have a 2-minute raw screen recording and want to trim the pauses, add background music, and export as a short reel — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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-or-maker
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the pauses, add background music, and export as a short reel" — 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 pauses, add background music, and export as a short reel" → 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.