Video Editing Classes

Get edited tutorial clips ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, WebM, up to 500MB), say something li...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud video-editing integration that uses a single service token; it does not ask for unrelated credentials or install arbitrary code, but it will upload user videos and call external APIs so you should review privacy and trust the remote service.

Purpose & Capability

The name/description (cloud video editing, upload raw footage, export MP4) align with the instructions (upload endpoint, render/export workflow). The single required credential (NEMO_TOKEN) matches the described cloud backend. Minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) and install-path detection for attribution headers, but the registry metadata provided earlier did not declare required config paths — this is a small mismatch but does not contradict the stated purpose.

Instruction Scope

SKILL.md provides explicit runtime steps that stay within video-editing operations: check for NEMO_TOKEN, create an anonymous token via POST to the service if missing, create sessions, upload media, use SSE for edits, and request exports. These instructions will cause the agent to transmit uploaded videos and metadata to https://mega-api-prod.nemovideo.ai. The skill also instructs the agent to read its own YAML frontmatter and inspect install paths to set an X-Skill-Platform header — that implies some local filesystem inspection (install-path detection) but is scoped to attribution rather than unrelated secrets.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing new is written to disk by an installer. This is the lowest-risk install mechanism in the platform model.

Credentials

Only one credential is requested (NEMO_TOKEN) which is appropriate for a single third-party editing backend. The skill will also generate an anonymous token by calling the service if NEMO_TOKEN is not present (and then use that token). There are no unrelated secrets requested. The small mismatch between the declared registry configPaths (none) and the SKILL.md metadata (~/.config/nemovideo/) is worth noting but not proof of malicious intent.

Persistence & Privilege

always:false and no install-time persistence is requested. The skill uses ephemeral session_id tokens for render jobs; it does not ask to modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) but not combined with 'always:true' or broad credential access.

Assessment

This skill appears to do what it says: it uploads your video and controls a cloud rendering service (mega-api-prod.nemovideo.ai) using a single NEMO_TOKEN (or an automatically obtained anonymous token). Before installing or using it, consider: - Privacy/ownership: your uploaded footage is sent to a third-party service. Don’t upload sensitive or private footage unless you trust their handling and retention policies. Ask for the service's privacy policy and data retention terms. - Tokens: you can supply your own NEMO_TOKEN to avoid anonymous token creation; otherwise the skill will call the API to mint a 7-day anonymous token. If you prefer, provide a token you control and revoke it when done. - Attribution and local reads: the skill will read its own frontmatter and may inspect install paths to set an X-Skill-Platform header — this is limited but means the agent may check certain paths. - Network traffic: all operations contact https://mega-api-prod.nemovideo.ai. If you need higher assurance, verify the domain/operator (homepage, repo, privacy policy) before uploading content. What would raise confidence: a known homepage or source repository, published privacy/security docs, or an operator identity and terms of service for nemovideo.ai. If you cannot verify the service, avoid uploading sensitive content and consider providing a scoped service token you can revoke.

Getting Started

Ready when you are. Drop your raw video footage here or describe what you want to make.

Try saying:

• "edit a 3-minute unedited screen recording into a 1080p MP4"
• "trim the pauses, add transitions, and overlay text labels on each section"
• "turning raw recordings into structured edited video lessons for students and beginner 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 Editing Classes — Edit and Export Video Lessons

Drop your raw video footage in the chat and tell me what you need. I'll handle the AI-guided video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 3-minute unedited screen recording, ask for trim the pauses, add transitions, and overlay text labels on each section, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 2 minutes process significantly faster and are easier to iterate on.

Matching Input to Actions

User prompts referencing video editing classes, 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-editing-classes
• 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)

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

Common Workflows

Quick edit: Upload → "trim the pauses, add transitions, and overlay text labels on each section" → 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 "trim the pauses, add transitions, and overlay text labels on each section" — 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.