Youtube Video Editor Fiverr

Skip the learning curve of professional editing software. Describe what you want — trim dead air, add transitions, and sync background music to cuts — and ge...

Security Scan

The skill's requirements and runtime instructions generally match its stated purpose (remote AI video editing), but a small metadata inconsistency and privacy considerations around uploading videos warrant caution.

Purpose & Capability

The skill requests a single service credential (NEMO_TOKEN) which is appropriate for a cloud video-editing API. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that the registry metadata did not list; it's unclear whether the skill actually needs or will read local config files, which is disproportionate for a purely cloud-based editor.

Instruction Scope

Runtime instructions are limited to establishing a session, uploading media, streaming edits via SSE, polling render status, and returning download URLs. The instructions do not ask for unrelated system files or additional credentials. They do instruct using an environment token if present or obtaining an anonymous token via the service's API — behavior consistent with the described cloud workflow.

Install Mechanism

This is an instruction-only skill with no install spec or code files, so nothing is written to disk or downloaded at install time — lowest-risk install mechanism.

Credentials

Only NEMO_TOKEN is required, which is proportional to calling the provider's API. Note: the frontmatter references a local config path that wasn't declared in the registry top-level requirements; clarify whether the skill will read ~/.config/nemovideo/ or any other local files before installing or providing a token.

Persistence & Privilege

The skill does not request permanent/always-on presence (always: false) and does not modify other skills or system-wide config. Autonomous invocation is allowed but is the platform default and is not by itself a red flag.

Assessment

This skill appears to do what it advertises: connect to nemovideo's backend, accept uploads, and return edited videos. Before installing or enabling it, consider: (1) Only provide a NEMO_TOKEN you intend for this service — don't reuse high-privilege or unrelated service tokens. (2) Confirm privacy: uploaded videos will be sent to https://mega-api-prod.nemovideo.ai; avoid uploading sensitive or private footage unless you've reviewed their privacy/terms. (3) Ask the publisher to clarify the frontmatter reference to ~/.config/nemovideo/ (does the agent read local config files?). (4) Because the skill can obtain an anonymous token from the provider if no token is present, be aware that uploads will still go to the provider even if you don't supply a token. If any of these points are unacceptable, don't install or don't upload sensitive media.

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 dead air, add transitions, and"

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.

YouTube Video Editor — Edit and Export YouTube 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 10-minute unedited YouTube vlog recording, type "trim dead air, add transitions, and sync background music to cuts", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: splitting your video into shorter segments before uploading speeds up processing significantly.

Matching Input to Actions

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

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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	youtube-video-editor-fiverr
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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

Common Workflows

Quick edit: Upload → "trim dead air, add transitions, and sync background music to cuts" → 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 "trim dead air, add transitions, and sync background music to cuts" — 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 balance of quality and file size on YouTube.