Image To Video Gratis

convert static images into animated video clips with this skill. Works with JPG, PNG, WEBP, GIF files up to 200MB. social media creators use it for convertin...

Security Scan

The skill's runtime instructions mostly match an image→video service, but metadata mismatches, an unknown external API host, and unclear handling of tokens/configuration make the package internally inconsistent and worth caution.

Purpose & Capability

The declared purpose (convert images to videos) aligns with the runtime instructions (upload, render, download). The single required env var NEMO_TOKEN is plausible. However the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/) that is not reflected in the registry's required config paths — this mismatch is unexplained and reduces confidence.

Instruction Scope

Instructions explicitly send user images and metadata to a third‑party API (mega-api-prod.nemovideo.ai), request/refresh tokens via an anonymous-token endpoint, and direct the agent to save session_id. These are expected for a cloud render service. The doc does not specify where session_id or tokens are stored (in-memory vs disk) and instructs auto-detection of platform from install path (may require filesystem inspection), which is not fully scoped or documented.

Install Mechanism

No install spec and no code files — instruction-only — so nothing is written to disk or downloaded by the skill itself. This minimizes install-time risk.

Credentials

Only NEMO_TOKEN is required, which is proportionate. But SKILL.md metadata also lists a config path (~/.config/nemovideo/) that would grant access to a user config directory; the registry metadata earlier lists no required config paths — the inconsistency is suspicious. The skill will upload user files to an external, unverified domain; users should consider privacy implications.

Persistence & Privilege

always:false and user-invocable:true. The skill does ask to 'save session_id' but does not demand permanent system-wide privileges or modifications to other skills. No automatic always-enabled privilege is requested.

What to consider before installing

This skill is plausible for converting images to video, but exercise caution before installing: 1) The package has no source or homepage and the API host (mega-api-prod.nemovideo.ai) is unverified — consider whether you trust sending images to that domain. 2) There is a metadata mismatch: the SKILL.md mentions ~/.config/nemovideo/ while the registry metadata lists no config paths — ask the author to clarify where session tokens are stored and whether the skill will read/write your home config. 3) Prefer using the anonymous-token flow (creates short-lived token) rather than setting a persistent NEMO_TOKEN in your environment; treat any permanent token like a secret. 4) If you have sensitive images, do not use this skill until you confirm the service's privacy policy and retention rules. 5) If possible, request the skill's source or run it in an isolated/testing agent environment first. If the author cannot explain the config path discrepancy and data handling, avoid installing.

Getting Started

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

Try saying:

• "convert three product photos in JPG format into a 1080p MP4"
• "turn my photos into a 15-second video with smooth transitions"
• "converting still photos into shareable video content for social media 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.

Image to Video Gratis — Convert Photos into Videos Free

This tool takes your static images 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 in JPG format and want to turn my photos into a 15-second video with smooth transitions — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: using fewer images speeds up processing and keeps the video focused.

Matching Input to Actions

User prompts referencing image to video gratis, 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.

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

Header	Value
X-Skill-Source	image-to-video-gratis
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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.

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

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.

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 "turn my photos into a 15-second video with smooth transitions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across all platforms.

Common Workflows

Quick edit: Upload → "turn my photos into a 15-second video with smooth transitions" → Download MP4. Takes 30-60 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.