Free Video Clip Generator

Turn a short product description or a few stock images into 1080p ready-to-share clips just by typing what you need. Whether it's generating short video clip...

Security Scan

The skill's declared purpose (cloud video generation) aligns with the single credential it requests (NEMO_TOKEN) and its runtime instructions; there are minor metadata inconsistencies and the skill will send user media to a third‑party service, so review before sharing sensitive files.

Purpose & Capability

The skill claims to generate/export short video clips and the runtime instructions only reference a single service API (nemovideo.ai) and a single credential (NEMO_TOKEN). Requiring a service token is proportional to the described cloud-rendering capability.

Instruction Scope

SKILL.md directs the agent to create/consume a Bearer token, create sessions, send SSE messages, upload files (via multipart or URL), poll render status, and return download URLs — all expected for a cloud render workflow. Note: uploads may read local file paths when the user asks to upload a file, so the agent will transmit user-supplied media to the nemovideo.ai endpoints.

Install Mechanism

Instruction-only skill (no install spec, no code files). This is low risk from an install perspective because nothing is downloaded or written to disk by an installer.

Credentials

The skill requires a single environment variable (NEMO_TOKEN) which is appropriate for authenticating to the service. However, the SKILL.md frontmatter references a config path (~/.config/nemovideo/) while the registry metadata provided earlier lists no required config paths — this metadata mismatch should be clarified before installation.

Persistence & Privilege

The skill does not request always:true and does not declare system-wide privileges. It instructs the agent to save a session_id for ongoing jobs, which is reasonable for tracking cloud renders; there's no instruction to modify other skills or system-wide configs.

Assessment

This skill appears to be what it says: a cloud-based video generator that needs a service token and will upload any images/files you provide to nemovideo.ai. Before using it, consider: (1) confirm you trust the nemovideo.ai service and its privacy terms (your media will be sent to their servers); (2) you can avoid setting a permanent NEMO_TOKEN in your environment by letting the skill obtain a short anonymous token, or use a disposable token; (3) clarify the metadata mismatch about ~/.config/nemovideo/ with the publisher — the manifest inconsistently lists configPaths; (4) do not submit sensitive or proprietary images/text unless you accept that they'll be transmitted off your machine. If you want higher assurance, ask the skill author for a homepage/source code or documentation and for clarification about where session tokens are stored and how long they are retained.

Getting Started

Send me your text or images and I'll handle the AI video generation. Or just describe what you're after.

Try saying:

• "generate a short product description or a few stock images into a 1080p MP4"
• "create a 30-second video clip from my product photos with background music"
• "generating short video clips from text prompts or images for content creators, marketers, students"

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 Clip Generator — Generate and Export Video Clips

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

Here's a typical use: you send a a short product description or a few stock images, ask for create a 30-second video clip from my product photos with background music, 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 text prompts with clear descriptions produce more accurate clips.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	free-video-clip-generator
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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

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.

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)

Common Workflows

Quick edit: Upload → "create a 30-second video clip from my product photos with background music" → 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 "create a 30-second video clip from my product photos with background music" — 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.