Name Of Video Editing

Skip the learning curve of professional editing software. Describe what you want — trim the pauses, add transitions, and export a clean final cut — and get e...

Security Scan

The skill's behavior (calling an external nemovideo API and handling uploads) matches its description, but there are inconsistencies in its declared config requirements and a few instructions that merit caution before installing or using it.

Purpose & Capability

The name/description (AI cloud video editing) aligns with the runtime instructions: session creation, file upload, SSE conversation, and render/export flows to a nemovideo.ai backend. That API access and a token (NEMO_TOKEN) are reasonable for this purpose. However, the SKILL.md frontmatter lists a required config path (~/.config/nemovideo/) while the registry metadata shows no required config paths—an inconsistency that should be resolved.

Instruction Scope

SKILL.md instructions stay within video-editing scope: establishing a session, uploading user-provided video files, sending SSE edit commands, polling render status, and returning download URLs. Notable runtime behaviors: (1) if NEMO_TOKEN is absent the skill is instructed to automatically request an anonymous token from the service (network contact and automatic credential acquisition), (2) it tells the agent to include attribution headers and detect install paths to set X-Skill-Platform, and (3) it instructs forming multipart uploads from local file paths. These are expected for cloud editing, but automatic anonymous-token creation and local path detection are ops the user should be aware of.

Install Mechanism

Instruction-only skill with no install spec and no code files. Nothing is written to disk by an installer step in the package metadata, which is low-risk from an installation perspective.

Credentials

The skill declares a single primary credential (NEMO_TOKEN), which is proportionate to a cloud API-based editor. However, SKILL.md metadata also references a config path (~/.config/nemovideo/) that could imply reading local configuration files; the registry metadata did not declare this path. In addition, the skill will attempt to obtain an anonymous token if NEMO_TOKEN is missing, meaning it can operate without a user-supplied secret but will perform network calls to obtain credentials.

Persistence & Privilege

The skill is not declared always:true and does not request system-wide privileges. It does not attempt to modify other skills or agent-wide config in the provided instructions. Autonomous invocation is allowed (platform default) but not unusual here.

What to consider before installing

This skill appears to do what it claims: it will upload your videos to an external nemovideo.ai backend, run cloud rendering, and return download links. Before installing or using it: (1) Be comfortable that your video files will be transmitted to and processed by an external service (check their privacy/retention policy). (2) Prefer providing your own NEMO_TOKEN (stored in environment) rather than relying on the skill to request an anonymous token on your behalf. (3) Ask the publisher to clarify the metadata mismatch: SKILL.md lists a config path (~/.config/nemovideo/) but the registry metadata does not — confirm whether the skill will read that local folder. (4) If you need strong assurance, verify the domain (mega-api-prod.nemovideo.ai) and the service's legitimacy before sending sensitive footage. (5) If you are uncomfortable with automatic network token acquisition or with uploading files to an unknown third party, do not install/use the skill until those concerns are resolved.

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 pauses, 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.

Name of Video Editing — Edit and Export Finished Videos

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

Say you have a 2-minute unedited screen recording and want to trim the pauses, add transitions, and export a clean final cut — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

User prompts referencing name of video editing, 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 name-of-video-editing, 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 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

Common Workflows

Quick edit: Upload → "trim the pauses, add transitions, and export a clean final cut" → 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 pauses, add transitions, and export a clean final cut" — 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.