by 详细分析 ▾
运行时依赖
版本
Video Compressor Bitrate 初始版本发布。- 通过指定目标比特率（如"8 Mbps"）压缩视频，无需复杂的编辑软件。- 支持上传最大500MB的MP4、MOV、AVI、MKV文件。- 自动后端连接、token处理和会话管理。- 云GPU处理通常在30-90秒内返回压缩的MP4。- 专为需要更小、高质量视频文件的内容创作者、营销人员和学生设计。
安装命令
点击复制技能文档
Getting Started
Ready when you are. Drop your video files here or describe what you want to make.
Try saying:
- "compress a 10-minute 4K tutorial recording at 80MB into a 1080p MP4"
- "compress this video to 8 Mbps bitrate without losing visible quality"
- "reducing video file size by adjusting bitrate for upload or storage for content creators, marketers, students"
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-tokenwith theX-Client-Idheader - The response includes a
tokenwith 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 Bitrate — Compress Videos by Adjusting Bitrate
Drop your video files in the chat and tell me what you need. I'll handle the AI bitrate compression on cloud GPUs — you don't need anything installed locally.
Here's a typical use: you send a a 10-minute 4K tutorial recording at 80MB, ask for compress this video to 8 Mbps bitrate without losing visible 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 — lower bitrate means smaller file size but too low causes pixelation — aim for 4-8 Mbps for 1080p.
Matching Input to Actions
User prompts referencing video compressor bitrate, 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":""}. 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/ | POST | Upload a file (multipart) or URL. |
/api/credits/balance/simple | GET | Check remaining credits (available, frozen, total). |
/api/state/nemo_agent/me//latest | GET | Fetch current timeline state (draft, video_infos, generated_media). |
/api/render/proxy/lambda | POST | Start export. Body: {"id":"render_","sessionId":"","draft":,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s. |
Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-compressor-bitrate, 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).
All requests must include: Authorization: Bearer , X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.
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= (get |
| 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 |
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.
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
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):
- Video: city timelapse (0-10s)
- BGM: Lo-fi (0-10s, 35%)
- Title: "Urban Dreams" (0-3s)
Common Workflows
Quick edit: Upload → "compress this video to 8 Mbps bitrate without losing visible 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.
Tips and Tricks
The backend processes faster when you're specific. Instead of "make it look better", try "compress this video to 8 Mbps bitrate without losing visible 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 file size when compressing bitrate.