Ai Video Editor Mobile

Skip the learning curve of professional editing software. Describe what you want — trim the shaky parts, add transitions, and export as a Reel — and get edit...

Security Scan

The skill's requests and runtime instructions align with an AI cloud video-editing service and its single required credential (NEMO_TOKEN) is proportional, with only a small metadata inconsistency to verify before use.

Purpose & Capability

Name/description match the runtime instructions: the SKILL.md describes uploading mobile video, creating a session, sending SSE edit commands, polling render status, and downloading an output URL. Requesting a single service token (NEMO_TOKEN) is appropriate for a hosted API. One minor inconsistency: the registry metadata earlier listed no required config paths, while the SKILL.md frontmatter lists ~/.config/nemovideo/ — this should be clarified (reading that path would be unnecessary for basic API use).

Instruction Scope

Instructions stay within the editor's scope: they describe connecting to the nemovideo backend, creating sessions, uploading files (multipart or by URL), streaming SSE edits, polling render jobs, and returning download URLs. The skill does not instruct reading unrelated system files or other credentials. Note: it asks the agent to auto-detect an install path to populate X-Skill-Platform header (this reveals local install path information) — low risk but worth noting.

Install Mechanism

Instruction-only skill with no install spec and no code files; nothing is written to disk by an installer. This is the lowest-risk install model.

Credentials

Only NEMO_TOKEN is required (declared as primaryEnv), which is appropriate for authenticating to the external API. The skill includes a fallback flow to obtain an anonymous token (POST to the service) if no token is present. The frontmatter's mention of a config path (~/.config/nemovideo/) is inconsistent with the registry metadata and with the runtime instructions (which don't require reading that path) — confirm whether the skill will read or write that directory. No other unrelated credentials or secrets are requested.

Persistence & Privilege

always is false and there are no instructions to persist itself into agent configs or modify other skills. The skill requires network access to the external API (expected). Autonomous invocation is allowed by default but is not combined with unusual privileges here.

Assessment

This skill appears internally consistent for a cloud-based video editor: it needs a single service token (NEMO_TOKEN) to call https://mega-api-prod.nemovideo.ai and will upload user video to that service to produce edits. Before installing, confirm you trust that external domain and its privacy/retention policy for uploaded videos. Also clarify the small metadata mismatch: the SKILL.md frontmatter mentions ~/.config/nemovideo/ while the registry lists no config paths — ask the developer whether the skill will read or write that directory. Avoid supplying any unrelated or high-privilege credentials (AWS keys, system passwords). If you need stronger guarantees, ask for a link to the service's homepage/privacy policy or for the maintainer identity before using with sensitive footage.

Getting Started

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

Try saying:

• "edit my raw mobile footage"
• "export 1080p MP4"
• "trim the shaky parts, add transitions,"

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 Mobile — Edit Phone Videos for Social Media

This tool takes your raw mobile footage and runs AI mobile video editing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 60-second vertical phone recording and want to trim the shaky parts, add transitions, and export as a Reel — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: vertical 9:16 video is fully supported for Reels and TikTok exports.

Matching Input to Actions

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

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

Header	Value
X-Skill-Source	ai-video-editor-mobile
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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.

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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the shaky parts, add transitions, and export as a Reel" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across all mobile platforms.

Common Workflows

Quick edit: Upload → "trim the shaky parts, add transitions, and export as a Reel" → 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.