Video Editing With Nas

Skip the learning curve of professional editing software. Describe what you want — pull clips from my NAS, trim the best moments, and add transitions — and g...

Security Scan

The skill's declared token requirement and cloud API calls make sense for remote NAS-based editing, but there are mismatches in the metadata (a referenced local config path not declared elsewhere) and the instructions give the agent broad discretion to fetch/upload user video data to a third-party endpoint — review data-flow and the config-path mismatch before installing.

Purpose & Capability

The skill's name/description (NAS-based video editing) aligns with making API calls to a remote rendering service and requiring a service token (NEMO_TOKEN). However the SKILL.md YAML metadata lists a config path (~/.config/nemovideo/) as required while the registry summary listed no required config paths — this is an internal inconsistency that should be clarified. Otherwise the requested credential (NEMO_TOKEN) is proportionate to the described purpose.

Instruction Scope

The instructions direct the agent to obtain or generate a NEMO_TOKEN, create sessions, upload videos, stream SSE events, poll render status, and include attribution headers on every request to https://mega-api-prod.nemovideo.ai. That behavior is consistent with a cloud render service, but it also means user video files (or URLs to them) will be sent to an external third party. The SKILL.md implies the agent may determine install path headers and references a local config path in metadata — although it does not explicitly tell the agent to read arbitrary user files, the authoring is vague and gives the agent discretion to access local paths or request user credentials/URLs to pull from NAS.

Install Mechanism

No install spec and no code files — instruction-only. This minimizes on-disk additions and arbitrary-download risk.

Credentials

Only NEMO_TOKEN is declared as required, which is expected for a service that needs authentication. The SKILL.md also contains metadata that lists a local config path (~/.config/nemovideo/) which was not reported in the registry requirements — this mismatch could mean the skill expects to read local config files (tokens or settings) but that expectation wasn't surfaced elsewhere. Confirm whether the skill will access that path and why.

Persistence & Privilege

always:false (normal) and the skill is user-invocable. It does not declare any special persistent privileges or system-wide modifications. Autonomous invocation (model-invocation enabled by default) is standard and raises no new flags by itself.

What to consider before installing

This skill will send your videos (or video URLs) to a third-party service at mega-api-prod.nemovideo.ai for cloud editing and requires a NEMO_TOKEN. Before installing: (1) Confirm you are comfortable with uploading private video content to that external service and review their privacy/retention policies. (2) Ask the publisher to clarify the metadata inconsistency: SKILL.md references ~/.config/nemovideo/ but the registry showed no config path — clarify whether the skill will read local files. (3) Never hand over NAS admin credentials; prefer temporary share URLs. (4) If you want to proceed, prefer creating a limited-scope token/anonymous token rather than reusing high-privilege credentials. (5) If you cannot verify the service (domain ownership, privacy terms), treat the skill as higher-risk and avoid sending sensitive media.

Getting Started

Share your video clips and I'll get started on NAS-based AI editing. Or just tell me what you're thinking.

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "pull clips from my NAS, trim"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Video Editing with NAS — Edit and Export NAS-Stored Videos

Send me your video clips and describe the result you want. The NAS-based AI editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute footage file stored on a Synology NAS, type "pull clips from my NAS, trim the best moments, and add transitions", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: keep source clips under 10 minutes for faster NAS transfer and processing speeds.

Matching Input to Actions

User prompts referencing video editing with nas, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-editing-with-nas, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise 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)

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

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.

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 → "pull clips from my NAS, trim the best moments, and add 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "pull clips from my NAS, trim the best moments, and add transitions" — concrete instructions get better results.

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

Export as MP4 with H.264 for the widest playback compatibility across devices.