Video Generator Freepik

Turn three product photos from a Freepik download into 1080p animated video clips just by typing what you need. Whether it's generating short videos from Fre...

Security Scan

The skill mostly matches its stated purpose (upload images → cloud-rendered videos) but has an unexplained request to access a user config path and inconsistent metadata, so you should verify details before installing.

Purpose & Capability

Name/description and runtime instructions align: the skill uploads images and drives a cloud render API, and it requires a single service token (NEMO_TOKEN). However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) that would let the skill read local Nemo client state, while the registry metadata for the skill omitted any required config paths — an inconsistency that should be explained.

Instruction Scope

Instructions are explicit about calling the nemovideo backend (session creation, SSE streaming, upload, export). They also describe generating an anonymous token if NEMO_TOKEN is absent and instruct the agent to derive headers from install/config paths. The actions described stay within the stated goal, but the guidance to inspect install paths and (per frontmatter) config files broadens scope beyond simple API calls and could expose local credentials or config.

Install Mechanism

There is no install spec and no code files — the skill is instruction-only, so it doesn't download or install third-party packages. That is lower risk.

Credentials

Only NEMO_TOKEN is declared (appropriate for a cloud video service). The concern is the SKILL.md's frontmatter mentioning ~/.config/nemovideo/ (a config path that would plausibly contain credentials or tokens) while the registry metadata lists no required config paths. Asking to read a local config directory is disproportionate to the minimal token requirement unless the skill explicitly needs to reuse an existing Nemo client token — the registry should declare that.

Persistence & Privilege

always:false and no install-time persistence are appropriate. The skill keeps an in-session session_id but does not request elevated or permanent presence.

What to consider before installing

This skill appears to do what it says (upload images and call a nemo-video cloud API), but two things to check before installing: (1) confirm why the skill's SKILL.md references ~/.config/nemovideo/ — does it need to read local config or stored tokens? The registry metadata should explicitly declare any config paths it will access; ask the publisher to clarify or remove that requirement. (2) Verify the API domain (mega-api-prod.nemovideo.ai) is legitimate and that you trust Nemo Video; if you prefer, provide your own NEMO_TOKEN instead of letting the skill request an anonymous token. Don't install if you don't want a skill that may read ~/.config/nemovideo/ or contact that external API.

Getting Started

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

Try saying:

• "generate three product photos from a Freepik download into a 1080p MP4"
• "turn these Freepik images into a 15-second animated promo video"
• "generating short videos from Freepik stock images for designers and marketers"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Video Generator Freepik — Generate Videos from Freepik Images

This tool takes your images or prompts and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have three product photos from a Freepik download and want to turn these Freepik images into a 15-second animated promo video — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: using fewer images per video speeds up generation noticeably.

Matching Input to Actions

User prompts referencing video generator freepik, 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 video-generator-freepik, 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).

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.

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn these Freepik images into a 15-second animated promo video" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms.

Common Workflows

Quick edit: Upload → "turn these Freepik images into a 15-second animated promo video" → 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.