Video Editor In Browser

edit video clips into edited MP4 clips with this skill. Works with MP4, MOV, WebM, AVI files up to 500MB. content creators and marketers use it for editing a...

Security Scan

The skill is mostly coherent for a cloud-based video editor (it only needs a NEMO_TOKEN and calls a nemo API), but there are metadata inconsistencies and privacy/behavioral choices (automatic anonymous token generation, external uploads, and a referenced config path) that warrant caution before installing.

Purpose & Capability

Name/description match the runtime instructions: the skill talks to a nemo video backend to upload, edit, render, and return MP4s. Requesting NEMO_TOKEN as the primary credential is consistent. However, the SKILL.md frontmatter includes a required config path (~/.config/nemovideo/) while the registry metadata stated 'required config paths: none' — this mismatch should be resolved.

Instruction Scope

Instructions direct the agent to (a) generate an anonymous token by POSTing to https://mega-api-prod.nemovideo.ai, (b) create and store a session_id, and (c) upload user files (either multipart file paths or URLs). These actions are consistent with the editor purpose but involve sending user video data and session/auth tokens to an external service. The skill also instructs the agent to read install paths to set an X-Skill-Platform header and to read its own YAML frontmatter at runtime — both require filesystem access. The instructions say not to display raw tokens but do not specify secure storage location or retention policy.

Install Mechanism

No install spec or code is present (instruction-only), so nothing is written to disk by an installer. This is the lower-risk model for skills.

Credentials

Only one environment variable (NEMO_TOKEN) is declared and is appropriate for an API-based editor. But the SKILL.md will generate an anonymous token automatically if NEMO_TOKEN is missing — that grants the external service the ability to accept uploads and create render jobs on behalf of the user. The frontmatter's referenced config path (~/.config/nemovideo/) implies the skill might read or use a local config directory even though registry metadata listed none; that mismatch is concerning and should be clarified.

Persistence & Privilege

always:false (normal). The skill instructs storing session_id for the duration of the session and mentions orphaned cloud jobs if the client closes — this is expected for a remote render workflow and does not request elevated platform privileges. There is no instruction to modify other skills or system-wide settings.

What to consider before installing

This skill appears to be a legitimate cloud-based video editor, but proceed with caution. Before installing, consider: (1) Privacy — uploaded videos and generated tokens are sent to mega-api-prod.nemovideo.ai; do not use for sensitive content unless you trust the service and its policies. (2) Token handling — the skill will create and store an anonymous token if NEMO_TOKEN is not provided; ask where tokens/session IDs are stored and how long they persist. (3) Metadata mismatch — the SKILL.md references a local config path (~/.config/nemovideo/) while the registry says none; ask the author to clarify. (4) Confirm the service domain and owner identity (no homepage or publisher metadata is present here). If you need stronger guarantees, only install skills with a verified owner, published homepage/privacy policy, and explicit explanations of token storage and data retention.

Getting Started

Share your video clips and I'll get started on browser-based video editing. Or just tell me what you're thinking.

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "trim the intro, add text overlays,"

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 in Browser — Edit and Export Videos Online

This tool takes your video clips and runs browser-based video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-minute screen recording in MP4 and want to trim the intro, add text overlays, and export in 1080p — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 3 minutes process significantly faster in the browser.

Matching Input to Actions

User prompts referencing video editor in browser, 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.

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

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

• X-Skill-Source: video-editor-in-browser
• 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

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

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

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)

Common Workflows

Quick edit: Upload → "trim the intro, add text overlays, and export in 1080p" → 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 intro, add text overlays, and export in 1080p" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms and devices.