Free Video Generation Google

Turn a short text description of a product launch scene into 1080p AI generated videos just by typing what you need. Whether it's generating videos from text...

Security Scan

The skill's API usage and single credential (NEMO_TOKEN) are coherent with a video-generation service, but there are a few inconsistencies and a couple of behaviors (filesystem/metadata access, local config write hints, and a misleading name) that don't fully match the declared metadata and should be clarified before use.

Purpose & Capability

The skill claims to generate videos via a remote API and only asks for a single API token (NEMO_TOKEN), which matches that purpose. However the skill name includes 'Google' despite no Google APIs or Google-owned domains being referenced — this is misleading. Also the SKILL.md frontmatter (metadata) lists a config path (~/.config/nemovideo/) even though the registry metadata in the top-level report said 'Required config paths: none' — a metadata mismatch.

Instruction Scope

Runtime instructions include creating anonymous tokens, creating sessions, SSE streaming, multipart uploads (reading user file paths), saving session_id, and reading the skill file's YAML frontmatter to populate attribution headers. The attribution header X-Skill-Platform is determined by checking install paths like ~/.clawhub/ and ~/.cursor/skills/, which implies filesystem checks. These filesystem reads/writes (detecting install path; potentially writing session data or config under ~/.config/nemovideo/) go beyond pure stateless API calls and should be explicit to users.

Install Mechanism

This is an instruction-only skill with no install specification and no code files, so there's nothing to download or execute locally. That is the lowest-risk install pattern.

Credentials

Only one environment variable is required (NEMO_TOKEN) which is proportionate for a service that uses bearer auth. The SKILL.md also documents creating an anonymous token if NEMO_TOKEN is absent. The frontmatter's mention of a config path (~/.config/nemovideo/) appears to imply storing session or config data on disk; that wasn't declared in the top-level registry metadata and should be explained.

Persistence & Privilege

The skill asks to 'Save session_id' and may write or read user files for uploads and detect install paths to set attribution headers. It does not request 'always: true' and is not asking for other service credentials. Still, implicit local persistence (session tokens, session files under ~/.config/nemovideo/) is possible and should be clarified — users may want to know exactly where and how long tokens/session IDs are stored.

What to consider before installing

This skill mostly behaves like a normal remote video-generation integration (it needs a NEMO_TOKEN and talks to mega-api-prod.nemovideo.ai). Before installing: - Verify the API host and vendor: confirm the nemovideo.ai domain and service are legitimate (look for an official homepage or published docs). The skill's name misleadingly includes 'Google' but it does not use Google services. - Ask the author to clarify the metadata mismatch: SKILL.md mentions ~/.config/nemovideo/ but the registry said no config paths — ask whether the skill will write session or token data to disk and where. - Confirm what filesystem checks are performed: the skill will attempt to detect install path for attribution headers; ask whether it accesses other paths or files. - Be cautious when uploading local files; verify uploads go only to the stated API and avoid sending sensitive files. - Prefer using an ephemeral or limited-scope token if possible (the skill supports anonymous tokens). Rotate or revoke tokens if you later stop using the skill. If the maintainer can confirm that the only credential used is NEMO_TOKEN (or ephemeral anonymous tokens), that it only writes session data under an explicit location you approve, and that no other local files are read, the concerns above would be largely resolved.

Getting Started

Share your text prompts and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "generate my text prompts"
• "export 1080p MP4"
• "generate a 30-second video from my"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Free Video Generation Google — Generate Videos from Text Prompts

Send me your text prompts and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a short text description of a product launch scene, type "generate a 30-second video from my script about a new sneaker release", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter and more specific prompts tend to produce more accurate video results.

Matching Input to Actions

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

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

• X-Skill-Source: free-video-generation-google
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 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.

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

Common Workflows

Quick edit: Upload → "generate a 30-second video from my script about a new sneaker release" → 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 "generate a 30-second video from my script about a new sneaker release" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms and devices.