Video Compressore Parkside

Get compressed MP4 files ready to post, without touching a single slider. Upload your large video files (MP4, MOV, AVI, MKV, up to 500MB), say something like...

Security Scan

The skill's purpose (cloud video compression) mostly matches its instructions, but there are inconsistencies around credential/config requirements and a few implementation details that don't add up — review before installing or supplying real credentials.

Purpose & Capability

The skill claims to perform cloud video compression and all network endpoints and API actions in SKILL.md align with that purpose. Requesting a NEMO_TOKEN for backend authorization is coherent. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata says no config paths are required — this discrepancy is unexplained.

Instruction Scope

Instructions only instruct API calls to mega-api-prod.nemovideo.ai, SSE handling, uploads, polling and download — all expected for a cloud render service. They do tell the agent to derive an X-Skill-Platform header by inspecting install paths (e.g. ~/.clawhub/, ~/.cursor/skills/) which implies reading local install paths; that is marginal scope creep but not obviously malicious. The skill will upload user video files to the specified third-party domain, which is necessary for cloud processing but has privacy implications.

Install Mechanism

This is an instruction-only skill with no install spec or code files. That lowers disk-write risk; nothing is downloaded or installed by the skill itself.

Credentials

Registry declares NEMO_TOKEN as a required primary credential which fits a cloud API integration. But SKILL.md also describes an automatic anonymous-token acquisition flow (POST to /api/auth/anonymous-token) when NEMO_TOKEN isn't present, meaning the skill can obtain and use tokens itself. Also the frontmatter mentions a config path (~/.config/nemovideo/) that the registry did not list as required. These inconsistencies about how credentials and local config are used are concerning and should be clarified before providing secrets.

Persistence & Privilege

always:false and no install behavior is requested. The skill does not ask to modify other skills or system-wide settings. Autonomous invocation is allowed but is the platform default and not in itself a red flag here.

What to consider before installing

This skill will upload whatever video files you send to https://mega-api-prod.nemovideo.ai for cloud processing and expects a NEMO_TOKEN (but can also auto-request an anonymous token). Before installing or using it: 1) Do not provide a long-lived or production NEMO_TOKEN unless you trust the backend — use a disposable/test token if possible. 2) Confirm the backend domain and provider reputation (mega-api-prod.nemovideo.ai) and check privacy/storage/retention policies for uploaded videos. 3) Ask the skill author to clarify the inconsistent metadata (the frontmatter lists ~/.config/nemovideo/ while the registry lists no config paths) and whether the skill will inspect local install paths to derive headers. 4) If you need stronger assurance, request an auditable code path or a provider homepage/terms of service; avoid sending sensitive or private footage until you verify the service.

Getting Started

Ready when you are. Drop your large video files here or describe what you want to make.

Try saying:

• "compress a 2GB Parkside tool review video recorded on a phone into a 1080p MP4"
• "compress this video to under 200MB without losing quality"
• "reducing large video file sizes for sharing or uploading for DIY creators and tool reviewers"

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 Parkside — Compress and Export 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 2GB Parkside tool review video recorded on a phone, ask for compress this video to under 200MB 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 recordings before uploading.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-compressore-parkside, 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.

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 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)

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 video to under 200MB without losing quality" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, AVI, MKV for the smoothest experience.

H.264 codec gives the best balance of quality and size.

Common Workflows

Quick edit: Upload → "compress this video to under 200MB 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.