Ai Video Editor No Login

Turn a 2-minute screen recording or phone video into 1080p edited MP4 files just by typing what you need. Whether it's editing videos instantly without creat...

Security Scan

The skill's declared need for a single service token is plausible for a cloud video render API, but the SKILL.md and manifest contain inconsistent requirements (an extra configPath in the frontmatter) and the skill instructs the agent to obtain tokens and make many external API calls — things to double-check before installing.

Purpose & Capability

The skill's stated purpose (cloud video editing) aligns with requiring a service token (NEMO_TOKEN) and calls to a nemovideo.ai API. However the SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) even though the registry metadata shows no required config paths — this inconsistency is unexplained and could cause the agent to read files it doesn't need.

Instruction Scope

The instructions direct the agent to: generate anonymous tokens, POST/GET to multiple endpoints, upload user files, stream SSE, poll for renders, and save session IDs. These actions are consistent with the editor purpose, but the skill also requires adding custom attribution headers and may access a local config path per frontmatter. The combination of network token creation, file uploads, and implicit local config access increases the attack surface and warrants attention.

Install Mechanism

No install spec and no code files — instruction-only. This minimizes on-disk changes and installer risk.

Credentials

Only one declared credential (NEMO_TOKEN), which is appropriate for a hosted API. But the frontmatter's implied config path (~/.config/nemovideo/) would permit reading local config files if used, and the SKILL.md instructs the agent to create or use tokens — verify why both env var and config path access are present. Ensure the token's scope/privileges are minimal.

Persistence & Privilege

The skill is not always-enabled and does not request system-wide persistence. It asks to save a session_id (presumably in memory or per-session) but does not request elevated privileges or to modify other skills/configs.

What to consider before installing

This skill appears to do what it says (cloud video editing) and asks only for a single service token, but there are two things to check before installing: 1) The SKILL.md frontmatter references a local config path (~/.config/nemovideo/) that the registry metadata did not — confirm whether the skill will read files from your home directory and why. 2) The agent is instructed to create/refresh anonymous tokens by calling an external endpoint and will upload your video files to mega-api-prod.nemovideo.ai — only proceed if you trust that endpoint and its privacy/retention policies. If you decide to try it, prefer providing an ephemeral or low-privilege token (or rely on the anonymous-token flow rather than placing a long-lived token in your environment), restrict the agent's network access if possible, and monitor uploads and token usage. Because this is an instruction-only skill with no code to inspect, manual review of the service's privacy/security practices is recommended.

Getting Started

Share your raw video clips and I'll get started on AI video editing. Or just tell me what you're thinking.

Try saying:

• "edit my raw video clips"
• "export 1080p MP4"
• "trim the silent parts, add transitions,"

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 Login — Edit and Export Videos Instantly

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

Here's a typical use: you send a a 2-minute screen recording or phone video, ask for trim the silent parts, add transitions, and export a clean final cut, 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 60 seconds process the fastest with no account needed.

Matching Input to Actions

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

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

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)

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the silent parts, 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 platforms and devices.

Common Workflows

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