Free Video Generations

generate text prompts or images into AI generated videos with this skill. Works with MP4, MOV, PNG, JPG files up to 200MB. content creators, marketers, stude...

Security Scan

The skill's behavior is coherent with a video-generation service, but it sends uploaded media and environment-derived headers to an external API with no known homepage/source and includes metadata that suggests reading local paths — verify the backend and token use before installing.

Purpose & Capability

The name/description (generate videos from text/images) matches the runtime instructions: creating a session, uploading media, using SSE for edits, and exporting MP4s. Requesting a service token (NEMO_TOKEN) is appropriate for this purpose.

Instruction Scope

Instructions stay within video-generation workflows (session creation, upload, SSE, export). However the skill instructs the agent to detect local install paths (e.g., ~/.clawhub/, ~/.cursor/skills/) and to include X-Skill-Platform and other attribution headers on every request, which leaks local-environment info to the remote API. It also instructs polling and state checks and to upload user files up to 200MB — valid for the use case but privacy-sensitive.

Install Mechanism

No install spec and no code files (instruction-only). This has lower disk/write risk. There is nothing being downloaded or extracted by the skill itself.

Credentials

The only declared credential is NEMO_TOKEN (primaryEnv), which is proportional for a hosted video-rendering API. Caveats: SKILL.md also contains metadata listing a config path (~/.config/nemovideo/) not present in registry metadata — a mild inconsistency. The skill will send Authorization: Bearer <NEMO_TOKEN> and environment-derived attribution headers to the remote domain, so any token provided would be transmitted off-host and should be service-specific.

Persistence & Privilege

always is false, no install-time persistence is requested, and autonomous model invocation defaults are unchanged. The skill does not request system-wide configuration changes or permanent presence.

What to consider before installing

This skill appears to do what it says (upload media, create sessions, render videos) but it sends your files and any provided token to https://mega-api-prod.nemovideo.ai — a service with no published homepage or source in the registry. Before installing, consider: 1) Only use a token dedicated to this service (do not reuse AWS/GitHub/other secrets). 2) Avoid uploading sensitive or private media until you confirm the provider's privacy/security posture. 3) Ask the publisher for a homepage or source repo and a privacy policy; absence of these increases risk. 4) Note the skill will detect/install-path info and include it in requests — if you care about leaking environment details, do not install. If the author provides an official domain, documentation, or open-source code, re-evaluation could raise confidence.

Getting Started

Ready when you are. Drop your text prompts or images here or describe what you want to make.

Try saying:

• "generate a short text description of a product demo scene into a 1080p MP4"
• "generate a 15-second video clip from this product description"
• "generating short videos from text or image inputs at no cost for content creators, marketers, students"

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 Generations — Generate Videos from Text or Images

Drop your text prompts or images 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 a short text description of a product demo scene, ask for generate a 15-second video clip from this product description, and about 30-90 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter prompts with clear scene descriptions produce more accurate results.

Matching Input to Actions

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

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: 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: free-video-generations
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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)

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

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.

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 "generate a 15-second video clip from this product description" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms.

Common Workflows

Quick edit: Upload → "generate a 15-second video clip from this product description" → 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.