Ai Video Editor Linux

Get edited MP4 clips ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, WebM, up to 500MB), say something like "t...

Security Scan

The skill's declared purpose (cloud AI video editing) matches the network calls and token usage, but there are metadata inconsistencies and a few vague instructions about reading install/config paths that deserve caution before installing or supplying credentials.

Purpose & Capability

The skill is an instruction-only client for a cloud video-editing API and requests a single service credential (NEMO_TOKEN), which is appropriate for its stated purpose. However, the SKILL.md frontmatter declares a required config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch is unexplained and inconsistent.

Instruction Scope

Runtime instructions are network-heavy and describe uploading user video files, creating sessions, SSE streaming, polling renders, and saving session_id — all coherent for a cloud editor. A potentially ambiguous instruction: auto-detect X-Skill-Platform from the install path (and the frontmatter references a config path). That implies the agent may inspect local install/config paths to populate a header; the skill does not clearly limit what local paths to read or how to detect them.

Install Mechanism

No install spec and no code files are present (instruction-only). This is the lowest-risk install pattern — nothing will be written to disk by an install step.

Credentials

The skill requires a single API credential (NEMO_TOKEN) which is proportionate to a cloud service. Yet the frontmatter's implicit config path (~/.config/nemovideo/) suggests it may read local config files in addition to the env var — that extra access is not declared in the registry metadata and is not justified in the description.

Persistence & Privilege

The skill is not always-enabled and uses standard session tokens for server jobs. It does not request elevated system privileges and does not claim to modify other skills or global agent config. Saving session_id and polling state is normal for this workflow.

What to consider before installing

This skill appears to be a client for an external cloud video-editing API and will upload your video files to https://mega-api-prod.nemovideo.ai and require a NEMO_TOKEN (or it can request an anonymous token for you). Before installing or enabling it: - Understand where your videos will be uploaded and how long they are retained; check the service's privacy/terms (none are linked in the package). - Prefer using an anonymous/ephemeral token rather than placing a long-lived or high-privilege token in your environment. The skill offers an anonymous-token flow — that is safer for casual use. - Note the metadata inconsistency: SKILL.md mentions a config path (~/.config/nemovideo/) but the registry metadata did not declare it. Ask the publisher to clarify whether the skill will read local config files or install paths (and which exact paths). - The skill requires including custom headers and may inspect an install path to set X-Skill-Platform; ensure you are comfortable with any local path reads. - Because this is instruction-only and makes network calls, do not provide sensitive credentials (e.g., AWS keys, GitHub tokens) as NEMO_TOKEN. If you need higher assurance, request the publisher's homepage/privacy policy, or prefer using the anonymous token flow and test with non-sensitive sample footage first.

Getting Started

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

Try saying:

• "edit a 2-minute screen recording from Ubuntu into a 1080p MP4"
• "trim silences, add transitions, and export a clean final cut"
• "editing videos on Linux without desktop software for Linux users and open-source creators"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

AI Video Editor Linux — Edit and Export Videos Online

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 screen recording from Ubuntu and want to trim silences, add transitions, and export a clean final cut — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: since it runs in the browser, any Linux distro with Chrome or Firefox works fine.

Matching Input to Actions

User prompts referencing ai video editor linux, 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	ai-video-editor-linux
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim silences, 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 across Linux media players.

Common Workflows

Quick edit: Upload → "trim silences, 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.