Free Video Generation Automatic

generate text or images into auto-generated MP4 videos with this skill. Works with MP4, MOV, PNG, JPG files up to 200MB. content creators, marketers, small b...

Security Scan

The skill's requests and runtime instructions are internally consistent with a cloud video-generation integration: it needs a single service token, talks only to a single external API, and has no installable code — but it will perform network calls and persist session/token state, so review data-privacy implications before using.

Purpose & Capability

Name/description (auto-generating MP4s on cloud GPUs) match the declared requirement for a single service token (NEMO_TOKEN) and a service-specific config path (~/.config/nemovideo/). There are no extraneous environment variables or unrelated binaries requested.

Instruction Scope

SKILL.md instructs the agent to obtain/refresh an anonymous token, create sessions, upload files, stream SSE results, poll render status, and store session_id and token for subsequent calls. Those actions are expected for a cloud rendering service. The doc also instructs the agent to hide raw API responses and token values from the user — a plausible UX/information-hiding guideline but worth noting because it reduces visible transparency during setup and error handling.

Install Mechanism

Instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. This minimizes installation risk; runtime network calls are the primary surface.

Credentials

Only one credential (NEMO_TOKEN) is required and is directly relevant to the stated purpose. The metadata also lists a service-specific config path (~/.config/nemovideo/), which is reasonable for persisting tokens/sessions but does imply the skill may read/write files under the user's home directory for state persistence.

Persistence & Privilege

Skill is user-invocable and not forced-always; it requests to store a session_id and to persist/use a NEMO_TOKEN but does not request elevated system privileges or to modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) but not combined with other high-risk requests.

Assessment

This skill appears to do what it claims: it will make network requests to mega-api-prod.nemovideo.ai, upload your files, and store a short-lived anonymous token/session state so renders can be produced. Before installing, consider: 1) privacy: uploaded media may be retained by the service—check the provider's retention and deletion policy; 2) visibility: the skill's instructions tell the agent not to show raw API responses or token values, so errors and token exchanges may be hidden from you; 3) persistence: the skill may write state under ~/.config/nemovideo/ (or similar) to keep tokens/sessions—confirm where and how long tokens are stored; 4) network egress: the skill will perform outbound HTTPS requests and may auto-obtain a token on first use; if you need strict control over outbound traffic, do not enable it or provide an explicit NEMO_TOKEN instead of allowing anonymous creation; and 5) billing/limits: anonymous tokens are described as limited (free credits, 7-day expiry) and some errors require registration/upgrading. If you want higher assurance, ask the publisher for a privacy/data-retention statement and for explicit details on where tokens and session data are persisted.

Getting Started

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

Try saying:

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

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.

Free Video Generation Automatic — Generate Videos Automatically from Prompts

Drop your text or images in the chat and tell me what you need. I'll handle the automatic video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a short product description and three product photos, ask for generate a 30-second promotional video from my text and images automatically, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter text prompts with clear instructions produce more accurate results faster.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is free-video-generation-automatic, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise 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 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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 30-second promotional video from my text and images automatically" — 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 and devices.

Common Workflows

Quick edit: Upload → "generate a 30-second promotional video from my text and images automatically" → 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.