Video Compressor Online

compress large video files into compressed MP4 files with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. content creators, students, marketers...

Security Scan

The skill's requirements and runtime instructions are generally consistent with a remote video-compression service — it needs a service token and uploads user video files to nemovideo.ai — but there are a few small metadata and privacy-related inconsistencies you should be aware of before installing.

Purpose & Capability

Name/description (compress videos via remote service) aligns with declared primary credential (NEMO_TOKEN) and the API endpoints and upload/export workflows described in SKILL.md.

Instruction Scope

Instructions legitimately cover session creation, uploads, SSE, export polling and handling backend responses. They also instruct the agent to read the skill's frontmatter and to detect install-paths (e.g., ~/.clawhub/ or ~/.cursor/skills/) to set an X-Skill-Platform header — this is not required for core compression and involves peeking at filesystem paths, which is a modest privacy scope creep to be aware of. The skill will upload user-supplied video files to the external API (expected for this purpose).

Install Mechanism

No install spec or code is provided; this is an instruction-only skill and therefore does not write code or binaries to disk during install, which minimizes install-time risk.

Credentials

Only NEMO_TOKEN is required as the primary credential, which is proportional to a cloud video service. However, the SKILL.md frontmatter metadata also references a config path (~/.config/nemovideo/) and the skill instructs detection of install paths — the registry metadata listed no required config paths, so there is a small inconsistency to clarify (does the skill intend to read that local config directory?).

Persistence & Privilege

always is false and the skill does not request elevated or persistent platform-wide privileges. It does not instruct modifying other skills or system-wide agent settings.

Assessment

This skill uploads user videos to https://mega-api-prod.nemovideo.ai and needs a NEMO_TOKEN (it can also obtain an anonymous token by calling the service). Before installing: (1) confirm you trust nemovideo.ai and are comfortable with your files being uploaded to that service; (2) provide a token only from a trusted source (or accept anonymous tokens knowing they create a temporary remote account); (3) ask the publisher/registry to clarify the metadata inconsistency around the referenced config path (~/.config/nemovideo/) and whether the skill will read your home-directory install paths — if you want to avoid any local path checks, do not grant the skill filesystem access. If you need higher assurance, request a signed source or code so the network calls and headers can be audited.

Getting Started

Share your large video files and I'll get started on AI video compression. Or just tell me what you're thinking.

Try saying:

• "compress my large video files"
• "export 1080p MP4"
• "compress this video to under 50MB"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Video Compressor Online — Compress and Download Smaller Videos

Send me your large 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 1080p MP4 recording, type "compress this video to under 50MB without losing 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 online, 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.

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

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

Common Workflows

Quick edit: Upload → "compress this video to under 50MB without losing 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.

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