Video Editor Transitions

Get transition-edited clips ready to post, without touching a single slider. Upload your video clips (MP4, MOV, AVI, WebM, up to 500MB), say something like "...

Security Scan

The skill's declared behavior (remote video editing via a Nemo API) mostly matches its runtime instructions, but there are discrepancies (a declared config path in the SKILL.md frontmatter that isn't reflected in the registry metadata), no identified source/homepage, and instructions that hide technical details from the chat — worth investigating before installing.

Purpose & Capability

Name/description match the actions in SKILL.md: uploads, session creation, SSE streaming, render/export. Requesting a service token (NEMO_TOKEN) is consistent with calling an external video-rendering API. However the SKILL.md frontmatter claims it requires a config path (~/.config/nemovideo/) while the registry metadata lists no config paths — this inconsistency is unexplained and could indicate the skill expects to read user config files.

Instruction Scope

Instructions explicitly instruct the agent to create sessions, upload user video files, stream SSE, poll render endpoints, and (if no env token) create an anonymous token by POSTing to the external API. They also say to 'keep the technical details out of the chat' which means the agent will perform network actions without surfacing technical request/response details to users. The SKILL.md asks to auto-detect X-Skill-Platform 'from install path' (implies reading agent/install path) and references a config path in metadata — both expand the agent's scope beyond simply sending uploaded videos to an API.

Install Mechanism

No install spec and no code files — instruction-only skill, so nothing is written to disk by an installer. This is the lowest install risk.

Credentials

Only one environment credential (NEMO_TOKEN) is declared, which is appropriate for an external API. However SKILL.md also documents generating and using an anonymous token if NEMO_TOKEN is absent, and the frontmatter mentions a config path that could contain credentials — that mismatch should be clarified. Don't supply a high-privilege personal token unless you trust the backend.

Persistence & Privilege

always is false and there's no install-time persistence described. The skill does create short-lived sessions on the remote service but does not request permanent agent presence or modify other skills.

What to consider before installing

This skill appears to do what it says: upload your clips to a remote Nemo rendering service and return edited exports. Before installing or using it: 1) Note there is no source repository or homepage — verify you trust https://mega-api-prod.nemovideo.ai and the skill author. 2) Clarify the config path discrepancy: the SKILL.md frontmatter lists ~/.config/nemovideo/ but the registry metadata did not — ask if the skill will read that directory (it could contain other tokens). 3) Avoid supplying a personal/high-privilege NEMO_TOKEN unless you trust the service; prefer the anonymous token flow if you only need free/temporary usage. 4) Be aware uploads are sent to a third-party server (the service will receive your video content). If privacy or NDAs apply to your videos, do not upload them. 5) If you want to proceed, request the author/source URL and a privacy/data-retention policy and ask them to explain why the skill hides technical request details from the chat and whether the skill will read any agent filesystem paths.

Getting Started

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

Try saying:

• "add my video clips"
• "export 1080p MP4"
• "add smooth transitions between all clips"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Video Editor Transitions — Add Transitions Between Video Clips

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

A quick example: upload three 30-second clips from a travel vlog, type "add smooth transitions between all clips and match them to the beat", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: shorter clips with clear cut points produce cleaner transitions.

Matching Input to Actions

User prompts referencing video editor transitions, 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 requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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

Header	Value
X-Skill-Source	video-editor-transitions
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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.

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 "add smooth transitions between all clips and match them to the beat" — 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.

Common Workflows

Quick edit: Upload → "add smooth transitions between all clips and match them to the beat" → 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.