Best Video Editor For Android

Turn a 60-second phone-recorded vertical clip into 1080p edited video clips just by typing what you need. Whether it's editing phone-recorded videos into pol...

Security Scan

The skill's runtime instructions match a cloud-based video-editing purpose, but there are metadata inconsistencies and privacy/credential handling details that don't add up and warrant caution.

Purpose & Capability

The name/description align with the runtime actions (upload video, create session, render/export via https://mega-api-prod.nemovideo.ai). Requesting a NEMO_TOKEN is expected for a cloud service. However, the skill simultaneously declares NEMO_TOKEN as required while providing an anonymous-token acquisition flow in the SKILL.md (it will POST to an anonymous auth endpoint to obtain a token). That makes the declared 'required env var' ambiguous: it is not strictly required for operation. Also the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/) but the registry metadata listed no config paths — this mismatch is inconsistent.

Instruction Scope

Instructions stay largely within the stated purpose: create session, upload video, start SSE edits, poll for export and return a download URL. The skill explicitly instructs uploading user video files and tokens to the third-party API and to keep tokens secret. This is expected for a cloud renderer, but it is a high-privacy action (user video content will be sent to an external service). There are no instructions to read unrelated local files or to exfiltrate arbitrary system data.

Install Mechanism

This is instruction-only with no install spec or code files, so there is nothing written to disk or fetched at install time. That lowers install-time risk. Note: lack of source/homepage means you cannot verify the backend/service independently.

Credentials

Only NEMO_TOKEN is declared as the primary credential which is proportionate for a cloud API. But SKILL.md's anonymous-token flow (POST to /api/auth/anonymous-token) effectively allows operation without a pre-provided token, making the requirement inconsistent. The frontmatter also lists a config path (~/.config/nemovideo/) not present in the registry requirements. These mismatches reduce transparency about what credentials or local config the skill actually needs.

Persistence & Privilege

The skill does not request always:true and does not ask to modify other skills or system-wide settings. It keeps session_id and tokens for its own workflow, which is normal for a session-based cloud integration.

What to consider before installing

This skill appears to implement a cloud video-editing workflow and will upload your video files to mega-api-prod.nemovideo.ai and obtain/require a NEMO_TOKEN. Before installing or using it: (1) Decide whether you are comfortable uploading potentially sensitive video/audio to an unknown third-party—there is no homepage or source to verify privacy practices. (2) Ask the publisher for a homepage, privacy policy, or source code to confirm the endpoint and token handling. (3) If you have a vendor-provided NEMO_TOKEN, prefer supplying that rather than relying on anonymous tokens. (4) Note the metadata mismatch (declared env/config vs SKILL.md behavior); ask the author to clarify whether NEMO_TOKEN is mandatory and whether any local config (~/.config/nemovideo/) will be read. If you cannot verify these points, treat the skill with caution and avoid uploading sensitive content.

Getting Started

Got video clips to work with? Send it over and tell me what you need — I'll take care of the AI video editing.

Try saying:

• "edit a 60-second phone-recorded vertical clip into a 1080p MP4"
• "trim the footage, add transitions, and put text overlays on each scene"
• "editing phone-recorded videos into polished shareable clips for Android mobile creators"

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 for Android — Edit and Export Mobile 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 60-second phone-recorded vertical clip, type "trim the footage, add transitions, and put text overlays on each scene", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: vertical 9:16 video works perfectly for Reels and TikTok exports.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: 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	best-video-editor-for-android
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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)

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

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.

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

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.

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 and social platforms.