Video Clip Maker Online

Turn a 3-minute smartphone recording into 1080p edited video clips just by typing what you need. Whether it's trimming and assembling short clips from longer...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud video-editing integration — it only needs a NEMO_TOKEN and interacts with nemovideo.ai — with a few minor metadata/behavior notes to be aware of.

Purpose & Capability

The name/description (cloud video clip editing) align with the declared requirement for a NEMO_TOKEN and the API endpoints in SKILL.md. Minor inconsistency: the SKILL.md frontmatter declares a configPaths entry (~/.config/nemovideo/) that the registry metadata did not list as a required path; this is likely harmless but is an unexplained metadata mismatch.

Instruction Scope

Runtime instructions stay within the stated purpose (create sessions, upload video, handle SSE, run exports). They do instruct the agent to read this file's YAML frontmatter and to detect install paths (~/.clawhub/, ~/.cursor/skills/) in order to set attribution headers; that requires filesystem access beyond purely sending files and may leak platform info. Instructions also say to save session_id (unspecified storage scope). No instructions request unrelated system secrets or files.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk (nothing is downloaded or written by an installer).

Credentials

Only a single credential (NEMO_TOKEN) is required, which is proportional to a cloud API client. The skill's requirement to attach attribution headers on every API call (including platform and version derived from filesystem/frontmatter) can leak environment/skill metadata to the remote service; that's a privacy consideration but not a direct coherence problem.

Persistence & Privilege

always:false and normal autonomous invocation are used. The skill instructs saving session_id but does not request persistent system-wide privileges or modify other skills' configs. No evidence it requires elevated or permanent presence.

Assessment

This skill appears to be what it says: a cloud video-editing client for nemovideo.ai that needs a NEMO_TOKEN. Before installing, consider: (1) Do you trust https://mega-api-prod.nemovideo.ai to receive your videos and metadata? API calls (including attribution headers) will be sent there. (2) If you already have a NEMO_TOKEN in your environment, the skill will use it — prefer using a token scoped for this service rather than a shared secret. (3) The skill will attempt to read its frontmatter and check common skill-install paths to populate X-Skill-Platform — this requires filesystem access and may reveal platform/skill metadata; if you do not want that, ask whether the skill can rely solely on embedded metadata instead. (4) The anonymous token flow is described (short-lived tokens with limited credits) if you prefer not to supply a personal token. If you want greater assurance, ask the publisher for a privacy/security policy or test with a disposable account/token first.

Getting Started

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

Try saying:

• "turn my raw video footage"
• "export 1080p MP4"
• "trim the footage into a 30-second"

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.

Video Clip Maker Online — Trim and Export Video Clips

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

Say you have a 3-minute smartphone recording and want to trim the footage into a 30-second clip and add transitions — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter source clips process faster and give more precise cut results.

Matching Input to Actions

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

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

• X-Skill-Source: video-clip-maker-online
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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)

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.

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 footage into a 30-second clip and add transitions" — 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 footage into a 30-second clip and add transitions" → 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.