Video Editing With Best

Cloud-based video-editing-with-best tool that handles editing raw footage into professional-looking videos quickly. Upload MP4, MOV, AVI, WebM files (up to 5...

Security Scan

The skill's runtime instructions match a cloud video-editing tool and only ask for a single service token, but there are metadata inconsistencies and provenance gaps (no homepage/unknown source) you should understand before uploading video or granting persistent config access.

Purpose & Capability

The skill's endpoints, upload flow, SSE stream handling, and the single NEMO_TOKEN credential are coherent with a cloud video editing service. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier reported no required config paths — this mismatch is unexplained. Also the package has no homepage and an unknown owner, which reduces confidence in provenance though does not by itself make the capability incoherent.

Instruction Scope

Instructions are narrowly focused on authenticating, creating a session, uploading user-provided media, streaming edits via SSE, and polling for exports — all expected for this purpose. They do include guidance to save a session_id and to auto-detect the platform from the agent's install path (for X-Skill-Platform header), which implies reading/writing local config or install path metadata; the SKILL.md doesn't explicitly constrain where session state should be stored. There are no directives to read unrelated system files or other credentials.

Install Mechanism

This is an instruction-only skill with no install spec and no code files — lowest install risk. Nothing is downloaded or written by an installer according to the provided registry data.

Credentials

The single required environment variable (NEMO_TOKEN) is appropriate for a service that uses bearer tokens. The skill also documents an anonymous-token endpoint to obtain a short-lived token. The metadata/instructions implying a config path (~/.config/nemovideo/) suggests the skill may read/write local configuration, which is broader access than the registry summary showed; that mismatch should be resolved before trusting persistent credentials in that path.

Persistence & Privilege

The skill is not marked 'always' and does not request special platform privileges. It does expect to persist session state (session_id) and potentially store tokens in a config location (per frontmatter). There's no indication it touches other skills' configurations. Persisting session or token data to ~/.config/nemovideo/ (implied) increases the blast radius if the config is global or not clearly scoped.

What to consider before installing

This skill appears to implement a legitimate cloud video-editing flow, but proceed cautiously because the package has no homepage and an unknown owner, and the SKILL.md references a local config path (~/.config/nemovideo/) that conflicts with the registry metadata. Before installing or using: 1) Verify the service domain (mega-api-prod.nemovideo.ai) and look for an official site/privacy policy; 2) Avoid uploading sensitive or private footage until you confirm the service's privacy/retention policy; 3) Prefer generating ephemeral/anonymous tokens rather than storing long-lived credentials in your environment; 4) Inspect or monitor the ~/.config/nemovideo/ location if the agent writes there (or deny writes) and clear any stored tokens after use; 5) If you need higher assurance, ask the publisher for provenance (homepage, contact, open-source repo) or choose a well-known vendor instead.

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"

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.

Video Editing With Best — Edit and Export Polished Videos

Drop your raw video footage in the chat and tell me what you need. I'll handle the AI-powered video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 3-minute unedited screen recording, ask for trim the pauses, add transitions, and enhance the audio quality, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 2 minutes process significantly faster and yield cleaner AI edits.

Matching Input to Actions

User prompts referencing video editing with best, 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-best
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 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)

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the 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

Common Workflows

Quick edit: Upload → "trim the pauses, add transitions, and enhance the audio quality" → 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 enhance the audio quality" — 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.