Video Editing For Beginners Youtube

Get YouTube-ready videos ready to post, without touching a single slider. Upload your raw video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like...

Security Scan

The skill's behavior mostly matches a cloud video-editing service (it needs a NEMO_TOKEN and uploads videos to a nemovideo.ai API), but there are small inconsistencies and a few instructions that imply local probing and external data exfiltration that you should understand before installing.

Purpose & Capability

Name/description (cloud video editing) aligns with the runtime instructions to upload clips and call nemovideo.ai endpoints; requesting a single service token (NEMO_TOKEN) is expected. However, SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata above listed no required config paths — this mismatch should be clarified.

Instruction Scope

Instructions are explicit about uploading user video files, starting sessions, SSE streaming, polling renders, and including Authorization headers — all coherent for a remote render service. Two points to note: (1) headers include an X-Skill-Platform value 'detected from the install path' which implies the agent will probe filesystem locations (e.g., ~/.clawhub/, ~/.cursor/skills/) to derive a header; and (2) user video files and session metadata will be transmitted to an external domain (mega-api-prod.nemovideo.ai). Both behaviors are reasonable for this service but constitute data exposure and limited local probing.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. Nothing is downloaded or written to disk by an installer step described in SKILL.md.

Credentials

Only one credential is requested (NEMO_TOKEN) which is appropriate for a hosted API. The SKILL.md also documents how to obtain an anonymous token via an API call if NEMO_TOKEN is not present. The frontmatter's declaration of a config path (~/.config/nemovideo/) is not reflected in the registry metadata earlier; this inconsistency should be resolved. No unrelated credentials are requested.

Persistence & Privilege

always is false, and the skill does not request persistent system-wide privileges. It does imply maintaining session state with the remote API (session_id, render job ids) which is normal for this type of service.

What to consider before installing

This skill appears to be a thin client for a cloud video-rendering service: using it will upload your raw videos and related metadata to mega-api-prod.nemovideo.ai and require an API token (NEMO_TOKEN). Before installing, consider: (1) privacy — you will be transmitting potentially sensitive video/audio to a third party; (2) token handling — the skill can generate anonymous tokens for short-term use but may also use a long-lived NEMO_TOKEN if provided; (3) local probing — the skill asks for a header derived from detecting install paths (it may check common skill directories), which reveals some information about your environment; and (4) metadata mismatch — the SKILL.md lists a config path that the registry metadata does not, so confirm whether the skill will read or write ~/.config/nemovideo/ or other local files. If any of these are unacceptable (sensitive content, unclear token persistence, or unwanted local file access), do not install until the publisher clarifies these points and provides a privacy/security policy and a trusted homepage or source.

Getting Started

Share your raw video clips and I'll get started on AI automated editing. Or just tell me what you're thinking.

Try saying:

• "edit my raw video clips"
• "export 1080p MP4"
• "trim the long pauses, add transitions,"

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.

Video Editing for Beginners YouTube — Edit and Export YouTube Videos

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

A quick example: upload a 10-minute unedited screen recording or phone footage, type "trim the long pauses, add transitions, and put my channel intro at the start", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: keep your raw clips under 10 minutes for faster processing and cleaner AI cuts.

Matching Input to Actions

User prompts referencing video editing for beginners 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-editing-for-beginners-youtube, 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).

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the long pauses, add transitions, and put my channel intro at the start" — 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 the long pauses, add transitions, and put my channel intro at the start" → 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.