Video Compressor Gratis

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

This skill is internally consistent with a remote video-compression service: it asks for a single API token, describes remote upload/render endpoints, and has no installer or unexpected binaries — but you should be aware that your video files and a session token are uploaded to an external service and the skill's metadata has a small inconsistency about config paths and provenance is unclear.

Purpose & Capability

Name/description (server-side video compression) match the runtime instructions and required credential (NEMO_TOKEN). The skill's declared primary credential is appropriate for an API-backed service. Minor inconsistency: the SKILL.md YAML frontmatter references a config path (~/.config/nemovideo/) while the registry metadata earlier listed no required config paths.

Instruction Scope

Instructions explicitly direct the agent to call remote endpoints, create anonymous tokens if needed, upload user video files, start render jobs, stream SSE output, and save session_id. All of these are expected for this purpose. Important privacy/security note: user video and associated metadata are transmitted to mega-api-prod.nemovideo.ai — the SKILL.md instructs not to print tokens/raw JSON but does not describe retention or privacy guarantees.

Install Mechanism

No install spec and no code files — instruction-only skills are lower risk because nothing is written to disk. There is no download or execution of third-party packages.

Credentials

Only one environment variable (NEMO_TOKEN) is required, which is proportional for an API client. The frontmatter also mentions a config path (~/.config/nemovideo/) which is not declared elsewhere in the registry summary — this discrepancy should be clarified but does not by itself imply overbroad credential requests.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It asks the agent to maintain a session_id for the render session (normal) and does not instruct modifying other skills or global agent settings.

Assessment

This skill will upload any videos you send to an external service (mega-api-prod.nemovideo.ai) and uses an API token (NEMO_TOKEN) for authorization. Before installing or using it: 1) do not upload sensitive or private videos unless you trust the service and have checked its privacy/retention policy; 2) if you prefer minimising exposure, use the anonymous-token flow described (generates a short-lived token) rather than storing a long-lived secret; 3) note the small metadata mismatch (a config path referenced in the skill file) and the skill has no listed homepage or provenance — consider whether you need a known vendor or privacy terms before proceeding; 4) if you need stronger assurance, ask the publisher for a privacy/retention statement and for clarification about the configPath and token lifecycle.

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 200MB MP4 phone 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 students, casual creators, social media users"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Video Compressor Gratis — 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 200MB MP4 phone recording, type "compress this video to under 50MB without losing too much quality", and you'll get a 1080p MP4 back in roughly 20-60 seconds. All rendering happens server-side.

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

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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.

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

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.

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

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.