Ai Video Editor Apk Download

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

Security Scan

The skill mostly matches a cloud video-editing service, but there are several internal inconsistencies and minor red flags (misleading name, conflicting metadata about config paths, and instructions that derive/telemetry-install-path info) that merit caution before use.

Purpose & Capability

The described functionality (cloud AI video editing) aligns with the API endpoints and flows in SKILL.md. However the skill name includes 'APK Download' which is misleading for a video-editing service and could confuse users. Also the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — that mismatch is unexplained.

Instruction Scope

Instructions direct the agent to perform network calls to an external API (expected), create anonymous tokens when NEMO_TOKEN isn't set (explicitly allowed), upload user video files, and store session IDs. They also instruct deriving X-Skill-Platform by checking install paths (e.g., ~/.clawhub/, ~/.cursor/skills/), which implies inspecting the agent's install environment or filesystem and would leak platform/install-path info to the backend — this is outside pure video-editing needs and worth questioning. The doc also instructs to hide raw API responses and token values from users, which is reasonable for UX but reduces transparency about what is sent/received.

Install Mechanism

No install spec and no code files are present, so nothing is written to disk by the skill itself. That's the lowest-risk install posture.

Credentials

The only declared required environment variable is NEMO_TOKEN, which is coherent with the API's Authorization header. However, SKILL.md provides a fallback that auto-generates an anonymous token if NEMO_TOKEN is not set — this contradicts the idea of NEMO_TOKEN being strictly 'required'. The frontmatter also references a config path (~/.config/nemovideo/) that is not declared in the registry, creating ambiguity about what filesystem access the skill expects.

Persistence & Privilege

always:false and no install-level persistence are specified. The skill instructs keeping the session_id for requests but does not request system-wide privileges or automatic always-on inclusion.

What to consider before installing

This skill appears to be a cloud-based AI video editor and will upload your files to an external API. Before installing or invoking it, consider: (1) the skill name says 'APK Download' which is misleading — verify you actually want a video-editing service, not an APK-related download; (2) it will either use an existing NEMO_TOKEN or automatically request an anonymous token from the provider — be comfortable with the provider receiving your video content and basic session/install-path metadata; (3) the skill's instructions derive an X-Skill-Platform header by checking install paths (this may reveal details about your environment), and the frontmatter refers to a config path that the registry doesn't list — ask the author to clarify why filesystem info is needed and where session/token data will be stored; (4) confirm the provider's privacy/storage policy for uploaded videos and any retention or sharing rules; and (5) if you want higher assurance, request the skill owner publish a homepage, source link, or official documentation (and explain the configPath vs registry mismatch) before use.

Getting Started

Ready when you are. Drop your raw video footage here or describe what you want to make.

Try saying:

• "edit a 60-second phone-recorded clip into a 1080p MP4"
• "trim the footage, add transitions, and export as a clean MP4"
• "editing mobile-shot videos quickly without a desktop app for mobile-first content 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 APK Download — Edit and Export Videos Online

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-recorded clip and want to trim the footage, add transitions, and export as a clean MP4 — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 2 minutes process significantly faster.

Matching Input to Actions

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

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is ai-video-editor-apk-download, 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).

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 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

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

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.

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 export as a clean MP4" — 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 all platforms and devices.

Common Workflows

Quick edit: Upload → "trim the footage, add transitions, and export as a clean MP4" → Download MP4. Takes 1-2 minutes 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.