Video Compressorjs

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

Security Scan

The skill's declared purpose (cloud video compression) aligns with its runtime instructions (uploading files and calling a nemovideo.ai API); the request for a single service token is expected, but there are a few metadata inconsistencies you should be aware of before installing or using it with sensitive files.

Purpose & Capability

Name/description match the instructions: the skill sends user video files to a cloud render API (mega-api-prod.nemovideo.ai) and returns compressed MP4s. Requiring a NEMO_TOKEN (or issuing an anonymous token) is coherent with a cloud service that uses bearer tokens.

Instruction Scope

SKILL.md explicitly instructs the agent to connect, upload user files, use SSE/polling, and include attribution headers. These actions are within the stated purpose, but they involve sending user content off-host to an external API and storing a session_id. The instructions do not ask the agent to read unrelated system files or other credentials.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. All runtime behavior comes from SKILL.md and network calls.

Credentials

Only one credential (NEMO_TOKEN) is declared as primary, which is proportional. However, SKILL.md provides an anonymous-token flow (generating and POSTing a UUID) so the token appears optional in practice. Also, the SKILL.md frontmatter references a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this metadata mismatch is inconsistent and worth clarifying.

Persistence & Privilege

always:false and normal model invocation. The skill saves a session_id for job management (expected). It does not request persistent platform-wide privileges or modify other skills.

Assessment

This skill will upload any video you provide to an external service (mega-api-prod.nemovideo.ai) and requires or can mint a bearer token (NEMO_TOKEN / anonymous token). Before using it: (1) don't send sensitive or private videos unless you trust the service and its privacy/retention policy; (2) note the metadata mismatch (SKILL.md lists a config path while registry metadata does not) — ask the publisher to clarify what is written or read on disk; (3) if you supply your own NEMO_TOKEN, treat it like other API credentials and only use a token you trust; (4) test with non-sensitive sample videos first; (5) if you need stronger assurances, request the skill publisher's homepage or official docs and confirm the API domain and data-handling policies.

Getting Started

Got video files to work with? Send it over and tell me what you need — I'll take care of the video compression.

Try saying:

• "compress a 200MB MP4 screen 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 content creators, developers, marketers"

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

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

Say you have a 200MB MP4 screen recording 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 you more control over the output size.

Matching Input to Actions

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

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

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 file size for most platforms.