Video Editor Fiverr

Get polished edited clips ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, WebM, up to 500MB), say something li...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-hosted AI video editing service: it needs a service token (NEMO_TOKEN) and makes API calls to the documented nemovideo endpoints; nothing in the bundle indicates it intends unrelated access.

Purpose & Capability

Name/description (AI video editing) align with the declared requirement (NEMO_TOKEN) and the SKILL.md, which documents uploading footage, session creation, SSE messaging, and export endpoints on mega-api-prod.nemovideo.ai — all expected for a remote video-editing skill.

Instruction Scope

The instructions require contacting an external API, uploading user video files, managing session tokens, and polling for renders — all within the editing use case. Two things to note: (1) the skill instructs detecting an install path (~/.clawhub/, ~/.cursor/skills/) and reading the frontmatter for X-Skill-Platform/Version headers, which implies checking local paths/configs; (2) the agent is told to persist a session_id and treat NEMO_TOKEN as an auth bearer token. Both behaviors are explainable for this service but involve reading local paths and handling bearer credentials, so users should understand those reads occur.

Install Mechanism

No install spec or code is included — this is instruction-only. That minimizes local disk writes and arbitrary code installation risk.

Credentials

Only one credential (NEMO_TOKEN) is required, which is proportionate for an API-backed editing service. The SKILL.md also describes an anonymous-token flow (POST to /api/auth/anonymous-token) that returns a short-lived token (7-day expiry). Be aware bearer tokens grant API access to upload/trigger renders and query credits; treat them like any service credential. Also there is an inconsistency: the registry summary lists no required config paths, but the skill frontmatter metadata includes a configPaths entry (~/.config/nemovideo/). This mismatch should be clarified.

Persistence & Privilege

Skill is not always-enabled and uses the platform default (agent-invocable/autonomous allowed). It instructs saving session_id and using NEMO_TOKEN for requests; that's normal for a remote API client. There is no instruction to modify system- or other-skills' configs.

Assessment

This skill appears coherent for a cloud video-editing service, but before installing consider: (1) it requires NEMO_TOKEN (or will obtain a 7-day anonymous token) — anyone holding that token can call the service on your behalf and access uploads/credits, so only provide tokens you intend to share; (2) the skill will upload any video files you give it to an external host (mega-api-prod.nemovideo.ai) — review privacy/TOS if your footage is sensitive; (3) the SKILL.md suggests the agent may check local install paths and a ~/.config/nemovideo/ path to set attribution headers — confirm what local files will be read and that you’re comfortable with that; (4) clarify the configPaths metadata mismatch with the publisher if you need strict guarantees about filesystem access. If you’re comfortable with these points, the skill’s requirements match its stated purpose.

Getting Started

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

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "cut the pauses, 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 Editor Fiverr — Edit and Export Pro Videos

Send me your raw video footage and describe the result you want. The AI video editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute unedited screen recording, type "cut the pauses, add background music, and export as a clean 60-second clip", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 3 minutes process significantly faster and give more precise AI results.

Matching Input to Actions

User prompts referencing video editor fiverr, 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.

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: video-editor-fiverr
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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

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.

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 "cut the pauses, add background music, and export as a clean 60-second clip" — 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 social platforms and clients.

Common Workflows

Quick edit: Upload → "cut the pauses, add background music, and export as a clean 60-second clip" → 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.