Video Game

Get highlight reel clips ready to post, without touching a single slider. Upload your gameplay footage (MP4, MOV, AVI, WebM, up to 500MB), say something like...

Security Scan

The skill's stated purpose (cloud AI video editing) matches most of its instructions, but there are inconsistencies and a few instructions that ask the agent to probe local paths and manage tokens in ways that weren't declared — the mismatches warrant caution before installing.

Purpose & Capability

The skill claims to perform cloud video editing and requires a single API credential (NEMO_TOKEN), which is coherent with the described functionality. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) in its metadata that is not declared in the registry's top-level requirements; this mismatch is unexplained.

Instruction Scope

The runtime instructions include normal API workflows (anonymous-token acquisition, session creation, file upload, render/export polling) which are expected. Concerns: (1) instructions tell the agent to detect X-Skill-Platform from install paths (e.g., ~/.clawhub/, ~/.cursor/skills/) — that implies probing the host filesystem to determine install location, which is outside the obvious task of video editing and was not declared in the registry requirements; (2) the frontmatter references ~/.config/nemovideo/ which suggests reading/writing a local config directory though the registry reported no required config paths; (3) the skill instructs the agent to generate and persist tokens/session IDs for subsequent requests and to avoid showing raw tokens, which is normal for API clients but means the agent will create/hold credentials and session state automatically.

Install Mechanism

No install spec and no code files — instruction-only. That minimizes disk footprint and avoids downloading arbitrary binaries; this is the lower-risk install profile.

Credentials

Only a single credential (NEMO_TOKEN) is declared as required, which matches the API-based design. However, SKILL.md describes an automatic anonymous-token acquisition flow (POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token) that will generate and return a token if NEMO_TOKEN is not set; this is functionally fine but means the skill will create/hold credentials on the user's behalf. The unadvertised ~/.config/nemovideo/ path in the skill metadata implies possible local storage of config/credentials that wasn't declared at the registry level.

Persistence & Privilege

always:false and normal autonomous invocation settings. The skill asks to store session_id/token for request continuity, which is typical. There is no request to modify other skills or system-wide settings. The only minor privilege concern is the implied local config path (~/.config/nemovideo/) which could be used to persist data if the agent follows that metadata.

What to consider before installing

This skill appears to implement remote AI video editing and only needs a NEMO_TOKEN API credential — that is sensible. Before installing, consider: (1) the skill will upload your raw video files to a third-party domain (mega-api-prod.nemovideo.ai) — confirm you are comfortable with that service and its privacy/retention policy; (2) the skill's instructions tell the agent to detect install paths (e.g., ~/.clawhub, ~/.cursor/skills) and reference ~/.config/nemovideo/ even though the registry didn't list any config paths — ask the publisher why the skill needs to probe or write local paths and where it will store tokens/session data; (3) the skill will auto-request an anonymous token if none is provided and store session state — consider network monitoring or limiting outbound access if you want to audit this behavior; (4) if you need higher assurance, ask for source code or a canonical homepage, or run the skill in a sandboxed environment; given the inconsistencies, proceed only if you trust the backend domain or after obtaining clarifications.

Getting Started

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

Try saying:

• "edit my gameplay footage"
• "export 1080p MP4"
• "cut the best highlights, add kill-cam"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Video Game — Edit Gameplay Into Shareable Clips

Drop your gameplay footage in the chat and tell me what you need. I'll handle the AI video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 10-minute raw gameplay recording, ask for cut the best highlights, add kill-cam effects, and sync music to the action, 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 — shorter clips under 3 minutes process significantly faster and are ideal for YouTube Shorts or TikTok.

Matching Input to Actions

User prompts referencing video game, 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-game, 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).

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

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

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.

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 the best highlights, add kill-cam effects, and sync music to the action" → 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 the best highlights, add kill-cam effects, and sync music to the action" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for the best balance of quality and file size across all gaming platforms.