Video Compressor Youtube

Skip the learning curve of professional editing software. Describe what you want — compress this video for YouTube upload without losing quality — and get co...

Security Scan

The skill's requested credentials and runtime instructions are coherent with a cloud video-compression service that uploads user videos to nemovideo.ai, but there are minor metadata ambiguities and typical privacy considerations you should review before use.

Purpose & Capability

Name/description (YouTube video compression) aligns with the runtime instructions: the SKILL.md describes uploading user videos, creating sessions, rendering, and returning download URLs from mega-api-prod.nemovideo.ai. The only oddity is a mismatch between registry metadata (shows no config paths) and the SKILL.md frontmatter (which lists ~/.config/nemovideo/), but this can be a benign authoring inconsistency.

Instruction Scope

All instructions are limited to interactions with the nemovideo.ai service (auth, session creation, uploads, SSE, render polling). The agent is told to upload user-supplied video files and to generate or use a NEMO_TOKEN; it does not instruct reading unrelated system secrets or arbitrary files. There is some ambiguity about persistent storage: SKILL.md says to "Save session_id" without specifying where, and it instructs deriving an X-Skill-Platform header from install paths (implies reading install path), which grants some discretion to the agent but is not obviously excessive.

Install Mechanism

No install spec and no code files — instruction-only. This is the lowest-risk install mechanism because nothing is written to disk by the skill package itself.

Credentials

The skill requires a single API credential (NEMO_TOKEN), which is proportional for a cloud API client. The SKILL.md can also obtain a short-lived anonymous token via an anonymous-token endpoint if NEMO_TOKEN is absent. The frontmatter's reference to a config path (~/.config/nemovideo/) is present in SKILL.md but not in the registry metadata — this discrepancy could mean the skill expects to read/write a local config directory (for caching tokens or session state); that should be clarified before trusting persistent storage.

Persistence & Privilege

always:false (default) and no requests to modify other skills or system-wide settings. The only persistence implied is saving session_id / tokens for the service; it's not asking for permanent platform-level privileges.

Scan Findings in Context

[no_regex_findings] expected: Scanner found no code files to analyze. That's expected for an instruction-only skill, but absence of findings is not proof of safety — the security surface is the SKILL.md instructions and the external API endpoints it calls.

Assessment

This skill uploads whatever video files you provide to mega-api-prod.nemovideo.ai and requires an API token (NEMO_TOKEN) or will obtain an anonymous token for you. Before installing or using it: 1) Confirm you trust nemovideo.ai to handle your content (sensitive footage will be transmitted off your machine). 2) Verify the origin and scope of any NEMO_TOKEN you provide (don’t reuse unrelated tokens). 3) Ask the publisher to clarify where session_id / tokens are stored (SKILL.md mentions saving session state and references ~/.config/nemovideo/ in the frontmatter). 4) If you require higher assurance, request the publisher's service privacy/security documentation or a signed publisher identity; otherwise treat uploaded videos as leaving your environment.

Getting Started

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

Try saying:

• "compress a 500MB 10-minute YouTube vlog into a 1080p MP4"
• "compress this video for YouTube upload without losing quality"
• "reducing video file size for YouTube uploads for YouTubers"

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 for YouTube — Compress and Export YouTube Videos

Drop your 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 10-minute YouTube vlog, ask for compress this video for YouTube upload 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 and preserve more visual detail.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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.

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

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

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.

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 for YouTube upload 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 size.

Common Workflows

Quick edit: Upload → "compress this video for YouTube upload 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.