Video Clip Maker Online Free

edit video clips into edited video clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. TikTok creators use it for trimming and assemblin...

Security Scan

The skill's declared purpose (cloud video editing) mostly matches the network calls and token usage in its instructions, but there are small inconsistencies and privacy-relevant behaviors (auto-generating/storing a token, hiding token values, and a conflicting config-path requirement) that warrant caution before installing.

Purpose & Capability

The skill's name and description align with the requests and APIs described: it needs a NEMO_TOKEN and talks to a nemovideo.ai rendering backend for uploads, SSE editing, and exports. That credential is proportionate to a cloud rendering service. However, the SKILL.md frontmatter lists a required config path (~/.config/nemovideo/) while the registry metadata says no config paths are required — an internal inconsistency about what the agent should access.

Instruction Scope

Runtime instructions tell the agent to automatically obtain an anonymous token (POST to /api/auth/anonymous-token), create and store sessions, upload user video files, and include specific attribution headers. They also instruct the agent to 'not display raw API responses or token values to the user' and to auto-connect on first open. While each step can be legitimate for a cloud editor, the combination of (a) automatic token generation/store and (b) explicit instruction to hide token/API responses increases the risk that sensitive values could be handled without user-visible auditing. The instructions also refer to auto-detecting the install path and the ~/.config/nemovideo/ path, which implies filesystem access beyond the immediate task.

Install Mechanism

No install spec and no code files — instruction-only skill. This is lower risk because nothing gets written to disk by an installer, but it also means there is no local code to audit; behavior is defined entirely by the SKILL.md instructions.

Credentials

Only a single primary credential (NEMO_TOKEN) is required, which is appropriate for a third-party rendering service. However, the frontmatter's declared config path (~/.config/nemovideo/) suggests the agent may try to read local configuration (e.g., existing tokens) — this should be justified to the user. Also, the skill can generate an anonymous token server-side if none is present, meaning it can obtain credentials on behalf of the user.

Persistence & Privilege

always is false and the skill does not request permanent platform-level presence. Autonomous invocation is allowed (the platform default) but not combined with other strong privileges. The skill does instruct storing session_id and tokens for the session, which is normal for a remote service workflow.

What to consider before installing

This skill appears to do what it says (cloud video editing) but I flagged it as suspicious because: (1) the SKILL.md instructs the agent to automatically obtain and store a token from https://mega-api-prod.nemovideo.ai and to hide token/API responses from the user, and (2) the frontmatter asks the agent to access ~/.config/nemovideo/ though registry metadata lists no config paths — an internal inconsistency. Before installing, consider: - Do you trust nemovideo.ai as a destination for uploading potentially-sensitive videos? All media will be sent to that backend. - The skill will either use your NEMO_TOKEN or create one automatically; ask for explicit consent before any automatic token creation or upload. - Because this is instruction-only (no code to inspect) and the source/homepage is unknown, you have limited auditability. Prefer skills from known publishers or with a homepage/repo you can review. - If you still want to try it, require the skill to prompt you before creating tokens or uploading files, and avoid uploading private/confidential footage. - To reduce risk: manually obtain and set a dedicated NEMO_TOKEN with minimal scope, or test the endpoints outside the agent first to verify behavior. If you can get the publisher, homepage, or source repo, share it and I can reassess with higher confidence.

Getting Started

Ready when you are. Drop your video clips here or describe what you want to make.

Try saying:

• "edit a 2-minute raw phone recording into a 1080p MP4"
• "trim the clip, add transitions, and export as a short video"
• "trimming and assembling short clips from raw footage for TikTok creators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Video Clip Maker Online Free — Edit and Export Video Clips

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

A quick example: upload a 2-minute raw phone recording, type "trim the clip, add transitions, and export as a short video", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process noticeably faster.

Matching Input to Actions

User prompts referencing video clip maker online free, 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.

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

Header	Value
X-Skill-Source	video-clip-maker-online-free
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.

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.

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.

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

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)

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 → "trim the clip, add transitions, and export as a short video" → Download MP4. Takes 30-60 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.

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 as a short 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.