No Login Video Editor Ai

edit video clips into edited MP4 clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. casual creators and students use it for editing vid...

Security Scan

The skill's behavior mostly matches a cloud-based video editor, but there are inconsistencies (required env var vs. anonymous token flow, claimed config path access, unknown source) that warrant caution before installing.

Purpose & Capability

The skill claims to be a no-login video editor and its runtime instructions describe anonymous token generation and a fully cloud-hosted pipeline — which is coherent with the stated purpose. However the registry metadata declares NEMO_TOKEN as a required environment variable even though SKILL.md provides an explicit anonymous-token flow (UUID → POST → data.token) when no env var is present. That mismatch (required credential vs. documented optional flow) is an incoherence. The metadata also lists a config path (~/.config/nemovideo/) which isn't clearly necessary for the documented ephemeral session behavior.

Instruction Scope

SKILL.md directs the agent to contact a remote API, upload user-supplied video files or URLs, start render jobs, poll for status, and download generated MP4s — all consistent with a video editor. It instructs saving a session_id and not printing tokens or raw JSON. It asks the agent to detect install path / read the skill frontmatter for attribution headers; reading those local paths/files is narrowly scoped, but does require file-system reads (skill file and possibly install path detection). The instructions do not ask the agent to read unrelated files or environment variables beyond NEMO_TOKEN.

Install Mechanism

No install spec and no code files are present (instruction-only). This is the lowest-risk install model: nothing is downloaded or written by an installer as part of skill installation.

Credentials

The registry requires a single credential (NEMO_TOKEN) and declares it as the primaryEnv. That is reasonable for an API-driven editor — except SKILL.md documents how to obtain an anonymous token programmatically if NEMO_TOKEN is not set, meaning the env var is not strictly necessary. This registry-vs-runtime inconsistency could confuse users and automated policy checks. The metadata's request to access ~/.config/nemovideo/ is also disproportionate for a purely ephemeral session flow unless the skill intends to persist session state locally (which isn't clearly documented). No other unrelated secrets are requested.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It instructs saving a session_id and references a config path (~/.config/nemovideo/), implying it may persist session state locally — but it does not explicitly require writing system-wide settings or modifying other skills. Autonomous invocation is allowed (platform default).

What to consider before installing

This skill will upload any videos you give it to a third-party API (mega-api-prod.nemovideo.ai) and operate on cloud GPUs. Before installing: (1) be aware that uploaded media is sent off your device — don't send sensitive or private videos. (2) The registry claims NEMO_TOKEN is required but the skill can generate an anonymous token itself; that mismatch is odd and may be a packaging error. (3) The metadata claims access to ~/.config/nemovideo/ and the skill may persist session info locally — consider whether you’re comfortable with that. (4) The skill source and homepage are unknown; prefer skills from a known publisher or with a published homepage/privacy policy. If you proceed, monitor network activity, review what the service stores about your uploads (privacy/retention), and avoid providing any credentials unrelated to the video service.

Getting Started

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

Try saying:

• "edit a 2-minute screen recording or phone video into a 1080p MP4"
• "trim the clip, add transitions, and export without signing up"
• "editing videos instantly without creating an account for casual creators and students"

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.

No Login AI Video Editor — Edit and Export Videos Instantly

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

Say you have a 2-minute screen recording or phone video and want to trim the clip, add transitions, and export without signing up — the backend processes it in about 30-90 seconds and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster with no account required.

Matching Input to Actions

User prompts referencing no login video 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.

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: no-login-video-editor-ai
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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 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

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.

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 "trim the clip, add transitions, and export without signing up" — 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 all platforms and devices.

Common Workflows

Quick edit: Upload → "trim the clip, add transitions, and export without signing up" → Download MP4. Takes 30-90 seconds 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.