Clip Editor Free

Turn a 2-minute raw video clip from a phone into 1080p edited video clips just by typing what you need. Whether it's quickly trimming and editing short video...

Security Scan

The skill mostly matches its stated purpose (cloud video editing) but has a few inconsistencies and behaviors you should be aware of — it will auto-request/issue bearer tokens, persist session state, and the SKILL.md claims a config path not present in the registry metadata.

Purpose & Capability

The skill's name, description, and runtime instructions consistently describe an online AI video editing service using a single bearer token (NEMO_TOKEN) and clearly documented API endpoints. However, the SKILL.md frontmatter lists a required config path (~/.config/nemovideo/) while the registry metadata shows no required config paths — this mismatch is unexplained.

Instruction Scope

Instructions direct the agent to automatically connect on first open and, if no NEMO_TOKEN exists, call the anonymous-token endpoint to obtain a bearer token (100 free credits) and then create and persist a session_id. The skill also instructs not to display raw API responses or token values to the user, which reduces transparency about what credentials are created or stored. The runtime actions (uploads, SSE, polling render status) all route to the declared backend endpoints and are appropriate for editing, but the automatic network calls and hidden token handling are noteworthy privacy/consent concerns.

Install Mechanism

No install spec and no code files — instruction-only. Low install risk because nothing is downloaded or written by an installer. All execution is via runtime API calls described in SKILL.md.

Credentials

Only one credential is declared (NEMO_TOKEN) which aligns with the service. But the skill expects to obtain/store that token itself if missing and may persist session state; combined with the hidden-display instruction this raises proportionality concerns (automatic creation/storage of a bearer token without explicit user consent). The frontmatter's configPaths value (not declared in registry metadata) is an additional unexplained request for local config access.

Persistence & Privilege

always:false (normal). The skill will create and persist a session_id and may store the anonymous token (NEMO_TOKEN) for up to 7 days per the backend description; this is expected for a cloud session but means the skill acquires lasting credentials/access until they expire or are removed.

What to consider before installing

This skill appears to implement a legitimate cloud video-editing workflow, but proceed cautiously. Before installing or using it: 1) Understand that the skill will call an external backend (mega-api-prod.nemovideo.ai) and will automatically request and keep a bearer token (NEMO_TOKEN) if one isn’t present — this happens without explicit separate consent beyond opening the skill. 2) Be aware uploaded videos are sent to that remote service; don’t upload sensitive content unless you trust the provider and their privacy policy. 3) Note the SKILL.md frontmatter references a local config path (~/.config/nemovideo/) that the registry metadata does not — ask the author why the skill needs that path. 4) If you’re uncomfortable with automatic token creation/persistence, only use the skill with a disposable account/token or block it from making outbound network requests until you can review behavior. 5) Prefer skills with a known, verifiable source and a published privacy/security policy for handling user media.

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the AI clip editing.

Try saying:

• "edit a 2-minute raw video clip from a phone into a 1080p MP4"
• "trim the clip, remove silences, and add smooth transitions"
• "quickly trimming and editing short video clips without paid software for content 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.

Clip Editor Free — Edit and Export Video Clips

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

Say you have a 2-minute raw video clip from a phone and want to trim the clip, remove silences, and add smooth transitions — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

User prompts referencing clip editor 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.

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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: clip-editor-free
• 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.

Error Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

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.

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the clip, remove silences, and add smooth 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 clip, remove silences, and add smooth 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.