Video Editor Remastered

Skip the learning curve of professional editing software. Describe what you want — remaster this old footage, sharpen the details, and boost the colors to lo...

Security Scan

The skill's requests and runtime instructions are generally consistent with a cloud-based video remastering service: it needs a single service token, uploads user video files, and talks to a single API endpoint — there are minor metadata inconsistencies and the skill will send your videos to an external service, so review that before use.

Purpose & Capability

Name/description (AI video remastering) align with the runtime instructions: the skill uploads video files, creates a session, sends edit requests and polls for a rendered MP4 from a remote GPU backend. The only declared credential (NEMO_TOKEN) fits that purpose. Minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata above stated 'Required config paths: none'. This is a small metadata mismatch but does not break coherence.

Instruction Scope

SKILL.md stays within the stated scope: it describes authenticating (using NEMO_TOKEN or generating an anonymous token), creating a session, uploading videos, streaming SSE edits, polling render status, and returning download URLs. It does require reading/synthesizing an install path string to set the X-Skill-Platform header (i.e., checking local paths like ~/.clawhub or ~/.cursor/skills/) and storing a session_id for subsequent calls — these are reasonable for attribution/session management but are the only filesystem checks referenced. The instructions do not ask for unrelated secrets or system-wide data.

Install Mechanism

Instruction-only skill with no install spec and no code files. This is low-risk from an installation perspective because nothing is downloaded or written by an installer step by default.

Credentials

The sole required environment variable is NEMO_TOKEN (declared as primaryEnv), which is appropriate for a remote service. SKILL.md also instructs the agent to obtain an anonymous token from the service automatically if NEMO_TOKEN is not present — that behavior is coherent but effectively results in the skill creating credentials at runtime. The frontmatter's mention of a local config path (~/.config/nemovideo/) suggests the skill may persist session/token info locally; this is plausible for convenience but is a slightly higher privilege than in-memory-only session use.

Persistence & Privilege

always:false and normal autonomous invocation are appropriate. The skill asks to store session_id (expected) and may read/write under ~/.config/nemovideo/ (implied by frontmatter). It does not request system-wide or other-skills' credentials or make any claims about modifying other skills or system settings.

Assessment

This skill appears to do what it claims: it will upload your videos to the external domain mega-api-prod.nemovideo.ai, use or generate a NEMO_TOKEN, create a session, and return a rendered video URL. Before installing or using it: (1) confirm you are comfortable with external uploads of any videos you provide (do not upload sensitive content), (2) verify the privacy/terms of the unknown backend if possible, (3) be aware the skill may persist session/token data under ~/.config/nemovideo/ (the frontmatter mentions this), and (4) consider testing with a non-sensitive short clip first. The only minor red flag is a metadata mismatch (registry said no config paths but SKILL.md references one); if provenance matters, ask the publisher for a homepage or source code to increase confidence.

Getting Started

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

Try saying:

• "remaster my raw video footage"
• "export 1080p MP4"
• "remaster this old footage, sharpen the"

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.

Video Editor Remastered — Remaster and Export HD Videos

Send me your raw video footage and describe the result you want. The AI video remastering runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute low-quality phone recording from 2015, type "remaster this old footage, sharpen the details, and boost the colors to look modern", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips process faster — split long videos into segments before uploading for quicker results.

Matching Input to Actions

User prompts referencing video editor remastered, 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.

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

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

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.

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.

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

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)

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

Common Workflows

Quick edit: Upload → "remaster this old footage, sharpen the details, and boost the colors to look modern" → 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 "remaster this old footage, sharpen the details, and boost the colors to look modern" — 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 the best balance of quality and file size.