Editor Download Apk

Turn a 2-minute smartphone video clip into 1080p edited MP4 files just by typing what you need. Whether it's editing videos online without downloading an APK...

Security Scan

The skill's declared purpose (cloud video editing) mostly matches its runtime instructions, but there are small metadata inconsistencies and it will automatically obtain/send API tokens and upload user videos to an external, unverified service — make sure you understand the privacy/credential flow before using it.

Purpose & Capability

The skill's stated purpose (cloud-based video editing) aligns with the network endpoints and actions documented in SKILL.md. Requesting a single service token (NEMO_TOKEN) is proportionate for a cloud editing backend. However, the registry metadata lists no required config paths while the skill frontmatter in SKILL.md declares a config path (~/.config/nemovideo/), which is an inconsistency that should be clarified.

Instruction Scope

The SKILL.md instructs the agent to read NEMO_TOKEN from the environment (expected) and, if missing, to POST to an anonymous-token endpoint to obtain a token — then create a session and upload user media. Those network operations and file uploads are consistent with the service purpose, but they do mean user-provided video files and tokens will be transmitted to mega-api-prod.nemovideo.ai. The instructions tell the agent not to expose tokens in UI, which is good, but there's no extra guidance about handling sensitive content or retention/consent.

Install Mechanism

No install spec and no code files are present (instruction-only), so nothing is written to disk by an installer. This minimizes local code-install risk.

Credentials

The skill only requests a single credential (NEMO_TOKEN), which is appropriate for a remote API. However, the registry metadata declares 'Required config paths: none' while SKILL.md frontmatter lists a config path (~/.config/nemovideo/) — an incoherence. Also, although NEMO_TOKEN is listed as required, SKILL.md documents an anonymous-token acquisition flow when the token is absent; that behavior means the skill will create and use ephemeral credentials automatically if you don't provide one, which may be unexpected to users who assumed the token must be supplied manually.

Persistence & Privilege

The skill does not request always:true and does not modify other skills or system-wide settings. It only reads an environment variable and uses in-memory/session tokens for API calls; persistence and privilege requests appear limited to its own session scope.

What to consider before installing

This skill will upload your video files and use or obtain a bearer token (NEMO_TOKEN) to communicate with an external service at mega-api-prod.nemovideo.ai. Before installing or invoking it: (1) confirm you trust that external domain and the skill author — there is no homepage or source listed; (2) understand that if you do not provide NEMO_TOKEN the skill will call the service to generate an anonymous token automatically (this creates credentials and transmits data); (3) consider privacy: uploaded videos may leave your device and be processed/stored by the third party; (4) ask the owner to clarify the metadata mismatch about config paths and whether any local config will be read/written; and (5) if you need guarantees about retention, encryption, or PII handling, get those in writing from the service before sending sensitive media. If you want lower risk, use a local/offline editor or only use this skill with non-sensitive test content.

Getting Started

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

Try saying:

• "edit a 2-minute smartphone video clip into a 1080p MP4"
• "trim the video, add transitions, and export as MP4"
• "editing videos online without downloading an APK app for mobile users"

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.

Editor Download APK — Edit Videos Without APK Install

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

Say you have a 2-minute smartphone video clip and want to trim the video, add transitions, and export as MP4 — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: no APK install needed — edit directly in your browser on any device.

Matching Input to Actions

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

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

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the video, add transitions, and export as 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 Android and iOS devices.

Common Workflows

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