Video Maker Google Free

Get polished MP4 videos ready to post, without touching a single slider. Upload your images or clips (MP4, MOV, JPG, PNG, up to 500MB), say something like "c...

Security Scan

The skill's runtime instructions, required credential (NEMO_TOKEN), and network calls are consistent with a cloud-hosted video rendering service — nothing indicates it is trying to do unrelated or hidden work, though there are minor metadata inconsistencies and normal privacy risks to consider.

Purpose & Capability

The skill claims to upload media and request cloud renders; the single required credential (NEMO_TOKEN) and the listed API endpoints match that purpose. One inconsistency: the registry metadata indicated no required config paths, but the SKILL.md frontmatter references ~/.config/nemovideo/ in metadata (likely for storing tokens/session). This is a minor mismatch but not evidence of malicious intent.

Instruction Scope

Instructions focus on creating a session, uploading media, streaming SSE responses, polling job status, and exporting downloads — all coherent with a video render backend. The skill only reads NEMO_TOKEN from the environment and otherwise obtains an anonymous token via the service’s auth endpoint if none is present. It does not instruct reading arbitrary system files or unrelated credentials. It does mention auto-detecting a platform string from an install path, which is a small scope creep (harmless if limited to agent install path).

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That lowers risk and matches the described behavior.

Credentials

Requesting a single service token (NEMO_TOKEN) is proportional for a cloud video service. The SKILL.md also supports obtaining an anonymous token itself via the provider’s anonymous auth endpoint (no user secret needed). Note the frontmatter references a config directory (~/.config/nemovideo/) not declared in the registry; that likely is where tokens/sessions might be stored — verify whether you want the skill to persist tokens locally before installing.

Persistence & Privilege

The skill is not marked always:true and does not request elevated platform-wide privileges. It maintains session state with the backend (session_id) as expected for a remote render workflow; nothing indicates modification of other skills or system-wide settings.

Assessment

This skill appears to do what it says: upload your media to a nemo-video backend, render on cloud GPUs, and return a download link. Before installing, consider: 1) NEMO_TOKEN is the service credential — if you provide your personal token it grants the skill access to that account/credits; prefer using an anonymous token if you want limited exposure. 2) Any media you upload is sent to https://mega-api-prod.nemovideo.ai — do not upload sensitive or regulated content unless you trust the service and its privacy policy. 3) The SKILL.md mentions storing session/token data (config path in frontmatter) — verify whether you are comfortable with local persistence of tokens. 4) The registry metadata and SKILL.md slightly disagree about declared config paths; that mismatch is minor but worth confirming. If you need higher assurance, ask the author for the official service homepage, privacy/terms, or a signed publisher identity before using with private data.

Getting Started

Got images or clips 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 product photos and a logo file into a 1080p MP4"
• "combine these images into a 30-second video with background music and text overlays"
• "creating videos from images or clips without paid software for students and small business owners"

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.

Video Maker Google Free — Create and Export MP4 Videos

Drop your images or clips in the chat and tell me what you need. I'll handle the AI video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a five product photos and a logo file, ask for combine these images into a 30-second video with background music and text overlays, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — using fewer than 10 images speeds up rendering noticeably.

Matching Input to Actions

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

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.

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.

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "combine these images into a 30-second video with background music and text overlays" — concrete instructions get better results.

Max file size is 500MB. Stick to MP4, MOV, JPG, PNG for the smoothest experience.

Export as MP4 for widest compatibility across Google Drive, YouTube, and social platforms.

Common Workflows

Quick edit: Upload → "combine these images into a 30-second video with background music and text overlays" → 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.