Video Editing With Blender Tutorial

edit video clips into edited tutorial videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. 3D artists and Blender learners use it for tu...

Security Scan

The skill's runtime instructions, requested credential (NEMO_TOKEN), and network endpoints are consistent with a cloud-based video-editing service, but there are a few minor metadata mismatches and privacy considerations to review before installing.

Purpose & Capability

The skill claims to perform cloud GPU video editing and all described actions (session creation, upload, render, export) target a nemo video API — requiring a NEMO_TOKEN is proportionate. Minor inconsistency: the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry summary lists no required config paths.

Instruction Scope

SKILL.md confines operations to the nemo backend (session, SSE chat, upload, render, poll), and the only environment variable referenced in the runtime instructions is NEMO_TOKEN (with a documented anonymous-token fallback). It does not instruct reading unrelated system files or other credentials.

Install Mechanism

There is no install spec and no code files — this is instruction-only, so nothing is written to disk by an installer. This is the lowest install risk profile.

Credentials

The skill asks only for NEMO_TOKEN (primary credential), which fits the claimed API usage. The frontmatter also references a config path (~/.config/nemovideo/) which could imply reading or caching local tokens; that was not declared in the registry metadata and should be confirmed.

Persistence & Privilege

always is false and the skill does not request persistent system-wide privileges or modifications to other skills. It runs via remote API calls and relies on the provided token for authorization.

Assessment

This skill appears to do what it says: it uploads user video and orchestrates edits on a remote nemo video service using a NEMO_TOKEN. Before installing, confirm the provenance of the NEMO_TOKEN you will provide (use an account token you control or rely on the anonymous-token flow if that suits you). Note the frontmatter mentions a local config path (~/.config/nemovideo/) even though the registry summary did not — ask the publisher whether the skill will read or write that directory. Finally, remember using this skill will transmit uploaded video to https://mega-api-prod.nemovideo.ai; only send media you are comfortable being processed by that service and review its privacy/retention policies if available.

Getting Started

Send me your video clips and I'll handle the AI-guided video editing. Or just describe what you're after.

Try saying:

• "edit a 2-minute raw Blender render sequence into a 1080p MP4"
• "cut the render into a tutorial flow, add step labels and transitions"
• "turning Blender screen recordings into structured video tutorials for 3D artists and Blender learners"

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 Editing with Blender Tutorial — Edit Blender Recordings into Tutorials

Drop your video clips 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 2-minute raw Blender render sequence, ask for cut the render into a tutorial flow, add step labels and transitions, 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 — break long Blender walkthroughs into shorter clips before uploading so each step processes faster.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	video-editing-with-blender-tutorial
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "cut the render into a tutorial flow, add step labels and transitions" — 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 YouTube and tutorial platforms.

Common Workflows

Quick edit: Upload → "cut the render into a tutorial flow, add step labels and 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.