Video Android

Turn a 2-minute Android screen recording into 1080p edited MP4 clips just by typing what you need. Whether it's editing Android-recorded videos for social me...

Security Scan

The skill's requested token and network calls line up with a cloud-based video-editing tool, but there are small metadata inconsistencies and you should confirm you trust the external API before uploading videos or providing a token.

Purpose & Capability

The skill claims to perform cloud video editing and only requires an API token (NEMO_TOKEN) and interactions with a video render API (mega-api-prod.nemovideo.ai). Those requirements are consistent with a cloud video-editing workflow.

Instruction Scope

The SKILL.md instructs the agent to: read NEMO_TOKEN or obtain an anonymous token, create sessions, upload user video files (multipart or by URL), send SSE messages, poll for render status, and return download URLs. All of this is expected for a cloud editor. It also asks the agent to auto-detect an install path to set an X-Skill-Platform header (may require reading an install path or runtime path info) — benign for telemetry but something to be aware of for privacy.

Install Mechanism

No install spec or code is present; this is instruction-only. That minimizes on-disk installation risk.

Credentials

The only declared credential is NEMO_TOKEN (primaryEnv), which is appropriate for an API-backed service. However, the SKILL.md frontmatter also references a config path (~/.config/nemovideo/) while the registry metadata earlier reported no required config paths — this mismatch should be clarified. The skill also supports creating an anonymous token if NEMO_TOKEN is absent, which reduces friction but still results in networked uploads.

Persistence & Privilege

The skill is not forced-always and is user-invocable. It allows normal autonomous invocation (disable-model-invocation: false) which is the platform default; this is expected for a usable skill.

Assessment

This skill appears to be a straightforward cloud-based video editor: it will upload your Android screen recordings to https://mega-api-prod.nemovideo.ai, use a session token (NEMO_TOKEN) to run cloud render jobs, and return download URLs. Before installing or using it: 1) Only provide NEMO_TOKEN if you trust the nemo video service and its handling of uploaded videos. If you don't have a token, the skill will obtain an anonymous starter token automatically — that still uploads your video to the external service. 2) Confirm the inconsistency around config paths — SKILL.md references ~/.config/nemovideo/ even though registry metadata listed no config paths. 3) Be aware the agent may read runtime/install-path information to fill the X-Skill-Platform header (minor privacy leak of environment/paths). 4) Because this is instruction-only, there is no local code to inspect — all behavior is driven by the SKILL.md text. If you have sensitive video content, do not upload it until you verify the service's privacy/retention policy and trustworthiness.

Getting Started

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

Try saying:

• "edit a 2-minute Android screen recording into a 1080p MP4"
• "trim the footage, add captions, and export for YouTube"
• "editing Android-recorded videos for social media or YouTube 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.

Video Android — Edit Android Videos and Export

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 Android screen recording and want to trim the footage, add captions, and export for YouTube — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips under 60 seconds process significantly faster.

Matching Input to Actions

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

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

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

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.

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.

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.

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

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

Common Workflows

Quick edit: Upload → "trim the footage, add captions, and export for YouTube" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "trim the footage, add captions, and export for YouTube" — 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 web platforms.