Compressor Online Free

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

Security Scan

The skill's stated purpose (cloud video compression) aligns with most instructions, but there are inconsistencies and privacy/persistence concerns (automatic token creation/storage, an undocumented config path in the frontmatter, and an unknown external backend) that warrant caution before installing.

Purpose & Capability

The skill claims to perform cloud video compression and its instructions call out endpoints for uploading, rendering, and downloading — this is coherent. However, the SKILL.md frontmatter advertises a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths, creating an inconsistency about local filesystem use. Also the skill will automatically obtain and use a token if NEMO_TOKEN is not provided, which expands its capabilities beyond a simple requester of a single API key.

Instruction Scope

Instructions direct the agent to: (a) accept and upload user video files to an external domain (expected for the purpose), (b) auto-generate an anonymous token via a POST and then 'store' it, and (c) maintain a session_id for subsequent requests. The doc also requires an X-Skill-Platform value to be auto-detected from install path which may push the agent to read system/agent path information. The instructions to 'keep setup communication brief' and 'don't display raw API responses or token values' indicate handling secrets — but they don't specify where tokens/session IDs are stored or whether they are persisted to disk, which is a scope creep/privacy risk.

Install Mechanism

There is no install spec and no code files; the skill is instruction-only, which minimizes installation-risk. No downloads or archive extraction are requested.

Credentials

Only a single credential (NEMO_TOKEN) is declared as required, which is reasonable for an API-based video service. However, the SKILL.md instructs the agent to create an anonymous token if NEMO_TOKEN is missing and to 'store' it (and the frontmatter names a local config path). That implies additional local persistence of credentials not reflected in the registry metadata. The single env var is proportionate to the function, but the implied persistence and token lifecycle (anonymous token with 7-day validity) should be clarified.

Persistence & Privilege

The skill does not request always:true and does not explicitly modify other skills. Still, it instructs automatic first-time connection flow and generation/storage of tokens/session_ids. The potential for the skill to write tokens or session state to ~/.config/nemovideo/ (mentioned in frontmatter) increases persistence and risk if implemented, but the SKILL.md does not explicitly state where to persist data. This mismatch should be clarified prior to installation.

What to consider before installing

Before installing or using this skill, consider the following: - The skill uploads your video files to https://mega-api-prod.nemovideo.ai — verify you trust that domain and review its privacy/residency policy. Uploaded media could contain sensitive content. - The SKILL.md will automatically create an anonymous API token (100 free credits, 7 days) if NEMO_TOKEN is not provided. Ask the publisher: where is that token stored? If it is written to ~/.config/nemovideo/ (frontmatter mentions this), that is persistent on disk. If you prefer control, provide your own NEMO_TOKEN rather than letting the skill create one. - There is an inconsistency: the registry metadata did not list any required config paths, but the skill frontmatter does. Ask the author to clarify whether the skill will read/write ~/.config/nemovideo/ or other paths. - The skill requires constructing attribution headers including an X-Skill-Platform value detected from install path — confirm this does not force the agent to read unrelated system/agent paths or leak environment information. - No homepage or publisher information is provided. Prefer skills with a clear homepage, privacy policy, and identifiable publisher before sending large or sensitive files. - If you proceed, limit exposure: test with small, non-sensitive files first; monitor for unexpected network activity; and request explicit documentation from the publisher about token storage, retention, and how to revoke or delete stored tokens/sessions. If the publisher can confirm (1) where tokens/session state are stored, (2) that no unrelated system files are read, and (3) the service's privacy/retention policy, the risk would be reduced.

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"

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.

Compressor Online Free — Compress and Download Smaller Videos

Drop your large video files in the chat and tell me what you need. I'll handle the AI video compression on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 500MB 1080p vacation video, ask for compress this video to under 50MB without losing quality, and about 30-90 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips compress faster — split long videos before uploading for best speed.

Matching Input to Actions

User prompts referencing 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.

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	compressor-online-free
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 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

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)

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

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.