Video Compressor Panda

Turn a 500MB 10-minute MP4 recording into 1080p compressed MP4 files just by typing what you need. Whether it's reducing video file size for sharing or uploa...

Security Scan

The skill's requested credential and runtime actions align with a cloud-based video-compression service; nothing in the instructions or metadata is disproportionate to that purpose, but it will upload your videos and use/obtain tokens on a third-party backend so review privacy/credentials before using.

Purpose & Capability

Name/description promise (cloud GPU video compression) matches the instructions and the single required credential (NEMO_TOKEN) which is used for API calls to mega-api-prod.nemovideo.ai. No unrelated credentials or binaries are requested.

Instruction Scope

Instructions are explicit about creating sessions, uploading videos, polling exports, and using SSE. They direct uploads of user video files to the stated nemovideo.ai endpoints (expected). The SKILL.md also instructs reading the skill's YAML frontmatter and detecting an install path (~/.clawhub or ~/.cursor/skills/) to set attribution headers — this requires access to the skill file and home paths (reasonable but worth noting). The skill will generate an anonymous token via the provider if NEMO_TOKEN is absent; it will therefore cause network calls and transfer user media off-device. No instructions to read unrelated system files or other credentials are present.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk or fetched during install. This is the lowest-risk install model.

Credentials

Only NEMO_TOKEN is declared as required (primary credential), which is appropriate for a hosted API. Metadata also lists a config path (~/.config/nemovideo/); the SKILL.md does not strongly justify reading that path but doing so could be reasonable to discover local config or tokens. Expect the skill to either use an existing NEMO_TOKEN you provide or obtain an anonymous short-lived token via the provider's API.

Persistence & Privilege

always:false and user-invocable; the skill does not request persistent system privileges or indicate modification of other skills. Autonomous invocation is allowed (platform default) but not combined with any other concerning privileges.

Assessment

This skill will upload your videos to mega-api-prod.nemovideo.ai and uses an API token (NEMO_TOKEN). If you do not provide a token, the skill will request an anonymous short‑lived token from nemovideo.ai and use that to process uploads. No code is installed locally, but your media and any metadata sent to that backend will leave your machine. Before installing or using: 1) confirm you trust nemovideo.ai and are comfortable uploading the videos and any embedded metadata, 2) avoid supplying long-lived/personal tokens unless you trust the service (anonymous tokens expire in 7 days), 3) if you need guarantees about retention or privacy, ask the publisher for a homepage or privacy/terms links (none are provided), and 4) be aware the skill may read its frontmatter and detect install paths to set attribution headers. If you want stronger assurance, request the skill's source or a reputable homepage before use.

Getting Started

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

Try saying:

• "compress a 500MB 10-minute MP4 recording into a 1080p MP4"
• "compress this video to under 50MB without losing too much quality"
• "reducing video file size for sharing or uploading for content creators, students, marketers"

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.

Video Compressor Panda — Compress and Export Smaller Videos

Send me your video files and describe the result you want. The AI video compression runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 500MB 10-minute MP4 recording, type "compress this video to under 50MB without losing too much quality", and you'll get a 1080p MP4 back in roughly 30-90 seconds. All rendering happens server-side.

Worth noting: shorter clips compress faster and give more predictable output sizes.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: video-compressor-panda
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "compress this video to under 50MB without losing too much quality" — concrete instructions get better results.

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

H.264 codec gives the best balance of quality and size.

Common Workflows

Quick edit: Upload → "compress this video to under 50MB without losing too much quality" → Download MP4. Takes 30-90 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.