Ai Video Editor For Android

Turn a 60-second phone recording shot on Android into 1080p edited MP4 clips just by typing what you need. Whether it's editing phone-recorded videos quickly...

Security Scan

The skill's declared purpose (cloud video editing) mostly fits its runtime instructions, but there are small metadata inconsistencies and the instructions will upload local video files and read local install/config paths — actions you should explicitly consent to and verify before installing.

Purpose & Capability

The skill claims to edit Android phone video via a cloud render pipeline and the SKILL.md only requires a single service token (NEMO_TOKEN) and network access to nemovideo.ai — that is coherent. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) and runtime instructions expect to detect install paths (~/.clawhub/, ~/.cursor/skills/) while the registry metadata earlier reported no required config paths. This metadata mismatch is unexplained and worth confirming.

Instruction Scope

The instructions direct the agent to: read the skill frontmatter, detect install paths, read/attach local files for multipart uploads (e.g. -F "files=@/path"), call several nemovideo.ai endpoints, and include attribution headers on every request. Uploading user videos to a third-party cloud is central to the skill but is a privacy/security-sensitive operation and should be expected and consented to. The instructions do not reference any unrelated system secrets, but they do require filesystem access and generate/use tokens obtained from the external API.

Install Mechanism

Instruction-only skill with no install spec and no code files — the lowest install risk. Nothing is fetched or written by an installer step in the provided metadata.

Credentials

Only one declared credential is required (NEMO_TOKEN), which matches the stated API usage. The skill will generate an anonymous token automatically if NEMO_TOKEN is not present. The SKILL.md frontmatter also declares a config path (~/.config/nemovideo/) and runtime behavior checks local install paths — these filesystem accesses are minor but should have been declared in the registry metadata (which currently lists no config paths). No unrelated secret/env var requests were found.

Persistence & Privilege

always is false and the skill does not request persistent system-wide changes or privileged escalations. It does not declare modifying other skills or system configs.

What to consider before installing

This skill will upload your videos and related metadata to a third-party service (api host: mega-api-prod.nemovideo.ai) and will use or obtain a token (NEMO_TOKEN or an anonymous token it fetches). Before installing, verify you trust that service and avoid sending sensitive or private videos. Confirm whether the platform/company is legitimate (there is no homepage provided). Ask the publisher to explain the metadata mismatch (SKILL.md declares ~/.config/nemovideo/ and install-path detection but the registry shows no required config paths). If you proceed, prefer providing a limited-scoped token and do not reuse credentials from other services. If you need higher assurance, request the skill author publish a homepage, privacy policy, and a canonical install/manifest that matches the runtime instructions.

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 phone recording shot on Android into a 1080p MP4"
• "trim the clip, add transitions, and overlay background music"
• "editing phone-recorded videos quickly on Android devices for Android content creators"

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 Android — Edit and Export Videos on Mobile

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

Say you have a 60-second phone recording shot on Android and want to trim the clip, add transitions, and overlay background music — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 2 minutes process significantly faster on mobile connections.

Matching Input to Actions

User prompts referencing ai video editor for android, 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-for-android
• 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 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 clip, add transitions, and overlay background music" → 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 clip, add transitions, and overlay background music" — 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 Android apps and social platforms.