Video Maker Free App Android

Get finished MP4 videos ready to post, without touching a single slider. Upload your video clips or images (MP4, MOV, AVI, WebM, up to 500MB), say something...

Security Scan

The skill mostly does what its description says (upload video files to a cloud render service), but there are several internal inconsistencies around required credentials and declared config paths that you should understand before installing.

Purpose & Capability

The skill's name and description match the actions in SKILL.md: uploading user media to a cloud rendering API and returning MP4s. Requesting a single service token (NEMO_TOKEN) is consistent with a cloud video service.

Instruction Scope

Instructions are specific about APIs, endpoints, SSE behavior, uploads, and required headers; they do not ask for unrelated system secrets. They do instruct the agent to read the skill's YAML frontmatter and to detect the agent install path to set X-Skill-Platform, which implies reading filesystem paths under the user's home directory (e.g., ~/.clawhub/, ~/.cursor/skills/). This is within attribution scope but worth noting.

Install Mechanism

No install spec and no code files — instruction-only skill — so nothing is written to disk by an installer. Lowest install risk.

Credentials

Registry metadata marks NEMO_TOKEN as a required primary credential, yet SKILL.md contains logic to obtain an anonymous token automatically if NEMO_TOKEN is not present. Also the frontmatter lists a configPaths entry (~/.config/nemovideo/) while registry metadata earlier indicated no required config paths. These mismatches (required env var vs optional token acquisition, and inconsistent configPaths) are incoherent and merit clarification.

Persistence & Privilege

The skill does not request always:true, does not ask to modify other skills, and only instructs storing a session_id for the duration of interactions. No elevated or persistent platform privileges are requested.

What to consider before installing

This skill appears to be a straightforward cloud video-processing connector: it uploads your media to mega-api-prod.nemovideo.ai, uses a bearer token for authorization, and returns a download URL for rendered MP4s. Before installing, consider the following: (1) Privacy: your videos (and any associated audio/metadata) will be uploaded to an external service — confirm their retention, sharing, and deletion policies. (2) Credentials: the registry marks NEMO_TOKEN as required, but the SKILL.md can auto-generate a short-lived anonymous token if none is present — clarify whether you must supply a personal token and what that token grants. (3) Filesystem reads: the skill will read its own frontmatter and may inspect home-directory install paths to set X-Skill-Platform; verify you’re comfortable with that minimal filesystem access. (4) Billing/credits: anonymous tokens give limited free credits; exports can be blocked by subscription tiers (402). (5) Attribution headers: the skill enforces X-Skill-Source/X-Skill-Version/X-Skill-Platform and may fail exports if missing. If you need higher assurance, ask the publisher for: the service’s privacy/DPA, exact token semantics (what NEMO_TOKEN scopes and lifetime are), clarification of the configPaths vs registry metadata mismatch, and whether uploads are encrypted at rest/transit. The inconsistencies above are not proof of malice but warrant clarification before use.

Getting Started

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

Try saying:

• "create five 10-second phone clips from a weekend trip into a 1080p MP4"
• "combine my clips into one video with music and transitions"
• "editing and combining phone clips into shareable videos for Android mobile users"

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.

Video Maker Free App Android — Create and Export Mobile Videos

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

Say you have five 10-second phone clips from a weekend trip and want to combine my clips into one video with music and transitions — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter clips under 30 seconds each produce the fastest results.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: video-maker-free-app-android
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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 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)

Common Workflows

Quick edit: Upload → "combine my clips into one video with music and transitions" → 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 "combine my clips into one video with music and transitions" — 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 devices and social platforms.