Editor Transitions

Turn three 30-second clips from a vlog shoot into 1080p transition-edited clips just by typing what you need. Whether it's adding seamless transitions betwee...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud video-editing service: it uploads user media to mega-api-prod.nemovideo.ai and uses a NEMO_TOKEN (which it can obtain anonymously) to run edits, so behavior matches its description but you should be aware your media and a short-lived token are sent to an external service.

Purpose & Capability

The name/description describe cloud-based transition editing and the skill only requires a service token (NEMO_TOKEN) and API calls to mega-api-prod.nemovideo.ai — that is proportionate. Minor inconsistency: the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) and runtime code that reads the skill file/frontmatter to populate attribution headers, whereas the registry metadata listed no required config paths. This is a small metadata mismatch, not evidence of malicious intent.

Instruction Scope

Runtime instructions perform network operations (anonymous-token request, session creation, SSE streaming, file uploads, export rendering) and will upload user media to the external backend — that is expected for a cloud editor but is the primary privacy/security surface. The skill also instructs generating/storing a session_id and token and to read the skill's YAML frontmatter and detect install path to fill attribution headers. It does not ask for unrelated local files or other credentials, but you should expect your video/audio files to be transmitted to the third-party endpoint.

Install Mechanism

Instruction-only skill with no install spec and no code files, so nothing is written to disk during installation. This minimizes attack surface from install-time downloads.

Credentials

The only declared credential is NEMO_TOKEN (primaryEnv), which is appropriate for calling the described API. The skill auto-obtains an anonymous token if none is provided (by POSTing to the service), which is reasonable but means the skill will make outbound network requests and persist a token/session for subsequent calls. The frontmatter's mention of a config path and the runtime need to inspect install path/frontmatter to populate headers are not documented in registry metadata — a minor mismatch that requires filesystem read access to the skill files/install path.

Persistence & Privilege

The skill is not forced-always; it is user-invocable and allowed to run autonomously (default). It does instruct storing session_id and token for the session lifecycle, but it does not request system-wide persistent privileges or alteration of other skills/configs.

Assessment

This skill appears to do what it says: it uploads your clips to mega-api-prod.nemovideo.ai and uses a NEMO_TOKEN to run cloud editing. Before installing or using it, consider: (1) Privacy — your raw video/audio will be uploaded to a third-party service; don't send confidential or sensitive footage. (2) Tokens — the skill can auto-create a short-lived anonymous token if NEMO_TOKEN is not present; if you provide your own NEMO_TOKEN, it will be used for all API calls. (3) Metadata mismatch — the SKILL.md mentions reading the skill file/frontmatter and a config path (~/.config/nemovideo/), though the registry metadata did not declare that; expect the skill to read its own files/install-path to build attribution headers. (4) Trust the domain — confirm you are willing to send media to https://mega-api-prod.nemovideo.ai and consider checking the service’s privacy/terms. Because there is no install-time code download, the main risk is data exposure to the remote service rather than local code execution.

Getting Started

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

Try saying:

• "add three 30-second clips from a vlog shoot into a 1080p MP4"
• "add smooth transitions between all clips and match them to the beat"
• "adding seamless transitions between video clips for YouTubers and 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.

Editor Transitions — Add Transitions Between Video Clips

Drop your video clips in the chat and tell me what you need. I'll handle the AI transition editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a three 30-second clips from a vlog shoot, ask for add smooth transitions between all clips and match them to the beat, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips with clear cut points produce cleaner AI-detected transitions.

Matching Input to Actions

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

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: editor-transitions
• 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

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)

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.

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.