Ai Video Editor No Limit

Skip the learning curve of professional editing software. Describe what you want — cut dead air, add transitions, and export with no watermark — and get unli...

Security Scan

The skill appears to implement a cloud-based video editor (uploads to nemovideo.ai) which matches its name, but there are metadata inconsistencies, no verifiable source/homepage, and privacy/locals-file access concerns that you should understand before installing.

Purpose & Capability

The skill's stated purpose (cloud AI video editing) matches the runtime instructions (uploading footage, creating sessions, rendering/exporting). Required credential (NEMO_TOKEN) is consistent with calling the service. However, SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this mismatch is unexplained and may imply the skill expects local config access that wasn't declared.

Instruction Scope

Instructions direct the agent to upload user video files and send them to https://mega-api-prod.nemovideo.ai and to obtain/store session tokens. Uploading user content to a third-party service is expected for this functionality but is a privacy/data-exfiltration risk. The instructions also mention detecting install path to populate an attribution header and the frontmatter references a local config path — both imply the agent may read filesystem locations (e.g., ~/.clawhub, ~/.cursor, ~/.config/nemovideo/) which is broader scope than simply accepting a file to upload.

Install Mechanism

This is an instruction-only skill with no install spec and no code files; nothing is written to disk by an installer. That minimizes install-time risk, but it also means the scanner had no code to analyze.

Credentials

Only one credential is declared (NEMO_TOKEN) which is proportionate for a cloud API. The skill also documents generating an anonymous token if none is present. The concern is the undeclared config path in the SKILL.md frontmatter which could expose additional local credentials/config if used; registry metadata did not declare that path.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It expects to keep a session_id for active work, which is normal. No install or persistent modifications are specified.

What to consider before installing

This skill will upload whatever videos you give it to a third-party domain (mega-api-prod.nemovideo.ai). That is necessary for a cloud editor but is a privacy risk—do not upload sensitive footage until you verify the provider. There is no homepage or verifiable source listed, and the SKILL.md includes a local config path (~/.config/nemovideo/) that the registry metadata did not declare; that mismatch suggests the skill might read local config files. Before installing, verify the provider and domain independently (search for nemovideo.ai, the API host, and the owner), avoid putting existing secret tokens into the skill unless you trust the service, and prefer skills from a documented homepage or known publisher. If you proceed, consider using an anonymous/limited token (as the instructions allow) and do not give the skill high-value credentials. If you want higher assurance, ask the publisher for a homepage, source repo, or clarification about which local paths the skill will read.

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 10-minute unedited screen recording into a 1080p MP4"
• "cut dead air, add transitions, and export with no watermark"
• "editing and exporting videos without usage caps or watermarks for content creators and marketers"

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 No Limit — Edit and Export Videos Without Restrictions

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

Say you have a 10-minute unedited screen recording and want to cut dead air, add transitions, and export with no watermark — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: breaking long videos into segments before uploading can speed up processing.

Matching Input to Actions

User prompts referencing ai video editor no limit, 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 ai-video-editor-no-limit, 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).

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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 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 → "cut dead air, add transitions, and export with no watermark" → 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 "cut dead air, add transitions, and export with no watermark" — 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.