Free Video Generation App

generate text or images into ready-to-share videos with this skill. Works with MP4, MOV, JPG, PNG files up to 200MB. TikTok creators use it for generating sh...

Security Scan

The skill's requests and runtime instructions are generally consistent with a cloud video-rendering integration that needs a single service token, but there are a few small metadata/instruction ambiguities you should note before installing.

Purpose & Capability

Name/description align with the behavior in SKILL.md: it talks to a remote Nemo video API, uploads media, starts render jobs, and returns download URLs. Asking for a single service token (NEMO_TOKEN) is expected for this purpose.

Instruction Scope

Runtime instructions stay within the video-generation domain (create session, run SSE, upload files, poll renders). Minor scope notes: SKILL.md instructs the agent to detect an install platform by checking user paths (~/.clawhub/, ~/.cursor/skills/) and references a config path (~/.config/nemovideo/) — this implies reading filesystem paths beyond just reading the NEMO_TOKEN env var. It also instructs generating and 'saving' anonymous tokens/session_id but doesn't specify where to persist them.

Install Mechanism

Instruction-only skill with no install spec or downloaded code, so it does not write new binaries or archives to disk. This is the lowest-risk install pattern.

Credentials

Only the NEMO_TOKEN is declared and used as the primary credential, which is proportional to a cloud API client. Small ambiguity: SKILL.md's YAML frontmatter lists a config path (~/.config/nemovideo/) not present in the registry metadata, and the instructions say to store the anonymous token/session id — the mechanism/placement for that storage is unspecified.

Persistence & Privilege

Skill is not force-included (always: false) and does not declare elevated platform privileges. It does instruct persistent session/token handling, but that is expected for a remote-rendering client and is not itself privileged.

Assessment

This skill appears to be what it says: a cloud video-renderer that needs a single service token (NEMO_TOKEN) to call nemovideo.ai endpoints and manage sessions. Before installing: 1) Only provide a token you control and that is scoped appropriately (do not reuse high-privilege or unrelated credentials). 2) Ask or confirm where anonymous tokens and session IDs will be stored (in-memory vs written to ~/.config/nemovideo/ or other files) if you care about persistence or local files. 3) Be aware media you upload will be sent to the external API (privacy/PD concerns). 4) The SKILL.md references filesystem paths to detect platform — if you prefer the skill not probe your home directory, ask for that behavior to be removed. If the author or homepage is unknown, consider testing with throwaway media/credentials first or requesting more provenance (official domain, docs, or open-source code) to raise confidence.

Getting Started

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

Try saying:

• "generate a short text prompt or three product images into a 1080p MP4"
• "create a 30-second promotional video from these product photos"
• "generating short videos from text prompts or images without editing skills for TikTok creators"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Free Video Generation App — Generate Videos from Text or Images

Send me your text or images and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a short text prompt or three product images, type "create a 30-second promotional video from these product photos", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter prompts with clear scene descriptions produce more accurate results.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is free-video-generation-app, 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).

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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.

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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 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)

Error Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry once

Common Workflows

Quick edit: Upload → "create a 30-second promotional video from these product photos" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a 30-second promotional video from these product photos" — 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 social platforms.