Fiverr Videoeditor Youtube

Turn a 10-minute unedited YouTube vlog recording into 1080p polished YouTube videos just by typing what you need. Whether it's editing YouTube videos without...

Security Scan

The skill is mostly coherent for a cloud AI video-editing integration, but there are metadata/instruction inconsistencies (env/config requirements) and it will call an external API, so you should review the token usage and the target domain before installing.

Purpose & Capability

The skill's name/description (AI video editing) matches the runtime instructions (upload, session creation, render/export endpoints). However, there's a mismatch in declared requirements: the registry listing shows no required config paths, while the SKILL.md frontmatter declares configPaths (~/.config/nemovideo/). Also the registry lists NEMO_TOKEN as required, but the SKILL.md explicitly instructs the agent to obtain an anonymous token if NEMO_TOKEN is absent. These inconsistencies suggest sloppy metadata rather than malicious intent, but they should be clarified.

Instruction Scope

The SKILL.md is instruction-only and confines itself to the stated service: establishing a session, uploading video, SSE chat, polling export status, and returning download URLs from mega-api-prod.nemovideo.ai. It does instruct the agent to read this file's YAML frontmatter and to detect install path (to set an X-Skill-Platform header), which requires local path inspection. There are no instructions to read unrelated system files or other environment variables.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is downloaded or written to disk by an installer. This is the lowest-risk install profile.

Credentials

The skill declares a single credential (NEMO_TOKEN) which is appropriate for a cloud API service, but two issues raise concern: (1) the registry required-env listing implies NEMO_TOKEN is mandatory, yet SKILL.md supports auto-acquiring an anonymous token if absent; (2) the SKILL.md metadata claims a config path (~/.config/nemovideo/) which could expose local configuration if read. Requesting an API token is proportionate for this purpose, but the inconsistent declarations and the implied potential to read a local config directory warrant caution.

Persistence & Privilege

The skill is not marked always:true and does not request elevated or persistent platform presence. It does instruct adding attribution headers derived from install path/frontmatter, but it does not ask to modify other skills or system settings. Autonomous invocation is allowed (platform default) but not by itself a problem.

What to consider before installing

This skill appears to implement a cloud video-editing integration and needs a NEMO_TOKEN (or will request an anonymous token from mega-api-prod.nemovideo.ai). Before installing: (1) confirm you trust the domain mega-api-prod.nemovideo.ai and the service’s privacy/terms because your video files will be uploaded; (2) decide whether you want to provide a persistent NEMO_TOKEN (it grants the skill bearer access to the service under your account) or allow the skill to use an anonymous token (short-lived, limited credits); (3) be aware the skill asks the agent to read its own frontmatter and detect install path (it may inspect ~/.config/nemovideo/ if present) — ensure no sensitive tokens or unrelated secrets are stored there; (4) ask the skill author to resolve the metadata inconsistencies (registry vs SKILL.md) so you know whether NEMO_TOKEN and the config path are actually required. If you don’t trust the remote service or don’t want uploads to an external cloud, do not install or provide a token.

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"
• "trim silences, add intro, cut to"

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.

Fiverr Video Editor YouTube — Edit and Export YouTube Videos

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 10-minute unedited YouTube vlog recording and want to trim silences, add intro, cut to 8 minutes with smooth transitions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: splitting a long video into segments before uploading speeds up processing significantly.

Matching Input to Actions

User prompts referencing fiverr videoeditor youtube, 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: fiverr-videoeditor-youtube
• 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)

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

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 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 "trim silences, add intro, cut to 8 minutes with smooth transitions" — 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 YouTube upload compatibility.

Common Workflows

Quick edit: Upload → "trim silences, add intro, cut to 8 minutes with smooth transitions" → 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.