Ai Video Editor Gameplay

Skip the learning curve of professional editing software. Describe what you want — cut out the slow parts, add highlight transitions, and sync clips to the b...

Security Scan

The skill's requested secrets, endpoints, and actions align with a cloud-based gameplay video editing service; nothing requested is disproportionate to that purpose.

Purpose & Capability

Name/description describe cloud video editing and the skill only requires NEMO_TOKEN and references APIs on mega-api-prod.nemovideo.ai — these are coherent with a remote render/editing service. The declared config path (~/.config/nemovideo/) and primaryEnv (NEMO_TOKEN) match the described need to persist a session/token.

Instruction Scope

Instructions direct the agent to upload user video files, create sessions, stream SSE edits, poll for render status, and obtain download URLs — all expected for a cloud editor. Note: the skill instructs generating an anonymous token via an API call if NEMO_TOKEN is missing and keeping session_id for operations. It also instructs deriving an X-Skill-Platform header from install paths (which implies checking common install directories); this is limited filesystem access but not unrelated to attribution headers.

Install Mechanism

Instruction-only skill with no install spec and no code files. No packages or remote archives are downloaded or executed by an installer — lowest-risk install posture.

Credentials

Only one credential is required (NEMO_TOKEN), which is appropriate for authenticating to the described API. The SKILL.md describes obtaining an anonymous token if none is present. No other unrelated secrets or credentials are requested.

Persistence & Privilege

Skill is not always-enabled and does not request system-wide changes. It may persist session/token data per its config path, which is reasonable for maintaining a session with the cloud service.

Assessment

This skill sends your uploaded videos and edit requests to mega-api-prod.nemovideo.ai and requires a NEMO_TOKEN (the skill can obtain a short-lived anonymous token if one isn't set). Before installing, confirm you are comfortable uploading your footage to that service, understand the token's scope and 7-day expiry, and review any privacy/terms at the service endpoint. The skill may check common install directories to set an attribution header (minor filesystem access). If you handle sensitive footage, consider not using the skill or verify how the provider stores/retains media and how to revoke tokens.

Getting Started

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

Try saying:

• "edit a 10-minute screen recording of a gaming session into a 1080p MP4"
• "cut out the slow parts, add highlight transitions, and sync clips to the beat"
• "trimming and enhancing gaming recordings for YouTube or Twitch for gaming content 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.

AI Video Editor Gameplay — Edit and Export Gameplay Videos

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

A quick example: upload a 10-minute screen recording of a gaming session, type "cut out the slow parts, add highlight transitions, and sync clips to the beat", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: splitting long sessions into shorter clips before uploading speeds up processing significantly.

Matching Input to Actions

User prompts referencing ai video editor gameplay, 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 ai-video-editor-gameplay, 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)

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 → "cut out the slow parts, add highlight transitions, and sync clips to the beat" → 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 out the slow parts, add highlight transitions, and sync clips to the beat" — 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, Twitch, and TikTok.