Video Maker Automatic

Skip the learning curve of professional editing software. Describe what you want — automatically edit my footage into a finished video with transitions and m...

Security Scan

The skill's instructions mostly match an auto-video-editing tool, but there are small inconsistencies and a couple of behaviors (automatic token issuance, reading install/config paths and frontmatter) that deserve closer scrutiny before install.

Purpose & Capability

The declared purpose (auto-edit and export videos) aligns with the network endpoints, upload, and export flows in SKILL.md. Required credential NEMO_TOKEN is appropriate for a cloud service. However, the SKILL.md metadata includes a configPaths entry (~/.config/nemovideo/) while the registry summary lists no required config paths — this mismatch is an incoherence in the manifest.

Instruction Scope

Runtime instructions direct the agent to upload user video files to a remote API, create sessions, use SSE, poll export status and include attribution headers. These are expected for a cloud render pipeline. Concerning details: SKILL.md instructs reading this file's YAML frontmatter and detecting install path (~/.clawhub/, ~/.cursor/skills/) to set an X-Skill-Platform header — that requires filesystem/agent-path inspection which is not essential to core editing and broadens the scope of what the agent reads.

Install Mechanism

No install spec and no code files (instruction-only). Lowest risk for arbitrary disk writes or hidden installs.

Credentials

Only one environment variable is declared (NEMO_TOKEN), which is proportional for a third‑party API. SKILL.md also documents a fallback anonymous-token flow (POST to /api/auth/anonymous-token) to obtain a short-lived token if none is present — this is functional but redundant with primaryEnv and means the skill can operate without a user-supplied secret.

Persistence & Privilege

always:false and no install behavior that modifies other skills or global agent settings. The skill does not request permanent presence or elevated privileges.

What to consider before installing

This skill appears to do what it says (upload clips to a cloud service and return edited videos), but review these points before installing: - Privacy: uploaded videos are sent to mega-api-prod.nemovideo.ai — do not send sensitive or private footage unless you trust the service and understand its retention/TOS. - Token handling: you can supply your own NEMO_TOKEN, or the skill will request an anonymous short-lived token on your behalf. If you let the skill obtain tokens, be aware those tokens grant the service access to uploads and jobs until expiry. - File-system reads: the instructions ask the agent to read this file's frontmatter and detect install paths to set attribution headers — confirm you’re comfortable with that filesystem inspection. - Manifest mismatch: the registry metadata and SKILL.md disagree about required config paths; ask the publisher to clarify what, if any, local config is accessed. If you need to proceed: provide a dedicated or revocable token, avoid uploading sensitive footage, and ask the publisher for a privacy/retention policy and clarification of the config-path behavior.

Getting Started

Share your raw footage or clips and I'll get started on AI automatic video creation. Or just tell me what you're thinking.

Try saying:

• "create my raw footage or clips"
• "export 1080p MP4"
• "automatically edit my footage into a"

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 Maker Automatic — Auto-Edit and Export Videos

This tool takes your raw footage or clips and runs AI automatic video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 2-minute raw screen recording and want to automatically edit my footage into a finished video with transitions and music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter source clips under 3 minutes produce faster and more accurate automatic edits.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: video-maker-automatic
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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)

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.

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

Common Workflows

Quick edit: Upload → "automatically edit my footage into a finished video with transitions and music" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "automatically edit my footage into a finished video with transitions and music" — 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.