Video Editing Ai Software

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

Security Scan

The skill's instructions match a cloud video-editing service (requiring a NEMO_TOKEN and uploading files to a third-party API), but the package lacks a verifiable source/homepage and the SKILL.md and registry metadata disagree about config path requirements — worth caution before installing.

Purpose & Capability

The name/description (cloud video editing) aligns with the runtime instructions: it makes API calls, uploads video files, creates sessions, and requires a service token (NEMO_TOKEN). Requesting a service token for a remote video-rendering backend is coherent with the stated purpose.

Instruction Scope

Instructions focus on contacting the remote API, creating a session, uploading files, streaming server-sent events, and exporting results — all within the skill's remit. Two notable behaviors: (1) the skill instructs automatically connecting to the backend on first open (network activity may occur without explicit user action), and (2) it tells the agent to read this file's YAML frontmatter and to detect install paths to set attribution headers (requires filesystem access to the skill file/agent install location). These actions are explainable but worth surfacing to users.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest installation risk from this vector. Nothing is downloaded or written by an installer in the metadata provided.

Credentials

Declared primary credential (NEMO_TOKEN) is appropriate for a third-party API. However, SKILL.md frontmatter lists a configPaths requirement (~/.config/nemovideo/) while the registry metadata earlier reported no required config paths — this inconsistency is unexplained. Also, the skill will upload user video files to an external domain (mega-api-prod.nemovideo.ai), which has privacy implications; ensure the token and uploads are acceptable to you before use.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It only describes ephemeral session tokens and in-memory session IDs; no persistent installation or cross-skill config modifications are described.

What to consider before installing

This skill appears to be a cloud-based video editor that uploads your files to mega-api-prod.nemovideo.ai and uses a NEMO_TOKEN for authentication — that is consistent with its stated purpose, but exercise caution: (1) the package has no homepage or verifiable publisher listed — that's a trust signal to check; (2) SKILL.md and registry metadata disagree about required config paths (~/.config/nemovideo/ is mentioned in the file but not in registry fields) — ask the publisher which is correct; (3) the skill will automatically contact the backend on first use and can upload videos — do not upload sensitive or private footage until you confirm the service's privacy policy and ownership; (4) prefer creating or providing your own token rather than relying on the skill to auto-generate/store credentials if you have concerns about persistence; (5) if you still want to try it, test first with non-sensitive sample videos and verify returned download URLs and headers are what you expect. If you need higher assurance, request a reputable homepage, documentation, or publisher contact before installing.

Getting Started

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

Try saying:

• "edit a 3-minute unedited screen recording into a 1080p MP4"
• "cut the pauses, add transitions, and export as a clean 90-second clip"
• "automatically trimming and polishing raw footage for social media or presentations for content creators and marketers"

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 Editing AI Software — Edit and Export Polished 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 3-minute unedited screen recording and want to cut the pauses, add transitions, and export as a clean 90-second clip — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 2 minutes process significantly faster and give more accurate AI cuts.

Matching Input to Actions

User prompts referencing video editing ai software, 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-editing-ai-software
• 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 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 → "cut the pauses, add transitions, and export as a clean 90-second clip" → 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 "cut the pauses, add transitions, and export as a clean 90-second clip" — 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 best balance of quality and file size.