Video Compressor For Discord 10mb

compress video files into compressed Discord-ready clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. Discord users and gamers use it f...

Security Scan

The skill's declared purpose (cloud video compression) matches most of its runtime instructions, but there are small inconsistencies and ambiguous metadata (config path and platform autodetection) that warrant caution before installing or giving it credentials or uploading private videos.

Purpose & Capability

The skill is a cloud-based video compressor and requests a single service credential (NEMO_TOKEN) and network access to nemovideo endpoints — this is consistent with the stated purpose. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported 'Required config paths: none', which is an inconsistency worth clarifying.

Instruction Scope

The instructions explicitly tell the agent to upload user videos and interact with remote APIs (session creation, SSE chat, upload, export) — all consistent with compressing videos remotely. They also include a fallback flow to obtain an anonymous token via a POST to an external endpoint. The instructions do not request unrelated files or unrelated credentials, but they do instruct the agent to 'keep technical details out of the chat' and require specific attribution headers on every request (including auto-detecting an install path), which is ambiguous in an instruction-only skill and could lead to unexpected behavior.

Install Mechanism

This is an instruction-only skill with no install spec or code files, so nothing will be written to disk by an installer. That lowers supply-chain risk.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is proportionate. However, the SKILL.md metadata referencing a config path (~/.config/nemovideo/) is inconsistent with the registry's 'no config paths' claim — it's unclear whether the skill expects to read local config files (which could contain secrets). The fallback that generates and uses an anonymous token is reasonable, but you should confirm whether tokens are persisted to disk or stored in agent state.

Persistence & Privilege

The skill is not set to always:true, and there is no instruction to modify other skills or global agent settings. There is no explicit instruction to persist credentials system-wide; still, clarify whether anonymous tokens or session IDs are stored locally by the agent.

What to consider before installing

This skill appears to do what it says (uploading videos to a nemovideo cloud service to compress them) and asks only for a single service token. Before installing or using it: 1) Confirm the NEMO_TOKEN source and prefer using an ephemeral/anonymous token rather than a long-lived account token. 2) Ask the skill author whether the agent will read or write ~/.config/nemovideo/ (the SKILL.md frontmatter mentions it but registry metadata does not). 3) Verify the domain (mega-api-prod.nemovideo.ai) and review the service's privacy/retention policy — you will be uploading potentially sensitive video content. 4) Clarify what 'X-Skill-Platform' auto-detection means for an instruction-only skill (there's no install path to detect). If the author can explain or remove the config-path ambiguity and confirm tokens are not persisted insecurely, the mismatch looks like sloppy metadata rather than malicious behavior.

Getting Started

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

Try saying:

• "compress my video files"
• "export 720p MP4"
• "compress this video under 10MB for"

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 for Discord 10MB — Compress Videos for Discord Upload

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

A quick example: upload a 50MB gameplay clip or screen recording, type "compress this video under 10MB for Discord upload", and you'll get a 720p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: trimming your clip to only the essential seconds before compressing helps preserve more quality within the 10MB limit.

Matching Input to Actions

User prompts referencing video compressor for discord 10mb, 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: 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-compressor-for-discord-10mb
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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)

Translating GUI Instructions

The backend responds as if there's a visual interface. Map its instructions to API calls:

• "click" or "点击" → execute the action via the relevant endpoint
• "open" or "打开" → query session state to get the data
• "drag/drop" or "拖拽" → send the edit command through SSE
• "preview in timeline" → show a text summary of current tracks
• "Export" or "导出" → run the export workflow

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.

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "compress this video under 10MB for Discord upload" — 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 for Discord-compatible MP4 files.

Common Workflows

Quick edit: Upload → "compress this video under 10MB for Discord upload" → Download MP4. Takes 20-40 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.