Free Video Image Generation

v1.0.0

Get AI-generated video clips ready to post, without touching a single slider. Upload your text prompts (JPG, PNG, WEBP, MP4, up to 200MB), say something like...

0· 40·0 current·0 all-time
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill's name/description (video generation) matches the declared primary credential (NEMO_TOKEN) and the documented API endpoints at mega-api-prod.nemovideo.ai. No unrelated credentials or binaries are requested.
Instruction Scope
SKILL.md instructs only service-related actions: create/use a session, upload files, stream SSE, poll export status. It does require network calls to the stated backend and will upload user-provided files and prompts there, which is expected for this purpose. It does not instruct reading arbitrary system files or unrelated environment variables.
Install Mechanism
This is an instruction-only skill with no install spec or code files—no packages are downloaded or written to disk by the skill itself.
Credentials
Only one env var is required (NEMO_TOKEN), which is proportionate. The metadata also lists a config path (~/.config/nemovideo/) even though SKILL.md does not reference reading it — this is a minor inconsistency (metadata claims possible config use). The skill also documents obtaining an anonymous token from the backend if no NEMO_TOKEN is present; that behavior is coherent but means the agent will reach out to the external service to get a temporary credential.
Persistence & Privilege
The skill is not always-included, does not request elevated or cross-skill config changes, and has no install-time persistence.
Scan Findings in Context
[no_findings] expected: No code files were present so the regex scanner had nothing to analyze. The security surface is the SKILL.md instructions and declared metadata.
Assessment
This skill will send your prompts and any uploaded files to https://mega-api-prod.nemovideo.ai and will either use a provided NEMO_TOKEN or request an anonymous token from that service. Before installing or providing credentials: 1) ensure you trust that backend (privacy, retention, and who can access uploaded media); 2) avoid providing highly privileged or production tokens—use a scoped or disposable token if possible; 3) note the metadata mentions ~/.config/nemovideo/ even though the instructions don't use it—be cautious if the agent asks to read local config files; and 4) because this is instruction-only, the agent will perform network calls at runtime (no local binaries are installed).

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🎬 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk971p3kjtpxxapyrny7k930w1185brkm
40downloads
0stars
1versions
Updated 21h ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

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

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

  • Generate a UUID as client identifier
  • POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
  • The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Free Video Image Generation — Generate Videos from Images or Text

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

Say you have a written description of a sunset over mountains and want to generate a 10-second video clip from my text prompt showing a city timelapse at night — the backend processes it in about 30-90 seconds and hands you a 1080p MP4.

Tip: shorter and more specific prompts tend to produce more accurate results.

Matching Input to Actions

User prompts referencing free video image generation, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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:

HeaderValue
X-Skill-Sourcefree-video-image-generation
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-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 saysYou 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

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate limit (1 token/client/7 days)Retry in 30s once

Common Workflows

Quick edit: Upload → "generate a 10-second video clip from my text prompt showing a city timelapse at night" → Download MP4. Takes 30-90 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 10-second video clip from my text prompt showing a city timelapse at night" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms and devices.

Comments

Loading comments...