Video Compressor Extreme

Skip the learning curve of professional editing software. Describe what you want — compress this video to under 100MB while keeping the best possible quality...

Security Scan

The skill's behavior (uploading user videos to an external cloud service and auto-requesting anonymous tokens) mostly matches its description, but there are small inconsistencies and privacy/traceability concerns you should review before installing.

Purpose & Capability

Name/description match the instructions: it routes uploads, creates sessions, starts render jobs and returns download URLs. The primaryEnv (NEMO_TOKEN) is coherent with a cloud API. However the skill source/homepage are unknown and the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) that is not listed in the registry-level requirements — this mismatch reduces traceability and is unexplained.

Instruction Scope

Runtime instructions will upload user video files (up to 500MB) to an external endpoint and may generate an anonymous token by POSTing to an API if NEMO_TOKEN is absent. That behavior is consistent with the stated purpose, but it means user data and derived tokens are transmitted off-device; the SKILL.md instructs not to expose tokens in UI, but the agent will still send them as Authorization headers to the third-party service. The instructions do not ask the agent to read unrelated local files, but the frontmatter's config path implies potential read/write access which is not described in the runtime steps.

Install Mechanism

No install spec and no code files — instruction-only skill — so nothing will be written to disk by an installer. This minimizes install-time risk.

Credentials

Only one declared credential (NEMO_TOKEN), which fits a cloud video service. The SKILL.md will obtain an anonymous token itself if NEMO_TOKEN is missing, so requiring the env var is not strict. The frontmatter also lists a config path (~/.config/nemovideo/), which implies local config access but the registry metadata provided to you said no required config paths — this inconsistency should be clarified before trusting credentials.

Persistence & Privilege

always is false and the skill does not request elevated or persistent system privileges. It does not declare modifying other skills or system-wide settings. Autonomous invocation is allowed (platform default) but not combined with 'always:true'.

What to consider before installing

This skill will upload whatever video you give it to a third‑party API (mega-api-prod.nemovideo.ai) and may generate/hold an anonymous token to do so. Before installing or using it: 1) Confirm you trust the external domain and service — there is no homepage or owner info. 2) Do not supply sensitive or private videos until you validate the service’s privacy/retention policy. 3) Note the skill can auto-create a NEMO_TOKEN by calling the API; consider whether you want the agent to obtain tokens on your behalf. 4) Ask the maintainer to explain the config path discrepancy (~/.config/nemovideo/) and to provide a trusted homepage or repo. 5) Test with a non-sensitive short clip first. If you need stronger assurance, request source code or a vetted published endpoint before use.

Getting Started

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

Try saying:

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

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 Extreme — Compress and Export Smaller Videos

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

Say you have a 2GB 1080p travel video recording and want to compress this video to under 100MB while keeping the best possible quality — the backend processes it in about 1-3 minutes and hands you a 1080p MP4.

Tip: shorter clips compress faster and give you more control over the quality-to-size ratio.

Matching Input to Actions

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

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

Header	Value
X-Skill-Source	video-compressor-extreme
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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 field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

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 "compress this video to under 100MB while keeping the best possible 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 file size for compressed output.

Common Workflows

Quick edit: Upload → "compress this video to under 100MB while keeping the best possible quality" → Download MP4. Takes 1-3 minutes 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.