Video Editing With Mac

Skip the learning curve of professional editing software. Describe what you want — trim the silent gaps, add transitions, and export as MP4 — and get edited...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based AI video-editing integration (it needs a single NEMO_TOKEN, uploads user videos, and talks to nemovideo.ai), with only minor metadata inconsistencies you should be aware of.

Purpose & Capability

Name/description promise (cloud video editing: upload, trim, render, download) aligns with the instructions and required credential (NEMO_TOKEN). The APIs, upload endpoints, and render/export flows match the stated purpose: nothing requests unrelated cloud credentials, system-level binaries, or unrelated services.

Instruction Scope

SKILL.md instructs the agent to check NEMO_TOKEN in the environment, create anonymous tokens if absent, create sessions, upload files (multipart or URLs), poll render status, and return download URLs. These actions are expected for a cloud-editing service, but the skill also asks the agent to auto-detect platform from its install path and references storing session_id and token values (with guidance to not display raw tokens). Be aware the agent will perform network calls and upload user-supplied video files to external servers; it may also read environment variables and installation paths for platform detection.

Install Mechanism

Instruction-only skill with no install spec and no code files. That minimizes risk from arbitrary installers or downloaded executables.

Credentials

Only a single credential is required (NEMO_TOKEN), which is appropriate for this purpose. The skill will generate and use an anonymous token if NEMO_TOKEN is not present. The frontmatter metadata also lists a config path (~/.config/nemovideo/) not declared elsewhere in the registry metadata — this mismatch is minor but worth noting.

Persistence & Privilege

Skill is not always-enabled and does not request system-wide persistence or modify other skills. It does instruct storing a session_id and using tokens for API requests, which is normal for a networked service.

Assessment

This skill is coherent with a cloud video-editing service: it needs one token (NEMO_TOKEN) and will upload videos to mega-api-prod.nemovideo.ai for processing. Before installing or using it, consider: 1) Privacy: uploaded videos leave your machine — do not send sensitive footage unless you trust nemo's service and policies. 2) Token handling: if you don't supply NEMO_TOKEN the skill will obtain an anonymous token and store session IDs/tokens; supply your own token if you want control. 3) Metadata mismatch: the SKILL.md frontmatter references ~/.config/nemovideo/ while the registry lists no config paths — this is likely benign but worth double-checking. 4) Verify the API domain (mega-api-prod.nemovideo.ai) is the intended service. If any of these are unacceptable, do not install or provide files/credentials.

Getting Started

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

Try saying:

• "edit my raw video footage"
• "export 1080p MP4"
• "trim the silent gaps, add transitions,"

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 Editing with Mac — Edit and Export Mac Videos

Drop your raw video footage in the chat and tell me what you need. I'll handle the AI video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute screen recording from a MacBook, ask for trim the silent gaps, add transitions, and export as MP4, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — MOV files from Mac export best — keep them under 500MB for fastest processing.

Matching Input to Actions

User prompts referencing video editing with mac, 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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	video-editing-with-mac
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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)

Common Workflows

Quick edit: Upload → "trim the silent gaps, add transitions, and export as MP4" → Download MP4. Takes 1-2 minutes 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 "trim the silent gaps, add transitions, and export as MP4" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for widest compatibility across platforms.