Youtube Video Editor And Downloader

Skip the learning curve of professional editing software. Describe what you want — download this YouTube video and trim it to the best 2 minutes with smooth...

Security Scan

The skill's requested access and runtime instructions are coherent with a cloud-based YouTube download/edit service, with only minor metadata inconsistencies and normal privacy considerations (uploads to an external API).

Purpose & Capability

Name/description match the runtime instructions: the skill drives a remote video-render API (download, edit, export). Requesting an API token (NEMO_TOKEN) and using HTTP endpoints is proportionate to that purpose.

Instruction Scope

The SKILL.md explicitly instructs the agent to call nemovideo.ai endpoints (auth, session creation, upload, render, polling) and to stream SSE. It also instructs reading the skill's frontmatter and detecting install path to set X-Skill-* headers (i.e., reading local skill metadata / install path). That filesystem metadata read is reasonable for attribution but expands scope beyond pure network calls. The doc also tells the agent how to obtain an anonymous token if no NEMO_TOKEN is present (network call).

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. Nothing is downloaded or written by an installer according to the package metadata.

Credentials

Only NEMO_TOKEN is declared as required (primary credential). The skill can also acquire a short-lived anonymous token if none is provided. This is proportionate to remote API usage. Be aware that video files (potentially sensitive) are uploaded to https://mega-api-prod.nemovideo.ai, so providing the token or using anonymous auth will transmit user content to that external service.

Persistence & Privilege

always:false and no apparent attempt to modify other skills or system-wide settings. Session tokens and render jobs are transient and server-side. The skill does reference a config path in its frontmatter (~/.config/nemovideo/) for metadata, but it does not require persistent privileges or always-on presence.

Assessment

This skill appears to do what it says: it uploads videos and controls remote editing/rendering on nemovideo.ai. Before installing or using it, consider: (1) Privacy — your uploaded videos (and any audio) will be sent to an external service (mega-api-prod.nemovideo.ai). Don't upload private or proprietary content unless you trust that service. (2) Credentials — you can supply NEMO_TOKEN or let the skill obtain an anonymous token (limited credits). Only provide an API token if you trust the owner and understand the token's permissions. (3) Metadata mismatch — the skill's SKILL.md mentions a config path (~/.config/nemovideo/) and reading frontmatter/install path for X-Skill-* headers, but registry metadata listed no config paths; this is a minor inconsistency to be aware of. (4) Billing/credits — exports may be limited or gated by credits or subscription tiers; check the service's terms before submitting large jobs. If you need higher confidence, ask the publisher for a homepage, privacy policy, or official documentation for the nemovideo.ai service and verify ownership/legitimacy of the domain and API.

Getting Started

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

Try saying:

• "edit a 10-minute YouTube tutorial video into a 1080p MP4"
• "download this YouTube video and trim it to the best 2 minutes with smooth transitions"
• "downloading and editing YouTube videos for reuse or repurposing for YouTubers"

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 and Downloader — Download, Edit and Export Videos

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

A quick example: upload a 10-minute YouTube tutorial video, type "download this YouTube video and trim it to the best 2 minutes with smooth transitions", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips process faster — trim your target section before applying effects.

Matching Input to Actions

User prompts referencing youtube video editor and downloader, 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.

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

• X-Skill-Source: youtube-video-editor-and-downloader
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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.

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.

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

Common Workflows

Quick edit: Upload → "download this YouTube video and trim it to the best 2 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "download this YouTube video and trim it to the best 2 minutes with smooth transitions" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, WebM, MOV, AVI for the smoothest experience.

Export as MP4 for widest compatibility across platforms and devices.