Video Montage Maker

create video clips into compiled montage video with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. social media creators use it for combining...

Security Scan

This is an instruction-only, cloud-backed video montage skill that is internally consistent with its stated purpose but you should verify and trust the external service before uploading videos or providing a token.

Purpose & Capability

The name/description (combine clips into a montage) aligns with the instructions (upload clips, create session, render/export via a cloud API). Requiring a single service token (NEMO_TOKEN) is expected for a cloud-rendering backend. Minor inconsistency: the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths; this is likely a metadata mismatch but not critical to functionality.

Instruction Scope

The SKILL.md stays within the video-montage domain: it instructs checking/obtaining a token, creating a session, uploading media, using SSE for edits, and polling export status. It does instruct automatic anonymous-token creation if NEMO_TOKEN is absent and to 'auto-detect' platform from the install path for an attribution header — that implies the agent may inspect its environment/install path. No instructions ask the agent to read unrelated files, system secrets, or transmit data to unrelated endpoints.

Install Mechanism

No install spec and no code files (instruction-only). This is the lowest-risk install model: nothing is written to disk by the skill itself.

Credentials

Only a single credential (NEMO_TOKEN) is requested, which is proportionate for a cloud rendering service. The skill will also attempt to obtain an anonymous token automatically if none exists — this creates credentials server-side and associates a generated client UUID. Consider that the token grants the backend access to uploaded media and job metadata. The frontmatter's config path requirement (in SKILL.md) is unclear and not reflected in registry metadata.

Persistence & Privilege

always:false and normal autonomous invocation are set. The skill does not request permanent system-wide privileges or modify other skills. It does persist session IDs/tokens for job management, which is expected for this workflow.

Assessment

This skill looks coherent for its stated purpose, but it routes your media and editing commands to a third-party backend (mega-api-prod.nemovideo.ai) and uses a bearer token (NEMO_TOKEN). Before installing or invoking: 1) Verify you trust the nemovideo.ai service and its privacy/storage policy — uploaded videos will be processed and may be retained per their policy. 2) If you don't already have a NEMO_TOKEN, the skill will request an anonymous token on your behalf (it generates a UUID and posts to their auth endpoint); be aware this creates an account-like record. 3) Avoid uploading sensitive content unless you confirm retention/processing rules. 4) Ask the publisher (or a registry maintainer) to clarify the configPath mention in the SKILL.md frontmatter and explain how X-Skill-Platform auto-detection works (it may require reading install paths). 5) Because this is instruction-only, no local code will be installed, but network activity to the listed endpoints is required. If any of these points are unacceptable, do not enable the skill or provide a permanent NEMO_TOKEN.

Getting Started

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

Try saying:

• "create five 10-second vacation clips into a 1080p MP4"
• "combine my clips into a 30-second montage with music and transitions"
• "combining multiple clips into a single edited montage video for social media creators"

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.

Video Montage Maker — Combine Clips into One Video

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

Say you have five 10-second vacation clips and want to combine my clips into a 30-second montage with music and transitions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: keep individual clips under 30 seconds for faster processing.

Matching Input to Actions

User prompts referencing video montage maker, 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	video-montage-maker
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 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 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "combine my clips into a 30-second montage with music and 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.

Common Workflows

Quick edit: Upload → "combine my clips into a 30-second montage with music and transitions" → Download MP4. Takes 1-2 minutes 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.