Video Editing With Obs

Skip the learning curve of professional editing software. Describe what you want — cut dead air, add transitions, and export a clean highlight reel — and get...

Security Scan

The skill's behavior (uploading your videos to an external API and using a NEMO_TOKEN) is coherent with video-editing functionality, but there are metadata inconsistencies, missing provenance, and instructions that will transmit local files and session tokens to an unknown cloud service — review before installing or uploading sensitive videos.

Purpose & Capability

The name/description (AI edit OBS recordings) align with the runtime instructions (uploading videos, creating render jobs). Requiring a NEMO_TOKEN is reasonable for a cloud API. However, registry metadata claims no config paths while the SKILL.md frontmatter references ~/.config/nemovideo/ (inconsistency). Also the registry declares NEMO_TOKEN as required but the instructions include a fallback anonymous-token flow, which is inconsistent with 'required' being mandatory.

Instruction Scope

The SKILL.md directs the agent to: read local file paths (upload files), generate a UUID, POST to external endpoints, store session_id, and include specific attribution headers. Uploading local video files and sending tokens/sessions to https://mega-api-prod.nemovideo.ai is intrinsic to the stated purpose, but it means user files and session tokens will be transmitted to a third party. The spec also demands X-Skill-Platform derived from an install path (vague for an instruction-only skill). The instructions do not clearly state where to persist session data, and metadata inconsistencies widen the ambiguity.

Install Mechanism

No install spec or code files are present; this is instruction-only which limits what is written to disk by the skill itself. That lowers install risk.

Credentials

Only NEMO_TOKEN is declared as required (primaryEnv), which makes sense for a cloud rendering API. However, the SKILL.md supports generating an anonymous token via the service, and the frontmatter references a config path (~/.config/nemovideo/), which the registry listing did not. This mismatch between declared requirements and the runtime instructions is unexpected and should be clarified.

Persistence & Privilege

always:false and no special persistence or system-wide changes are requested. The skill asks to save a session_id for its own session management, which is normal. It does not request elevated privileges or modify other skills.

Scan Findings in Context

[no-regex-findings] expected: The static regex scanner found no code to analyze (instruction-only SKILL.md). That is expected for a text-only skill, but absence of findings is not evidence of safety — the SKILL.md itself instructs outgoing network calls and file uploads.

What to consider before installing

This skill will upload your local video files and rely on a NEMO_TOKEN (or create an anonymous token) and send session tokens to https://mega-api-prod.nemovideo.ai. The package has no source/homepage and contains inconsistent metadata (declared vs frontmatter config requirements). Before installing or using it: (1) confirm you trust nemovideo.ai and the skill owner; (2) avoid uploading sensitive or private recordings; (3) prefer using an anonymous token instead of long-lived credentials and delete/revoke tokens after use; (4) ask the publisher to resolve the metadata inconsistencies (required env/config paths) and provide a homepage or source repository for inspection; and (5) if you must proceed, monitor network activity and do not place secrets in shared environments.

Getting Started

Share your OBS screen recordings and I'll get started on AI video editing. Or just tell me what you're thinking.

Try saying:

• "edit my OBS screen recordings"
• "export 1080p MP4"
• "cut dead air, add transitions, and"

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 OBS — Edit and Export OBS Recordings

This tool takes your OBS screen recordings and runs AI video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 12-minute OBS gameplay or tutorial recording and want to cut dead air, add transitions, and export a clean highlight reel — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: OBS saves as MKV by default — remux to MP4 in OBS settings before uploading for faster processing.

Matching Input to Actions

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

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

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

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.

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

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute 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.

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)

Common Workflows

Quick edit: Upload → "cut dead air, add transitions, and export a clean highlight reel" → 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 "cut dead air, add transitions, and export a clean highlight reel" — concrete instructions get better results.

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

H.264 codec gives the best balance of quality and file size for OBS exports.