Video Maker Editor

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

Security Scan

The skill's requirements and runtime instructions are generally consistent with a third‑party cloud video editing service (it needs a NEMO_TOKEN and calls nemovideo.ai endpoints), but it asks the agent to read some local paths and will upload user media to an external API — review privacy before use.

Purpose & Capability

The skill name and description match the declared runtime behavior: it talks to a cloud video-processing API and requires a single service token (NEMO_TOKEN). Minor inconsistency: the registry metadata reported no required config paths, while the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) and logic to detect install paths for attribution headers. This mismatch is worth noting but does not break coherence.

Instruction Scope

SKILL.md instructs the agent to obtain or reuse a NEMO_TOKEN, create sessions, upload user media, stream edits via SSE, poll render status, and add attribution headers. Those actions are within the expected scope for a cloud video editor. Two items to watch: (1) it directs the agent to inspect an install path to set X-Skill-Platform (e.g., checking ~/.clawhub or ~/.cursor/skills) and to read the skill's YAML frontmatter at runtime — both require filesystem reads beyond simply handling an upload; (2) all user media and edit metadata are sent to a third‑party endpoint (mega-api-prod.nemovideo.ai), so user privacy and content ownership are relevant concerns.

Install Mechanism

No install spec and no code files — instruction-only skill. This is the lowest install risk (nothing is downloaded or written by an installer).

Credentials

Only a single environment variable (NEMO_TOKEN) is declared as required, which is proportionate for a cloud service. However, the SKILL.md also references a config path (~/.config/nemovideo/) and recommends storing/using the anonymous token; reading ~/.config or install paths could expose cached tokens or config beyond the single declared env var. Ensure the agent isn't granted broader filesystem access than intended.

Persistence & Privilege

The skill does not request always:true and does not declare any system-wide config changes. It generates per-session tokens and session_id values but does not request permanent elevated privileges. The default ability for the agent to invoke the skill autonomously is the platform default and not flagged on its own.

Assessment

This skill uploads your video files and edit instructions to a third‑party service (mega-api-prod.nemovideo.ai) and uses a NEMO_TOKEN for authorization. Before installing or using it: (1) confirm you trust that remote service with the content you upload (do not upload sensitive or confidential video/audio); (2) prefer using an anonymous/disposable token if you only need a short trial — the SKILL.md documents an anonymous-token flow with 7‑day expiry; (3) be aware the skill may read local paths (e.g., ~/.config/nemovideo/ and install directories) to set attribution headers — if you do not want the agent to access these files, restrict filesystem permissions or decline those actions; (4) if you need higher assurance, ask the publisher for a homepage, privacy policy, or code, or test with non‑sensitive media and a disposable account. If you want me to, I can extract the exact API calls the skill will make and walk through the data that will be sent so you can evaluate privacy implications more precisely.

Getting Started

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

Try saying:

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

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 Maker Editor — Make and Edit Videos Fast

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

Say you have a 2-minute raw phone recording and want to trim the footage, add background music, and include text overlays — 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 video maker editor, 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: video-maker-editor
• 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.

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the footage, add background music, and include text overlays" — 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 and devices.

Common Workflows

Quick edit: Upload → "trim the footage, add background music, and include text overlays" → 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.