Video Compressor Jpg

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

Security Scan

The skill's requested permissions and runtime instructions are coherent with a cloud video-compression service, but it will upload user videos to an external API and can obtain anonymous tokens if you don't supply NEMO_TOKEN — review that before sending sensitive files.

Purpose & Capability

The skill claims to compress videos and export frames and its runtime instructions only reference endpoints and patterns needed to upload videos, create sessions, render, and download results. Requesting a single service token (NEMO_TOKEN) is proportional to a cloud render service.

Instruction Scope

Instructions explicitly instruct the agent to upload user files and interact with the external API (including streaming SSE responses). They also include logic to obtain an anonymous token from the same API if NEMO_TOKEN is absent. This is expected for a cloud-based video processor but means user files will leave the local environment — do not upload sensitive content unless you trust the service.

Install Mechanism

No install spec and no code files (instruction-only). That reduces supply-chain risk: nothing is written to disk by an installer as part of the skill package itself.

Credentials

Only a single credential (NEMO_TOKEN) is declared as required, which fits the stated purpose. The skill will also create and use anonymous tokens via the service if no token is provided. Minor metadata inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) not shown in the registry's required config paths — this is a small mismatch but not by itself dangerous.

Persistence & Privilege

The skill does not request always:true, has no install behavior, and does not ask to modify other skills or system settings. Its runtime behavior is limited to making HTTP calls to the external API and streaming responses.

Assessment

This skill will upload whatever video files you give it to https://mega-api-prod.nemovideo.ai and will either use your provided NEMO_TOKEN or obtain a short-lived anonymous token for you. Before using it: 1) Don’t upload sensitive or private videos unless you trust that domain and its privacy/storage policies. 2) Prefer to supply your own NEMO_TOKEN only if you understand where that token is scoped/issued. 3) Ask the publisher for a homepage, documentation, or privacy/security policy (none is listed). 4) Note the small metadata mismatch (a config path in SKILL.md not declared in registry) — it’s likely benign but you can request clarification. If you need lower risk, test with non-sensitive short clips first and verify the returned download URLs and retention behavior with the service provider.

Getting Started

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

Try saying:

• "compress my video files"
• "export 1080p MP4"
• "compress this video and export frames"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Video Compressor JPG — Compress Videos and Export Frames

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

Here's a typical use: you send a a 200MB MP4 video file, ask for compress this video and export frames as JPG images, 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 and give you more control over output quality.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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 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 and export frames as JPG images" — 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 MP4 output.

Common Workflows

Quick edit: Upload → "compress this video and export frames as JPG images" → 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.