Video Generator Free Google

Turn a short text description of a product launch into 1080p ready-to-share videos just by typing what you need. Whether it's generating short videos from te...

Security Scan

The skill's network actions and credential use mostly match a video-rendering service, but a few unexplained behaviors (requested config path, automatic anonymous-token creation/storage, and install-path inspection for attribution) are disproportionate or ambiguous and warrant caution.

Purpose & Capability

The skill's name and description (AI cloud video generation) align with the single required credential NEMO_TOKEN and the listed API endpoints. However the frontmatter also declares a required config path (~/.config/nemovideo/) that the runtime instructions do not meaningfully explain or use, which is an unexplained access request.

Instruction Scope

SKILL.md instructs the agent to check NEMO_TOKEN, and if absent to automatically POST to an anonymous-token endpoint, create sessions, upload user files, stream SSE responses, and poll status — all expected for this service. Concerns: the skill will automatically create anonymous credentials (using generated UUIDs) and store the returned token/session for future calls; it also requires detecting the agent install path to set an attribution header (this requires filesystem inspection). The doc instructs not to show raw tokens, which is reasonable, but automatic credential creation and implicit storage without a clear storage location or explicit user consent is surprising and could be abused.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. All runtime behavior is via HTTP requests and in-memory/session-state; nothing is written by an install step.

Credentials

Only NEMO_TOKEN is declared as required (primary credential), which fits a third-party video API. But the metadata's declared config path (~/.config/nemovideo/) appears unnecessary given the runtime instructions, and the skill's behavior of auto-obtaining tokens means it will act without a user-provided secret. It's unclear whether tokens/session IDs are persisted to disk (and where), which increases the risk surface.

Persistence & Privilege

always is false and the skill does not request elevated platform privileges. Autonomous invocation is allowed (platform default). There is no evidence it modifies other skill configurations or system-wide agent settings.

What to consider before installing

This skill mostly behaves like a normal cloud video-generation integration, but it will: (1) make network calls to https://mega-api-prod.nemovideo.ai, (2) automatically request an anonymous token if you don't provide NEMO_TOKEN, and (3) store a session_id/token for future requests. Before installing, consider: - Provide your own NEMO_TOKEN if you don't want the skill to generate anonymous credentials on your behalf. - Ask where tokens/session IDs are stored (in-memory only vs. written to ~/.config/nemovideo/) and whether the skill will create files on disk. - Be comfortable with the external host (mega-api-prod.nemovideo.ai) seeing uploads of any media you send. - If you need stricter guarantees, decline automatic token creation and restrict the skill to use a token you supply. Additional info that would raise confidence: explicit statements in the skill about where/if tokens are persisted, what exactly is written to disk (if anything), and why the config path in metadata is required.

Getting Started

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

Try saying:

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

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 Generator Free Google — Generate Videos from Text or Images

This tool takes your text prompts 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 a short text description of a product launch and want to generate a 30-second video from my product description with background music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter text prompts with clear details produce more accurate video results.

Matching Input to Actions

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

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-generator-free-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.

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

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)

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 product description with background music" — concrete instructions get better results.

Max file size is 200MB. 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 → "generate a 30-second video from my product description with background music" → 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.