Video Test

Turn a 30-second MP4 clip from a phone into 1080p tested video report just by typing what you need. Whether it's checking video files for playback and qualit...

Security Scan

The skill's runtime instructions mostly match a cloud video-processing service, but there are small metadata inconsistencies and several operational details (automatic anonymous token acquisition, required attribution headers, and implicit platform/install-path detection) that merit caution before use.

Purpose & Capability

The skill's declared purpose (cloud video analysis and export) aligns with the API endpoints and the single required credential (NEMO_TOKEN). However the SKILL.md frontmatter includes a required config path (~/.config/nemovideo/) while the registry metadata lists no config paths — this mismatch is an incoherence to clarify (why read a local config if all activity is cloud-based?).

Instruction Scope

Instructions explicitly direct the agent to obtain tokens (if not set), create sessions, upload user video files, stream SSE messages, run exports, and poll render status — all expected for a cloud render service. Concerns: (1) the skill instructs the agent to auto-acquire and store an anonymous token (which will enable uploading user media) and to ‘not display raw API responses or token values’ (this encourages hiding credential material without explaining storage/retention), and (2) it requires auto-detecting an 'install path' to set X-Skill-Platform — that may push the agent to inspect environment or file system paths. These behaviors expand scope beyond simple stateless API calls and should be confirmed with the skill author.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by the skill itself. That minimizes installation risk.

Credentials

Only one credential (NEMO_TOKEN) is declared and used, which is proportionate for a cloud video service. Note the frontmatter's configPaths entry implies access to a local config directory (~/.config/nemovideo/) even though the registry said no config paths — clarify whether local config access is required and where tokens/sessions are stored.

Persistence & Privilege

The skill is not 'always' enabled and doesn't request elevated platform privileges. It does instruct the agent to store session_id and token for subsequent requests; verify how and where the agent will persist these values and whether they are cleared/rotated.

What to consider before installing

This skill will upload your videos to a third-party cloud service (mega-api-prod.nemovideo.ai) and will create or use a NEMO_TOKEN to run renders. Before installing, confirm: (1) you are comfortable with uploading potentially sensitive video content to that domain, (2) where tokens and session IDs are stored and how long uploaded files/records are kept, (3) why the SKILL.md mentions a local config path (~/.config/nemovideo/) despite registry metadata not requiring it, and (4) whether the agent will need to inspect local install paths or other environment details to set attribution headers. If any of those are unclear, ask the skill author for explicit privacy/retention and storage details, or avoid using it with sensitive videos.

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the AI video analysis.

Try saying:

• "analyze a 30-second MP4 clip from a phone into a 1080p MP4"
• "test this video for quality, playback issues, and resolution"
• "checking video files for playback and quality issues before publishing for content creators"

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 Test — Test and Verify Video Files

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

Here's a typical use: you send a a 30-second MP4 clip from a phone, ask for test this video for quality, playback issues, and resolution, and about 20-40 seconds 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 60 seconds return test results faster.

Matching Input to Actions

User prompts referencing video test, 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-test
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 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 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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "test this video for quality, playback issues, and resolution" — 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.

Common Workflows

Quick edit: Upload → "test this video for quality, playback issues, and resolution" → Download MP4. Takes 20-40 seconds 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.