Video Editing With Unlimited

Cloud-based video-editing-with-unlimited tool that handles editing and exporting videos without render or export limits. Upload MP4, MOV, AVI, WebM files (up...

Security Scan

The skill mostly behaves like a cloud video-editing integration (it only needs a NEMO_TOKEN), but there are inconsistencies in its metadata and a few instruction items that ask the agent to inspect or persist local environment details that aren't justified by the description.

Purpose & Capability

The stated purpose (cloud video editing/export) matches the API endpoints and the single credential (NEMO_TOKEN). This credential is proportionate. However, the SKILL.md's YAML metadata lists a config path (~/.config/nemovideo/) that the registry metadata did not declare — a mismatch that suggests either outdated registry metadata or an instruction to touch a local config directory that wasn't advertised.

Instruction Scope

Instructions are primarily API calls to nemovideo.ai and are consistent with a cloud editing workflow. Concerns: (1) the skill tells the agent to detect install path (~/.clawhub/, ~/.cursor/skills/) to set an X-Skill-Platform header — this requires probing the filesystem and is not strictly needed for editing. (2) The YAML metadata in SKILL.md lists a config path, implying persistence to ~/.config/nemovideo/ (the registry top-level said none). The instructions also instruct saving session_id and tokens but do not specify where — raising the risk of local persistence without clear user consent.

Install Mechanism

No install spec and no code files; the skill is instruction-only. That minimizes installation risk because nothing is written to disk by an installer. The main runtime actions are outgoing HTTPS calls to the service domain.

Credentials

Only one env var is required (NEMO_TOKEN), which is appropriate for an API-backed video service. However, the SKILL.md both accepts an existing NEMO_TOKEN and documents obtaining an anonymous token via the API; the metadata's declared config path (~/.config/nemovideo/) implies the skill may persist tokens or session state locally — this was not declared in the registry summary and should be clarified.

Persistence & Privilege

The skill does not request always:true and uses normal autonomous invocation. The potential concern is local persistence: SKILL.md metadata and instructions imply saving session tokens/session IDs (and the config path in YAML) but the registry listing did not advertise any config-path requirement. Probing install paths to set headers is another form of local inspection. Combined, these indicate the skill may read or write local config state beyond what was declared.

What to consider before installing

This skill appears to be a legitimate cloud video-editing integration, but there are a few inconsistencies you should confirm before installing or providing credentials: 1) Confirm where the skill will store session tokens or anonymous tokens (it references ~/.config/nemovideo/ in its SKILL.md but the registry did not). If it will write to that path, ask for specifics and whether it respects permissions. 2) Ask why the skill needs to probe install paths (~/.clawhub/, ~/.cursor/skills/) to set an attribution header — this requires filesystem access and seems unnecessary. 3) Only provide a NEMO_TOKEN you control and can revoke; avoid using long-lived system credentials. 4) Verify the service domain (mega-api-prod.nemovideo.ai) and request a privacy/retention policy for uploaded videos. If the vendor/source cannot explain the config-path discrepancy and token persistence behavior, treat the skill with caution or avoid installing.

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the unlimited AI editing.

Try saying:

• "edit a 3-minute YouTube vlog recording into a 1080p MP4"
• "trim silences, add transitions, and export as many versions as I need"
• "editing and exporting videos without render or export limits for content 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.

Video Editing With Unlimited — Edit and Export Videos Without Limits

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

Here's a typical use: you send a a 3-minute YouTube vlog recording, ask for trim silences, add transitions, and export as many versions as I need, 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 process faster, so split long videos before uploading for quicker results.

Matching Input to Actions

User prompts referencing video editing with unlimited, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-editing-with-unlimited, 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.

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)

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 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 as many versions as I need" — 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 platforms and devices.

Common Workflows

Quick edit: Upload → "trim silences, add transitions, and export as many versions as I need" → 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.