Video Compressor Online Free

Get compressed MP4 files ready to post, without touching a single slider. Upload your video files (MP4, MOV, AVI, WebM, up to 500MB), say something like "com...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based video compression tool, but there are minor metadata inconsistencies and a few implementation details you should review before using it.

Purpose & Capability

The skill is a cloud video compressor and requests a single service credential (NEMO_TOKEN), which matches its described API-driven behavior. However the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — this mismatch is unexplained and worth confirming (is the agent allowed to read that directory?).

Instruction Scope

Instructions are focused on creating/using an anonymous NEMO_TOKEN, creating a session, uploading files, and polling for rendered output — all expected for a remote compressor. The skill instructs storing session_id and token for later requests and references uploading local files (multipart -F "files=@/path"). It also asks the agent to auto-detect an install path to set X-Skill-Platform header, which may cause the agent to inspect its environment/install paths; this is not necessarily malicious but is broader filesystem access than purely sending an uploaded file.

Install Mechanism

No install spec or code files are present; this is instruction-only and does not write binaries or download archives. That reduces installation risk.

Credentials

Only NEMO_TOKEN (primaryEnv) is required, which is proportionate for calling the documented API. The instructions also include a flow to obtain an anonymous token if none is set, which is consistent with needing service credentials. There are no unrelated cloud keys or broad secrets requested.

Persistence & Privilege

The skill is not permanently forced (always:false) and does not request elevated platform privileges. It does instruct the agent to store session tokens and session_id for subsequent requests, which is normal for a networked session-based service but means credentials may be kept in agent state.

Assessment

This skill sends your video files to a remote service (mega-api-prod.nemovideo.ai) for processing and will create or use a service token (NEMO_TOKEN) and store session IDs. Before installing: 1) Confirm you trust nemovideo.ai and its privacy policy — do not upload sensitive or private videos unless you accept that they will be processed on that third-party service. 2) Note the small metadata inconsistency (a config path is listed in the skill frontmatter but not in registry metadata) — ask the skill author whether the agent will read ~/.config/nemovideo/ and what it contains. 3) Understand tokens are stored for reuse and the skill may inspect its install path to set headers; if you need strict sandboxing, avoid installing. 4) If you already have a NEMO_TOKEN, provide it only if you trust the service; otherwise let the skill generate the anonymous token it describes (those expire after 7 days).

Getting Started

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

Try saying:

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

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 Compressor Online Free — Compress and Download Smaller Videos

This tool takes your video files and runs AI video compression through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 200MB MP4 recorded on a smartphone and want to compress this video to under 50MB without losing too much quality — the backend processes it in about 20-60 seconds and hands you a 1080p MP4.

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

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	video-compressor-online-free
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 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

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

Reading the SSE Stream

Text events go straight to the user (after GUI translation). Tool calls stay internal. Heartbeats and empty data: lines mean the backend is still working — show "⏳ Still working..." every 2 minutes.

About 30% of edit operations close the stream without any text. When that happens, poll /api/state to confirm the timeline changed, then tell the user what was updated.

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 too much quality" → Download MP4. Takes 20-60 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 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.