Video Editing With Online

Cloud-based video-editing-with-online tool that handles editing videos directly in the browser without software. Upload MP4, MOV, AVI, WebM files (up to 500M...

Security Scan

The skill's instructions, endpoints, and single required credential (NEMO_TOKEN) align with a cloud video-editing tool; there are a few minor metadata/information-disclosure concerns you should review before installing.

Purpose & Capability

The name/description match the runtime instructions: the SKILL.md documents uploading video files, creating a session, and calling a named backend (mega-api-prod.nemovideo.ai) to render and export MP4s. Requesting a service token (NEMO_TOKEN) is proportionate to this purpose. One inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier stated 'Required config paths: none' — this mismatch should be clarified.

Instruction Scope

All runtime actions are focused on the described backend API (auth, session creation, upload, SSE, render) and on sending user media to that service. The instructions also direct the agent to detect install path to set an X-Skill-Platform header (e.g., inspect ~/.clawhub/ or ~/.cursor/skills/), which implies reading local path information for attribution and could disclose local install paths. Otherwise the instructions do not request reading unrelated system files or additional credentials.

Install Mechanism

There is no install spec and no code files — this is an instruction-only skill. That minimizes risk from third-party packages or arbitrary downloads.

Credentials

The skill requires a single env var, NEMO_TOKEN, which is appropriate for an API-backed editing service. Minor concern: the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) in metadata while the registry summary listed none — this inconsistency could indicate the skill expects to access a local config directory (read-only attribution) and should be confirmed.

Persistence & Privilege

always:false and normal autonomous invocation are used. The skill does not request permanent presence or system-wide config changes and does not attempt to modify other skills' settings.

Assessment

This skill appears to do what it claims (upload your videos to mega-api-prod.nemovideo.ai and perform cloud rendering) and needs one token (NEMO_TOKEN). Before installing: (1) Confirm you trust the external service and its privacy policy — your videos and metadata will be sent to that API. (2) Do not reuse sensitive or unrelated credentials as NEMO_TOKEN (e.g., cloud provider keys). (3) Note the skill may generate an anonymous token by POSTing to the service if you don't provide NEMO_TOKEN; this is expected but results in outbound network calls. (4) The skill asks the agent to detect install path and set attribution headers — that can disclose local install path information; if that is a concern, request the author remove/install-path attribution or run in a sandbox. (5) Clarify the config-path mismatch (~/.config/nemovideo/) shown in the SKILL.md frontmatter vs registry metadata. If you don't recognize the skill owner or cannot verify the service, avoid providing your own token and consider running uploads through a separate, privacy-controlled workflow.

Getting Started

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

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "trim the clip, add transitions, and"

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 Editing With Online — Edit and Export Videos Online

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

Say you have a 2-minute screen recording or phone video and want to trim the clip, add transitions, and export as MP4 — 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 editing with online, 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: video-editing-with-online
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s 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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the clip, add transitions, and export as MP4" — 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 platforms and devices.

Common Workflows

Quick edit: Upload → "trim the clip, add transitions, and export as 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.