Video Editing With Ai App

Skip the learning curve of professional editing software. Describe what you want — trim the pauses, add transitions, and overlay background music — and get e...

Security Scan

The skill's requests and runtime instructions are coherent with a cloud-based AI video editing service; nothing in the package tries to access unrelated secrets or install arbitrary code, but there are a few small inconsistencies and privacy considerations you should review before use.

Purpose & Capability

The skill is declared as an instruction-only video-editing integration and requests a single credential, NEMO_TOKEN, which matches the stated backend API. One minor inconsistency: the registry metadata reported no required config paths, but the SKILL.md frontmatter includes a config path (~/.config/nemovideo/). This is plausible (local config storage) but the mismatch should be clarified.

Instruction Scope

The instructions limit actions to establishing a session, uploading videos, streaming SSE edits, polling export status, and returning download URLs. They do instruct the agent to generate an anonymous token via POST to https://mega-api-prod.nemovideo.ai if NEMO_TOKEN is missing, and to 'auto-detect' platform from the install path (which implies reading the agent's install path). No instructions request unrelated files, other credentials, or external exfiltration, but the platform-detection and optional config path access are vaguely specified and worth confirming.

Install Mechanism

No install spec or code files are included (instruction-only). No downloads or archives are written to disk by the skill itself, minimizing install-time risk.

Credentials

Only one environment variable is required (NEMO_TOKEN), which is proportional to a remote video editing API. The SKILL.md also documents an anonymous-token flow if no token is provided; no additional unrelated secrets or broad system credentials are requested.

Persistence & Privilege

The skill is not force-included (always: false) and uses normal autonomous invocation settings. It does not request system-wide configuration changes or privileges beyond using the declared token and optional config directory.

Assessment

This skill appears to do what it says: connect to a remote nemo video service, accept uploads, and return edited videos. Before installing or using it, consider: (1) Privacy: uploads go to mega-api-prod.nemovideo.ai — do not upload sensitive footage unless you trust their terms. (2) Credentials: NEMO_TOKEN is required; if absent the skill will request an anonymous token from the service (it will generate a client UUID). Decide whether to provide your own token or rely on the anonymous flow. (3) Clarify the config-path mismatch: SKILL.md references ~/.config/nemovideo/ but the registry showed no required config paths — confirm whether the skill will read/write that directory. (4) Attribution headers: the skill requires custom X-Skill-* headers on every request (used by the service); this is not inherently malicious but it does mean the service will see which skill/version/platform made requests. If any of these points worry you, ask the skill author for clarifications or avoid uploading private content.

Getting Started

Share your raw video footage and I'll get started on AI-powered 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.

Video Editing with AI App — Edit and Export Polished Videos

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

Say you have a 2-minute smartphone recording and want to trim the pauses, add transitions, and overlay background music — 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 video editing with ai app, 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 calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

Header	Value
X-Skill-Source	video-editing-with-ai-app
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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)

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

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.

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 overlay background music" → 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 overlay background music" — 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 all platforms.