Video Lesson Editor

Skip the learning curve of professional editing software. Describe what you want — cut the long pauses, add chapter titles, and export with subtitles — and g...

Security Scan

The skill's requests and runtime instructions are coherent with a cloud video-editing service: it asks only for a service token and describes API calls to a single remote backend for uploads, edits, and exports.

Purpose & Capability

Name/description match the requested resources and actions: the skill's declared NEMO_TOKEN and optional ~/.config/nemovideo/ path align with a hosted video-rendering backend. Required binaries and install steps are absent, which fits a purely cloud/API-driven editor.

Instruction Scope

SKILL.md contains detailed API workflows (session creation, SSE chat, upload, export polling) and instructions to upload user video files. It also explains anonymous-token acquisition if no NEMO_TOKEN is present. The instructions do not ask for unrelated files or credentials, but they do instruct uploading potentially large user videos to the remote endpoint (expected for the stated purpose).

Install Mechanism

No install spec or downloaded binaries are present; this is instruction-only. That minimizes local-write risk and matches the description of server-side rendering.

Credentials

Only NEMO_TOKEN (primary credential) and a config path (~/.config/nemovideo/) are declared. These are proportionate for a hosted editing service. Remember that possession of NEMO_TOKEN (including an anonymous one created at runtime) grants API access to upload and render media on the provider's backend, so the token is high-value for this skill's domain.

Persistence & Privilege

The skill is not marked always:true and does not request elevation or modification of other skills or system-wide settings. Autonomous invocation is allowed (platform default) but not combined with other high-risk privileges.

Assessment

This skill appears to do what it says: it will upload your video files and use a NEMO_TOKEN to call a nemovideo.ai backend for editing and rendering. Before installing or using it, confirm you trust the nemovideo.ai service and are comfortable uploading the footage and any embedded audio/text. If you lack a token, the skill will mint an anonymous token on your behalf — that is normal but means a short-lived account will be created on the provider. Avoid uploading sensitive or private content, consider creating a dedicated service account/token (rather than using broader credentials), and review nemovideo.ai's privacy/retention policy if available. No local code is installed by the skill itself, so its main risk is data exposure to the remote service.

Getting Started

Send me your raw lesson footage and I'll handle the AI lesson editing. Or just describe what you're after.

Try saying:

• "edit a 12-minute screen recording of a coding tutorial into a 1080p MP4"
• "cut the long pauses, add chapter titles, and export with subtitles"
• "editing raw tutorial recordings into structured video lessons for educators and course creators"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Video Lesson Editor — Edit and Export Lesson Videos

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

A quick example: upload a 12-minute screen recording of a coding tutorial, type "cut the long pauses, add chapter titles, and export with subtitles", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: splitting your lesson into chapters before uploading speeds up the editing process.

Matching Input to Actions

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

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 JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

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 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the long pauses, add chapter titles, and export with subtitles" — 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 learning platforms like Teachable and Udemy.

Common Workflows

Quick edit: Upload → "cut the long pauses, add chapter titles, and export with subtitles" → 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.