Best Video Editor Android

edit video clips into edited MP4 clips with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. Android mobile creators use it for editing phone-re...

Security Scan

The skill's requirements and runtime instructions are broadly consistent with a cloud-based video editing service, but there are small metadata mismatches and privacy implications you should understand before installing.

Purpose & Capability

The skill claims to perform cloud video editing and only requests a single service credential (NEMO_TOKEN) and network access to nemovideo.ai — which is appropriate for that purpose. Note: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported none; this mismatch should be clarified by the author.

Instruction Scope

Runtime instructions direct the agent to upload user-provided media and call several nemovideo.ai endpoints (session creation, SSE, upload, render). This is expected for a cloud editor. The instructions also tell the agent how to obtain an anonymous NEMO_TOKEN by POSTing to an external endpoint if no token is present. The file-upload and token-generation flows mean user video and usage metadata will be sent to a third party — an expected but important privacy implication. The instructions also attempt to detect the install path to set X-Skill-Platform headers, which implies the agent may inspect local install paths; this is not strictly necessary for editing and should be clarified.

Install Mechanism

No install spec and no code files (instruction-only) — lowest-risk installation model. Nothing is downloaded or written by an installer in the skill package itself.

Credentials

Only a single service credential (NEMO_TOKEN) is declared as required and is appropriate for a cloud API. The skill also supports creating an anonymous token automatically; that behavior is consistent with the stated flow. No unrelated secrets or multiple external service credentials are requested.

Persistence & Privilege

always is false and autonomous invocation is the platform default. The skill does reference a local config path (~/.config/nemovideo/) in its frontmatter, which could indicate local storage of tokens or config; the registry metadata did not declare config paths. Confirm whether the skill will write to local configuration before installing.

Assessment

This skill behaves like a typical cloud-based video editor: it uploads your videos to mega-api-prod.nemovideo.ai and uses (or can create) a NEMO_TOKEN to run jobs. Before installing, confirm you trust nemovideo.ai with your media and any metadata (privacy and retention). Ask the publisher to clarify the config-path discrepancy (~/.config/nemovideo/ appears in SKILL.md but not in registry metadata) and whether the skill will write tokens or files locally. If you need local-only editing or want to avoid sending media to a third party, do not install. Finally, be aware the skill may inspect its install path to set a header (X-Skill-Platform); if you consider that sensitive, request a version that does not probe local paths.

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"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Best Video Editor Android — Edit and Export Mobile Videos

Drop your video clips 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 phone-recorded vertical clip, ask for trim the footage, add transitions, and put text overlays on each scene, 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 — vertical 9:16 video works perfectly for Reels and TikTok output.

Matching Input to Actions

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

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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is best-video-editor-android, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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.

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

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.

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the footage, add transitions, and put text overlays on each scene" — 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.

Common Workflows

Quick edit: Upload → "trim the footage, add transitions, and put text overlays on each scene" → 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.