Video Editor For Beginners Pc

edit raw video clips into polished edited clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. beginners and first-time video creators us...

Security Scan

The skill mostly behaves like a cloud-based video editor and only needs a single API token, but there are inconsistencies in the declared metadata and the runtime instructions that warrant caution before installing or providing credentials.

Purpose & Capability

The name/description (cloud video editor) matches the actions described (create session, upload video, render/export). However the skill registry metadata and the SKILL.md disagree: the top-level registry said no required config paths, while the SKILL.md frontmatter declares a config path (~/.config/nemovideo/). Also the skill marks NEMO_TOKEN as a required env var yet includes an anonymous-token fallback flow — this mixed signal is inconsistent.

Instruction Scope

Instructions are focused on the video-editing workflow (session creation, SSE messaging, upload, render/poll, download). They also instruct the agent to read the skill's YAML frontmatter at runtime and to detect install path (e.g., ~/.clawhub, ~/.cursor), and reference a local config directory (~/.config/nemovideo/). Those file-system checks are plausible for finding stored tokens or attribution, but they expand scope beyond pure API calls and were not uniformly declared in the registry metadata.

Install Mechanism

No install spec and no code files — instruction-only skills have minimal install risk. There are no downloads or third-party package installs described.

Credentials

The skill requests one primary credential (NEMO_TOKEN), which is reasonable for a cloud API. But it's listed as 'required' while the SKILL.md also prescribes generating and using an anonymous token when NEMO_TOKEN is absent — the registry should not mark it as strictly required if fallback is supported. The SKILL.md's mention of a config path (~/.config/nemovideo/) could give the skill access to local files that may contain additional secrets; that path was not declared in the top-level manifest.

Persistence & Privilege

The skill does not request always:true and contains no install-time persistence. It does not ask to modify other skills or system settings. Autonomous invocation is allowed (platform default) but not combined here with other high-privilege features.

What to consider before installing

This skill largely appears to do what it claims (cloud-based video edits using a NEMO_TOKEN). Before installing or supplying credentials: (1) note the metadata mismatch — the SKILL.md references a local config directory (~/.config/nemovideo/) and install-path detection even though the registry showed no config paths; this means the skill may attempt to read local files for tokens or attribution. (2) Only provide a NEMO_TOKEN if you trust https://mega-api-prod.nemovideo.ai and its privacy practices; prefer using a limited/anonymous token if possible. (3) Avoid uploading videos that contain sensitive secrets or PII you don't want sent to an external service. (4) If you need higher assurance, ask the skill author for a clear manifest that matches the SKILL.md (declare config paths or remove them) and for a privacy/terms link for nemovideo.ai. If you want, share the full SKILL.md and manifest and I can re-check any additional inconsistencies.

Getting Started

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

Try saying:

• "edit a 3-minute screen recording or phone video into a 1080p MP4"
• "trim the boring parts, add transitions, and put text titles on each section"
• "editing raw footage into a finished video without prior experience for beginners and first-time video creators"

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.

Video Editor for Beginners PC — Edit and Export Finished Videos

Drop your raw video clips in the chat and tell me what you need. I'll handle the AI-assisted video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 3-minute screen recording or phone video, ask for trim the boring parts, add transitions, and put text titles on each section, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — keep clips under 5 minutes for faster processing and smoother AI edits.

Matching Input to Actions

User prompts referencing video editor for beginners pc, 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.

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

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

• X-Skill-Source: video-editor-for-beginners-pc
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the boring parts, add transitions, and put text titles on each section" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across YouTube, social media, and PC playback.

Common Workflows

Quick edit: Upload → "trim the boring parts, add transitions, and put text titles on each section" → 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.