Editor Fiverr

Turn a 2-minute unedited talking-head clip into 1080p polished edited clips just by typing what you need. Whether it's getting professional-looking edits wit...

Security Scan

The skill's requirements and runtime instructions are mostly consistent with a cloud video-editing assistant, but there are small inconsistencies you should understand before installing (how tokens/config are obtained and a hidden config-path reference).

Purpose & Capability

The skill claims to call a cloud video editing API and the instructions describe exactly those API calls (session creation, upload, SSE, render). Requested credential (NEMO_TOKEN) fits the stated cloud service purpose. One inconsistency: the registry metadata listed no required config paths, but the SKILL.md frontmatter metadata references ~/.config/nemovideo/ (minor mismatch).

Instruction Scope

Instructions direct the agent to upload user video files, initiate sessions, poll SSE, and include attribution headers. They also instruct detecting install path to set X-Skill-Platform (this implies reading the agent's filesystem to check ~/.clawhub/ or ~/.cursor/skills/). These behaviors are explainable for returning the correct headers, but they do require access to user files (for uploads) and to the agent's install paths (for platform detection).

Install Mechanism

This is an instruction-only skill with no install spec or code to download or write to disk, so there is no installer risk.

Credentials

Registry declares NEMO_TOKEN as a required primary env var, but the SKILL.md explicitly documents a fallback anonymous-token flow (POST to /api/auth/anonymous-token) if NEMO_TOKEN is not set. That makes the 'required' designation inconsistent. Aside from that, only the service's token is requested — which is proportionate for a cloud editor — but bearer tokens grant full API access to the backend, so treat them as sensitive.

Persistence & Privilege

The skill does not request always: true and has no install-time persistence. It asks to 'save session_id' (presumably in-session state) but provides no instructions to modify other skills or system-wide config.

Scan Findings in Context

[no_regex_findings] expected: The scanner reported no findings because this is an instruction-only skill with no code files. The SKILL.md is the entire runtime surface and was reviewed above.

Assessment

This skill appears to do what it says: it uploads your video to a cloud rendering service (mega-api-prod.nemovideo.ai) and returns edited output. Before installing or using it: 1) Understand you will be uploading media to an external service — check privacy/terms for sensitive content. 2) The registry says NEMO_TOKEN is required, but the instructions also document creating a short-lived anonymous token if none is present; clarify with the publisher which token you should use. 3) The skill may inspect install paths to set X-Skill-Platform headers — if you are uncomfortable with the agent reading its install directories, ask for clarification. 4) Because bearer tokens grant API access, use a dedicated/limited token (or the anonymous flow) rather than a high-privilege account token. 5) If you need higher assurance, request the publisher or registry to provide a homepage, service documentation, or a signed code package; that would raise confidence from medium to high.

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 captions, and"

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.

Editor Fiverr — Edit and Export Videos Instantly

This tool takes your raw video footage 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 unedited talking-head clip and want to cut the pauses, add captions, and export a clean final video — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 3 minutes process significantly faster and use fewer credits.

Matching Input to Actions

User prompts referencing 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is editor-fiverr, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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.

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.

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

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

Common Workflows

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the pauses, add captions, and export a clean final video" — 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 widest compatibility across platforms.