Image Compressor Pro Free

Get compressed image files ready to post, without touching a single slider. Upload your image files (JPG, PNG, WEBP, GIF, up to 200MB), say something like "c...

Security Scan

The skill's stated purpose (cloud image compression) is coherent with its runtime instructions, but there are small metadata mismatches and privacy-sensitive behavior (automatic token minting and uploading user files to an external domain) from an unknown source, so proceed with caution.

Purpose & Capability

Name/description match the runtime instructions: the skill calls a remote nemo-video API to compress user images. The one mismatch: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reports no required config paths — a minor inconsistency but not fatal to the stated purpose.

Instruction Scope

Instructions stay within the compressor workflow (create/use NEMO_TOKEN, create session, SSE messaging, upload files, poll exports). They do instruct the agent to upload user files and to automatically request an anonymous token from https://mega-api-prod.nemovideo.ai if NEMO_TOKEN is missing — expected for a cloud service but privacy-sensitive. The skill also reads its own frontmatter and may inspect install path to set attribution headers.

Install Mechanism

No install spec and no code files (instruction-only). This is low-risk from an install/execution perspective — nothing is written to disk by an installer.

Credentials

Only a single env var (NEMO_TOKEN) is required and is appropriate for authenticating to the described backend. The skill will also obtain an anonymous token automatically via an external POST if NEMO_TOKEN is absent — reasonable but means the skill will reach out to the external API and create credentials on your behalf.

Persistence & Privilege

always:false and normal autonomous invocation. The skill does not request elevated or persistent platform privileges and does not appear to modify other skills or global agent configuration.

What to consider before installing

This skill relies on a remote service (mega-api-prod.nemovideo.ai) and will upload whatever images you send to that service and may auto-create a 7‑day anonymous token if you don't provide NEMO_TOKEN. That behavior is coherent with a cloud compressor but has privacy implications: do not upload sensitive images unless you trust the service. Consider supplying a known NEMO_TOKEN from a trusted account if you want control over credentials. Note the SKILL.md frontmatter mentions a local config path (~/.config/nemovideo/) even though registry metadata doesn't — ask the author what, if anything, will be read from that path. Finally, the skill's source and homepage are missing; if you need higher assurance, ask the publisher for provenance and a privacy/terms link before installing.

Getting Started

Send me your image files and I'll handle the AI image compression. Or just describe what you're after.

Try saying:

• "compress a 4MB product photo in JPEG format into a 1080p MP4"
• "compress this image to under 500KB without losing visible quality"
• "reducing image file sizes for web upload for web designers, bloggers, marketers"

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.

Image Compressor Pro Free — Compress and Export Smaller Images

Send me your image files and describe the result you want. The AI image compression runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 4MB product photo in JPEG format, type "compress this image to under 500KB without losing visible quality", and you'll get a 1080p MP4 back in roughly under 20 seconds. All rendering happens server-side.

Worth noting: batch uploading multiple images saves time compared to compressing one at a time.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: image-compressor-pro-free
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "compress this image to under 500KB without losing visible quality" — concrete instructions get better results.

Max file size is 200MB. Stick to JPG, PNG, WEBP, GIF for the smoothest experience.

Export as WebP for the best balance of quality and file size on the web.

Common Workflows

Quick edit: Upload → "compress this image to under 500KB without losing visible quality" → Download MP4. Takes under 20 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.