Unlimited Editor Ai

Cloud-based unlimited-editor-ai tool that handles editing multiple videos without credit or usage limits. Upload MP4, MOV, AVI, WebM files (up to 500MB), des...

Security Scan

The skill's requirements and runtime instructions align with a cloud video-editing service (it asks only for a service token and describes API calls for uploads, sessions, and exports), but the backend is external and source is unknown so exercise caution before sending sensitive videos or credentials.

Purpose & Capability

Name/description match the declared runtime actions: uploading videos, creating sessions, SSE editing, and exporting. Requesting a NEMO_TOKEN and calling a nemo video API is coherent for a cloud editor.

Instruction Scope

SKILL.md instructs the agent to obtain/use a bearer token, create sessions, upload files, and poll renders — all expected. Minor inconsistency: frontmatter declares a config path (~/.config/nemovideo/) but the runtime steps do not describe reading that path; confirm whether the agent will inspect local files before use.

Install Mechanism

Instruction-only skill with no install spec or downloaded code; this has a low local disk/write footprint. Network calls to an external API are required for functionality.

Credentials

Only a single credential (NEMO_TOKEN) is required and that matches the described API usage. The extra metadata entry for a config path suggests potential local config access that is not otherwise justified by the instructions—verify whether your agent will expose that path or any local files.

Persistence & Privilege

Skill is not always-enabled and does not request elevated platform privileges or modify other skills. It will perform autonomous network actions per normal skill behavior; no persistent installation steps are declared.

Assessment

This skill appears internally consistent for a cloud video editor: it needs a NEMO_TOKEN and will upload your footage to an external service (https://mega-api-prod.nemovideo.ai) to do processing. Before installing or using it, consider: (1) Do you trust the external domain and its privacy/security practices? (2) Avoid uploading sensitive or private video content unless you confirm retention and sharing policies. (3) Confirm whether your agent runtime will read the declared config path (~/.config/nemovideo/) or any local files — if so, ensure no secrets are stored there. (4) If you don’t already have a NEMO_TOKEN, the skill will request an anonymous token from the remote API automatically; be aware that this grants the service temporary access tied to that token. If you need higher assurance, request the upstream privacy/security docs or test with non-sensitive sample videos first.

Getting Started

Send me your raw video footage and I'll handle the unlimited AI editing. Or just describe what you're after.

Try saying:

• "edit a 3-minute unedited vlog recording into a 1080p MP4"
• "cut out silences, add transitions, and export a clean final video"
• "editing multiple videos without credit or usage limits for content creators"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Unlimited Editor AI — Edit and Export Videos Without Limits

Send me your raw video footage and describe the result you want. The unlimited AI editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 3-minute unedited vlog recording, type "cut out silences, add transitions, and export a clean final video", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips process faster — split long videos before uploading for quicker results.

Matching Input to Actions

User prompts referencing unlimited editor ai, 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.

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

Header	Value
X-Skill-Source	unlimited-editor-ai
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut out silences, add transitions, and export a clean final video" — 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 → "cut out silences, add transitions, and export a clean final video" → 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.