Online Video Editor Youtube

Turn a 10-minute YouTube vlog recording into 1080p YouTube-ready videos just by typing what you need. Whether it's editing and polishing videos for YouTube u...

Security Scan

The skill mostly behaves like a cloud video editor (it only needs a single service token) but contains internal inconsistencies about config paths and requires uploading user videos to a third‑party API — the functional footprint is plausible but some details don't add up and raise privacy/clarity concerns.

Purpose & Capability

The name/description (YouTube video editor) matches the network endpoints and actions described (upload, render, export). Requesting a single NEMO_TOKEN credential and interacting with nemovideo.ai is coherent with the stated purpose. However the SKILL.md frontmatter declares a required config path (~/.config/nemovideo/) while the registry metadata earlier lists no config paths — that inconsistency should be clarified (why would a simple instruction-only skill need a local config path?).

Instruction Scope

Runtime instructions are narrowly scoped to connecting to the nemovideo.ai API: obtain or use NEMO_TOKEN, create a session, upload files, stream SSE edits, poll render status, and return download URLs. The instructions explicitly require uploading user video/audio/image files to the remote service; this is expected for a cloud editor but is a privacy-sensitive operation. The instructions do not request unrelated system files or extra environment variables.

Install Mechanism

There is no install spec and no code files — the skill is instruction-only, which is the lowest install risk. Nothing is downloaded or written by an installer as part of the skill definition.

Credentials

Only one credential (NEMO_TOKEN) is declared as required, which is proportionate for a cloud editing API. The frontmatter also lists a config path (~/.config/nemovideo/) which is not declared elsewhere in the registry metadata — this inconsistency could indicate the skill expects to read or write local configuration (and possibly tokens) but that behavior is not described in the instructions. Confirm whether the skill will store tokens or session data locally.

Persistence & Privilege

always is false (no forced inclusion) and the skill does not request elevated platform privileges. Autonomous invocation is allowed by default which is expected for skills. There is no instruction to alter other skills or global agent settings.

What to consider before installing

This skill appears to be a normal cloud-based video editor: it uploads your media to nemovideo.ai, uses a single service token (NEMO_TOKEN), creates sessions, and returns a downloadable MP4. Before installing or using it, consider: (1) Privacy — your videos are uploaded to a third-party service (nemovideo.ai). Do not upload sensitive or private footage unless you trust the provider and reviewed their privacy/retention policy. (2) Token and storage handling — the SKILL.md frontmatter references a local config path (~/.config/nemovideo/) but the registry metadata omitted it; ask the publisher whether tokens or session data will be stored on disk and where. (3) Token lifecycle — the anonymous token flow returns a short-lived token (noted as 7-day expiry); confirm how refresh/renewal and deletion are handled. (4) Verify the service — check the domain (TLS certificate, company, privacy terms) before sending content. If you need the skill for non-sensitive content and the vendor checks out, the required env var (NEMO_TOKEN) and network calls are proportionate. If you cannot verify the service or are concerned about privacy, do not use this skill with private videos.

Getting Started

Ready when you are. Drop your video clips here or describe what you want to make.

Try saying:

• "edit a 10-minute YouTube vlog recording into a 1080p MP4"
• "trim the pauses, add intro text, and export for YouTube upload"
• "editing and polishing videos for YouTube upload for YouTubers"

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.

Online Video Editor for YouTube — Edit and Export YouTube Videos

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 10-minute YouTube vlog recording and want to trim the pauses, add intro text, and export for YouTube upload — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 5 minutes process significantly faster.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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	online-video-editor-youtube
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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.

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the pauses, add intro text, and export for YouTube upload" — 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 YouTube compatibility.

Common Workflows

Quick edit: Upload → "trim the pauses, add intro text, and export for YouTube upload" → 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.