Nano Banana Video Generator Free

Turn a short text description of a banana character doing tricks into 720p animated video clips just by typing what you need. Whether it's generating short f...

Security Scan

The skill's declared purpose (text→video) mostly matches its instructions, but there are inconsistencies (hidden metadata vs registry), an unknown backend domain, automatic anonymous token creation/storage, and guidance to hide token values — together these warrant caution before installing.

Purpose & Capability

The skill claims to generate short videos from text and all runtime instructions are about calling a remote video-rendering API — that aligns with the name/description. However the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that the registry summary did not declare, which is an internal inconsistency and suggests the skill may expect to read/write a local config directory it didn't declare in the manifest.

Instruction Scope

Instructions direct the agent to auto-create an anonymous token by POSTing to https://mega-api-prod.nemovideo.ai and to store a session_id and token for subsequent calls. It also instructs not to display API responses or token values to the user. While creating an anonymous token for a cloud service is plausible, automatic network activity and explicit instruction to hide tokens increases risk: the skill could upload user files or arbitrary local paths if misused, and the guidance to suppress raw responses hampers auditing. The SKILL.md also asks the agent to 'auto-detect' platform from install path (implying filesystem access).

Install Mechanism

This is an instruction-only skill with no install steps or bundled code, so nothing is written to disk by the skill itself. That lowers supply-chain risk.

Credentials

The only required environment variable is NEMO_TOKEN, which is reasonable for a cloud API. However the skill instructs the agent to generate and store a token automatically if NEMO_TOKEN is not present, and explicitly tells the agent not to surface token values to the user. The requested scope (one token) is proportionate to the stated purpose, but the token-generation-and-hiding behavior is unusual and worth scrutiny.

Persistence & Privilege

The skill does not request always:true and does not declare elevated platform privileges. It does instruct storing a session_id and token for subsequent requests; this is normal for session-based APIs but combined with the auto-create-and-hide behavior it increases the chance of persistent tokens being created without a clear user consent flow.

What to consider before installing

Before installing: (1) Verify the backend domain (mega-api-prod.nemovideo.ai) and ask the author for a homepage or source — no homepage/source is provided. (2) Ask how/where the NEMO_TOKEN and session_id will be stored and how you can revoke/delete them. The SKILL.md tells the agent to auto-create an anonymous token and to hide raw API responses — insist on an explicit consent prompt before the agent makes network calls or creates tokens. (3) Be cautious about uploading local files: only upload files you intend to share; confirm the skill will not access arbitrary filesystem paths. (4) If you need stronger assurance, request the skill's source or a published security/privacy policy, or only use a sandboxed/ephemeral environment. If you proceed, monitor and revoke any tokens after testing.

Getting Started

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

Try saying:

• "generate my text prompts"
• "export 720p MP4"
• "generate a short animated nano banana"

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.

Nano Banana Video Generator Free — Generate Animated Videos From Text

This tool takes your text prompts and runs AI video generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a short text description of a banana character doing tricks and want to generate a short animated nano banana video from my description for free — the backend processes it in about 30-60 seconds and hands you a 720p MP4.

Tip: shorter and more specific prompts produce cleaner results faster.

Matching Input to Actions

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

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)

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 short animated nano banana video from my description for free" → 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 "generate a short animated nano banana video from my description for free" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.