Youtube Video Editor Transitions

Skip the learning curve of professional editing software. Describe what you want — add smooth transitions between all clips and export for YouTube — and get...

Security Scan

The skill's declared purpose (cloud-based automatic transition editing) lines up with its instructions, but small inconsistencies in the metadata and token handling plus the fact it will upload user videos to an external service warrant caution.

Purpose & Capability

The skill's name/description, endpoints, and required NEMO_TOKEN are consistent with a cloud video-editing service. However, the metadata declares a required config path (~/.config/nemovideo/) and a required env var (NEMO_TOKEN) while the runtime instructions also include an anonymous-token flow to obtain a token automatically if NEMO_TOKEN is missing — that mismatch is inconsistent (either the token is required or the skill can obtain one itself).

Instruction Scope

SKILL.md explicitly instructs the agent to upload user media and to call specific nemovideo.ai API endpoints (session creation, SSE chat, upload, export, polling). That is coherent with the stated purpose, but it means user video/audio files and session metadata will be transmitted to a third-party backend. The instructions correctly limit actions to the service API and do not ask to read unrelated local files, though the frontmatter's configPaths suggests possible local config access (not explicitly used in the runtime steps).

Install Mechanism

This is instruction-only with no install spec or downloaded code. No install-time code is written to disk, which reduces supply-chain risk.

Credentials

Only NEMO_TOKEN is declared as required (primary credential), which is proportionate for a cloud API. The inconsistency is that the instructions provide an anonymous-token retrieval flow if NEMO_TOKEN is absent. The metadata also lists a config path (~/.config/nemovideo/) — it's unclear whether the skill will read/write files there. Require/env and metadata should be clarified before trusting credentials.

Persistence & Privilege

always is false and the skill makes no requests to change other skills or global agent settings. Autonomous invocation is allowed by default (normal), but the skill does not request elevated persistent privileges.

What to consider before installing

This skill will upload your video and audio files to mega-api-prod.nemovideo.ai and use/obtain a NEMO_TOKEN for API calls. Before installing: 1) Decide whether you’re comfortable sending your media to that external service (don’t use it for sensitive content you cannot share). 2) Ask the publisher to clarify why metadata lists ~/.config/nemovideo/ and why NEMO_TOKEN is declared required when the skill can obtain an anonymous token itself. 3) If you plan to provide a permanent NEMO_TOKEN, treat it like any API secret (use a least-privilege token, rotate it, and avoid embedding it in shared environments). 4) Because this is instruction-only with no code to audit, test with non-sensitive sample videos first and request the service's privacy/retention policy. If you need greater assurance, prefer a skill with a known publisher or open-source code you can review.

Getting Started

Send me your video clips and I'll handle the AI transition editing. Or just describe what you're after.

Try saying:

• "add a 3-minute YouTube vlog split into five clips into a 1080p MP4"
• "add smooth transitions between all clips and export for YouTube"
• "adding transitions between clips in YouTube videos for YouTubers"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

YouTube Video Editor Transitions — Add Transitions and Export Videos

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 a 3-minute YouTube vlog split into five clips, type "add smooth transitions between all clips and export for YouTube", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: keeping individual clips under 2 minutes speeds up transition rendering noticeably.

Matching Input to Actions

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

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

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

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.

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)

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 "add smooth transitions between all clips and export for YouTube" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, WebM for the smoothest experience.

Export as MP4 with H.264 codec for best YouTube upload compatibility.

Common Workflows

Quick edit: Upload → "add smooth transitions between all clips and export for YouTube" → 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.