Video Compressor Ios

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

Security Scan

The skill's actions (uploading videos to a remote service using a NEMO_TOKEN) match its stated purpose and requested permissions, but there are minor metadata inconsistencies and privacy/operational details you should review before use.

Purpose & Capability

Name/description (compress iOS videos via remote GPU service) align with requested credential (NEMO_TOKEN) and the runtime instructions (upload, start render, poll status). The skill only asks for a single service token which is expected for a cloud render/compression service.

Instruction Scope

SKILL.md instructs the agent to create an anonymous token if NEMO_TOKEN is absent, start sessions, upload user files, stream SSE responses, and poll render status. Those actions are within the skill's purpose. Minor issues: the skill expects to derive X-Skill-Platform from install path (asks agent to inspect install path), and the instructions mention storing session_id/token without specifying storage location — this could lead to persistent state being written somewhere. Also the SKILL.md metadata lists a config path (~/.config/nemovideo/) not present in the registry 'required config paths' field, an inconsistency to verify.

Install Mechanism

Instruction-only skill with no install spec and no code files. This is the lowest install risk — nothing new is written to disk by an install step defined in the package itself.

Credentials

Only NEMO_TOKEN (primary credential) is required, which is proportional to a cloud video-rendering service. The skill will auto-request an anonymous token if none is present; that is reasonable but means the agent will contact the remote auth endpoint and may persist or cache the token/session (unspecified).

Persistence & Privilege

always:false and the skill is user-invocable and can be invoked autonomously (platform default). The skill does not request global or cross-skill config modification. Potential persistence concern: SKILL.md metadata references a config path (~/.config/nemovideo/) and the instructions say to 'store' tokens/session IDs — confirm where these are stored and for how long.

Assessment

This skill sends your video files to a third-party service (mega-api-prod.nemovideo.ai) and uses a single service token (NEMO_TOKEN). Before installing: 1) Confirm you trust nemovideo.ai (privacy policy, retention of uploaded videos, and where tokens/sessions are stored). 2) Ask how and where the agent will persist the anonymous token/session_id (SKILL.md implies storage but doesn’t say where; the metadata references ~/.config/nemovideo/). If you don't want persistent tokens or disk writes, require clarification. 3) Be aware the skill will automatically create an anonymous token (generating a client UUID) if none is present — this may create a short-lived identity/credits tied to you. 4) Avoid uploading sensitive content unless you accept external processing and storage. If any of these are unacceptable, do not enable the skill or provide your own vetted service credentials instead.

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 1080p MP4"
• "compress this video to under 100MB"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Video Compressor iOS — Compress iOS Videos to MP4

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 2-minute 4K iPhone recording at 800MB, type "compress this video to under 100MB without losing too much quality", and you'll get a 1080p MP4 back in roughly 20-60 seconds. All rendering happens server-side.

Worth noting: shorter clips compress faster — split long videos before uploading for best speed.

Matching Input to Actions

User prompts referencing video compressor ios, 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":"<lang>"}. 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/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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

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): 1. Video: city timelapse (0-10s) 2. BGM: Lo-fi (0-10s, 35%) 3. Title: "Urban Dreams" (0-3s)

Common Workflows

Quick edit: Upload → "compress this video to under 100MB without losing too much quality" → Download MP4. Takes 20-60 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 under 100MB without losing too much quality" — concrete instructions get better results.

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

H.264 codec gives the best balance of quality and file size for iOS-recorded videos.