Video Editing With Obs Studio

Turn a 10-minute OBS screen recording into 1080p edited video clips just by typing what you need. Whether it's trimming and polishing OBS screen recordings f...

Security Scan

The skill generally matches a cloud video-editing integration, but there are a few inconsistencies and minor scope creep (header/platform detection and declared required token vs. anonymous token flow) that deserve attention before installing.

Purpose & Capability

The name/description (cloud AI video editing for OBS recordings) aligns with the runtime instructions to upload recordings and call a nemo-video render API. Requesting a NEMO_TOKEN is reasonable. However, the SKILL metadata marks NEMO_TOKEN as required even though the SKILL.md documents an anonymous-token acquisition flow; that makes the declared requirement stronger than the documented runtime needs.

Instruction Scope

Instructions direct the agent to call many external endpoints, upload videos, generate and store a session_id, and include attribution headers derived from local install paths. The header logic asks the agent to detect install paths (~/.clawhub/, ~/.cursor/skills/) which implies reading filesystem locations not declared in requires.configPaths. The skill also instructs not to print tokens/raw JSON but requires saving session state — this is plausible but broad (uploads of potentially sensitive videos go to an external service).

Install Mechanism

Instruction-only skill with no install spec and no code files; nothing is written to disk by an installer. This is lower installation risk.

Credentials

Only one credential (NEMO_TOKEN) is declared as primary — appropriate for a cloud editing service. But the skill also lists configPaths (~/.config/nemovideo/) in metadata and asks the agent to derive X-Skill-Platform by probing install paths (which are not declared). The declared required env var is inconsistent with the documented anonymous-token flow (token can be obtained dynamically), so treating NEMO_TOKEN as strictly required is misleading.

Persistence & Privilege

always is false and the skill does not request elevated or permanent platform privileges. It instructs storing a session_id and using tokens for API calls, which is normal for a client integration; it does not ask to modify other skills or system-wide settings.

What to consider before installing

This skill appears to be a client for a cloud video-editing service and will upload your recordings to mega-api-prod.nemovideo.ai. Before installing: 1) Confirm you are comfortable uploading potentially sensitive video/audio to that external service and review its privacy/terms. 2) Note the metadata says NEMO_TOKEN is required but the instructions include an anonymous-token flow — prefer providing your own token if you want account control. 3) Be aware the skill may probe local install paths to set an attribution header (it references ~/.clawhub/ and ~/.cursor/skills/) and will save session IDs/tokens for future calls; if you want to avoid local file reads, restrict or inspect the agent’s filesystem access. 4) Because this is instruction-only (no code), the evaluator had limited static signals — if you need higher assurance, ask the publisher for a domain/owner verification, a privacy policy, or a code-backed implementation before use.

Getting Started

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

Try saying:

• "edit my raw footage"
• "export 1080p MP4"
• "trim 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 Studio — Edit and Export OBS Recordings

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

Say you have a 10-minute OBS screen recording and want to trim 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 exports MKV by default — remux to MP4 in OBS before uploading for faster processing.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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)

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.

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 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 "trim 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 size for OBS exports.