Ai Video Editor Ios

Turn a 60-second iPhone recording into 1080p edited video clips just by typing what you need. Whether it's editing iPhone videos quickly without a desktop ap...

Security Scan

The skill's requirements and runtime instructions align with its stated purpose (cloud video editing) and don't ask for unrelated credentials or installers, but it will upload user videos and create/stash anonymous tokens on your behalf—review privacy and trust in the remote service before use.

Purpose & Capability

The skill is a cloud-based video editor and only requests a NEMO_TOKEN credential and a nemo config path; both are coherent with a remote rendering service. No unrelated env vars or binaries are required.

Instruction Scope

The instructions direct the agent to upload user-provided video files, create an anonymous token via the service if NEMO_TOKEN is absent, maintain a session_id, and call SSE and render endpoints. They avoid reading arbitrary system files, but they ask the agent to detect install path for an attribution header and to avoid showing raw API responses/tokens to the user (this is slightly unusual but not inherently malicious).

Install Mechanism

No install spec or downloadable code is present (instruction-only skill), so there is no installation-phase risk or remote code downloads.

Credentials

Only one credential (NEMO_TOKEN) is required and is the primary credential for the described API. The skill also describes creating an anonymous token if none is supplied, which is proportional to providing access to the backend.

Persistence & Privilege

always:false and no instructions to modify other skills or system-wide config. The skill will hold session state (session_id/token) for API calls, which is expected for this functionality.

Assessment

This skill will upload any video you give it to https://mega-api-prod.nemovideo.ai and may create anonymous tokens on your behalf if you don't provide NEMO_TOKEN. Before installing/use: (1) confirm you trust nemovideo.ai and are comfortable sending the video content off-device (do not send sensitive personal data if you have privacy concerns); (2) consider supplying your own NEMO_TOKEN if you prefer control over credentials; (3) be aware anonymous tokens are short-lived and jobs may be orphaned if you close the session; (4) the skill deliberately hides raw API responses/tokens from the user—if you need transparency for debugging or auditing, request the skill developer to expose logs or responses. If you need more assurance, ask the publisher/homepage or request source code and a privacy policy before proceeding.

Getting Started

Send me your raw video footage and I'll handle the AI video editing. Or just describe what you're after.

Try saying:

• "edit a 60-second iPhone recording into a 1080p MP4"
• "trim the footage, add transitions, and export as a clean short clip"
• "editing iPhone videos quickly without a desktop app for iOS creators"

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.

AI Video Editor iOS — Edit and Export Videos on iOS

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 60-second iPhone recording, ask for trim the footage, add transitions, and export as a clean short clip, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter clips under 60 seconds process significantly faster on mobile connections.

Matching Input to Actions

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

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: ai-video-editor-ios
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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 Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

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.

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 → "trim the footage, add transitions, and export as a clean short clip" → Download MP4. Takes 30-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 "trim the footage, add transitions, and export as a clean short clip" — concrete instructions get better results.

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

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