Ai Video Editor Ipad

Turn a 2-minute iPhone video clip into 1080p edited MP4 videos just by typing what you need. Whether it's editing iPhone and iPad footage into polished video...

Security Scan

The skill’s requests and instructions are consistent with a cloud video-editing service (it needs a NEMO_TOKEN and makes API calls to a remote render service); nothing obviously unrelated or covert is present, though there are small metadata inconsistencies you should confirm before installing.

Purpose & Capability

The name and description (cloud AI video editing/export) match the runtime instructions (upload, session creation, render, download). Requiring a NEMO_TOKEN (and supporting anonymous tokens) is appropriate for a remote API. Minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata shown earlier reported no required config paths — this is likely a bookkeeping mismatch but worth confirming.

Instruction Scope

The instructions are narrowly focused on establishing a session, uploading media, streaming edits via SSE, polling render status, and returning a download URL — all within the stated video-editing purpose. They require adding attribution headers and include an instruction to auto-detect an install path for X-Skill-Platform (which may require filesystem/installation-path access in some agent implementations). The skill explicitly instructs not to surface technical details to the user. No instructions ask the agent to read unrelated system files, secrets, or history.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by the skill itself. That is the lowest-risk install profile.

Credentials

Only one credential is declared (NEMO_TOKEN) and it's clearly used for API Authorization. The SKILL.md also describes obtaining an anonymous token if NEMO_TOKEN is not present, which is consistent with the service flow. Aside from the noted configPaths discrepancy in frontmatter, no unrelated secrets or broad environment access are requested.

Persistence & Privilege

The skill does not request persistent installation or elevated platform privileges; always:false and normal autonomous invocation settings are used. It does not attempt to modify other skills or system-wide settings.

Assessment

This skill appears to do what it says: call a remote video-editing API and return edited files. Before installing: 1) Confirm you trust the backend domain (mega-api-prod.nemovideo.ai) because your uploaded videos and any associated metadata will be sent there. 2) Only provide an NEMO_TOKEN you control for this service — do not reuse sensitive tokens from other services. 3) Ask the author to clarify the configPath in the frontmatter (~/.config/nemovideo/) since the registry metadata omitted it; if your agent implementation would allow the skill to read that path, verify what data lives there. 4) If privacy is a concern, test with non-sensitive sample clips first and verify exported files and metadata behavior. If you need higher assurance, request the skill author or publisher identity and a homepage or documentation for the backend service.

Getting Started

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

Try saying:

• "edit my video clips"
• "export 1080p MP4"
• "trim the footage, add transitions, and"

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.

AI Video Editor for iPad — Edit and Export iPad Videos

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

A quick example: upload a 2-minute iPhone video clip, type "trim the footage, add transitions, and sync background music", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter clips under 60 seconds process significantly faster on mobile connections.

Matching Input to Actions

User prompts referencing ai video editor ipad, 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.

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

Header	Value
X-Skill-Source	ai-video-editor-ipad
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.

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

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.

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 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 "trim the footage, add transitions, and sync background music" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms and devices.

Common Workflows

Quick edit: Upload → "trim the footage, add transitions, and sync background music" → 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.