Video Editor For Pc

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

Security Scan

The skill appears to do what it claims (remote AI video editing) but contains inconsistencies about required credentials/config paths and will upload user videos to an external backend with an anonymous token — these mismatches and the unknown source make it worth closer scrutiny before installing.

Purpose & Capability

The skill's stated purpose (remote AI video editing) matches the API calls and flows described in SKILL.md. Requesting a NEMO_TOKEN is coherent with a remote service. However the registry metadata and the SKILL.md disagree: registry lists no config paths while the SKILL.md frontmatter declares ~/.config/nemovideo/ and marks NEMO_TOKEN as required even though the instructions will auto-generate an anonymous token if none is present. The package source/homepage is unknown, which reduces transparency.

Instruction Scope

The runtime instructions stay within the editing workflow: create/refresh session tokens, upload video files (multipart or URL), send edits via SSE, poll render status, and return a download URL. No instructions ask the agent to read unrelated system files or other credentials. Important privacy implication: user video files and session tokens are transmitted/stored by the external API (mega-api-prod.nemovideo.ai).

Install Mechanism

This is instruction-only with no install spec or code to download — low installation risk. There is no package download or archive extraction referenced.

Credentials

The registry declares NEMO_TOKEN as a required env var and primary credential, but SKILL.md explicitly supports auto-creating an anonymous token if NEMO_TOKEN is not set. That inconsistency is confusing: the skill does not strictly require a pre-provided secret. The frontmatter's declared config path (~/.config/nemovideo/) is not reflected in the registry metadata. Overall the number and type of credentials requested (a single service token) is proportionate to the purpose, but the mismatched declaration and the fact tokens are generated and used server-side are reasons to verify how tokens/session data are stored and protected.

Persistence & Privilege

The skill does not request always:true and has no install-time persistence. The frontmatter references a user config path (~/.config/nemovideo/), but SKILL.md does not specify writing files there — it's unclear whether session IDs or tokens are persisted to disk. Confirm where session state is stored if you care about local persistence of tokens or job IDs.

What to consider before installing

This skill will upload your videos and manage short-lived anonymous tokens on a third‑party service (mega-api-prod.nemovideo.ai). Before installing: 1) Be comfortable with your video content leaving your machine and being processed by that external service; do not use for sensitive/confidential footage unless you trust the operator. 2) Note the registry metadata disagrees with SKILL.md about required env vars and config paths — ask the publisher to clarify how NEMO_TOKEN is used and where session tokens are stored. 3) Because the skill's source/homepage is unknown, prefer installing only if you can verify the service operator or allow the skill network access to be restricted so uploads go only to known endpoints. 4) If you require stronger privacy, avoid using anonymous upload flows or require an account and explicit consent before sending files.

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 the silent parts, add transitions,"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Video Editor for PC — Edit and Export HD 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 3-minute screen recording or phone video, type "trim the silent parts, add transitions, and export as 1080p MP4", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 2 minutes process significantly faster than long recordings.

Matching Input to Actions

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

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.

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

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

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

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

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)

Common Workflows

Quick edit: Upload → "trim the silent parts, add transitions, and export as 1080p MP4" → 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 the silent parts, add transitions, and export as 1080p MP4" — 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 widest compatibility across platforms.