Image To Free

Turn three product photos or a landscape image into 1080p free video clips just by typing what you need. Whether it's converting static images into downloada...

Security Scan

Instructions, endpoints, and the single requested credential (NEMO_TOKEN) line up with the skill's stated function of converting images to short videos; nothing in the skill appears disproportionate or unrelated to that purpose.

Purpose & Capability

The skill's name and description match the actions described in SKILL.md: it uploads images and calls a nemo video rendering backend. The only minor inconsistency is metadata: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier stated no required config paths. This is likely a small metadata mismatch rather than a functional mismatch.

Instruction Scope

Runtime instructions are narrowly scoped to talking to the nemovideo API: obtain (or use) a NEMO_TOKEN, create a session, upload files, stream SSE responses, poll render status, and return a download URL. These actions are expected for a cloud-based image→video service. Two points to note: (1) the instructions ask the agent to auto-detect platform from the install path (requires access to agent/install path info), and (2) the skill instructs storing session_id and token for subsequent calls. Both are reasonable for this workflow but are worth noting because they imply reading/writing small local state and access to runtime path info.

Install Mechanism

No install spec and no code files — instruction-only skill. This is the lowest install risk: nothing is downloaded or written by an installer step.

Credentials

The skill declares a single credential (NEMO_TOKEN) which directly corresponds to the remote API it uses. It can also generate an anonymous token by calling the provider's anonymous-token endpoint if NEMO_TOKEN is not set, which is consistent with a free-tier flow. The minor discrepancy between 'no required config paths' in registry metadata and the SKILL.md frontmatter listing ~/.config/nemovideo/ should be clarified but does not materially expand credential access.

Persistence & Privilege

always:false and no install steps; the skill persists session tokens in-memory or its own session storage as part of normal operation. It does not request system-wide changes or elevated privileges.

Assessment

This skill appears to do what it says: it uploads images to a third-party service (mega-api-prod.nemovideo.ai) and returns rendered video URLs. Before installing: (1) be aware your images and any embedded metadata will be sent to that external service — avoid uploading sensitive images, secrets, or identifiable personal data; (2) the skill may generate and store a short-lived anonymous token if you don't provide NEMO_TOKEN; (3) confirm you trust the nemovideo endpoint and its privacy/terms if that matters to you; (4) the SKILL.md frontmatter references a config path (~/.config/nemovideo/) while registry metadata said none — if you require strict guarantees about local file access, ask the publisher to clarify. Otherwise this skill is internally coherent and proportionate to its advertised purpose.

Getting Started

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

Try saying:

• "convert three product photos or a landscape image into a 1080p MP4"
• "turn this image into a free downloadable video clip"
• "converting static images into downloadable video files at no cost for social media creators"

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.

Image to Free — Convert Images to Free Videos

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

Here's a typical use: you send a three product photos or a landscape image, ask for turn this image into a free downloadable video clip, and about 20-40 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — smaller image files process faster and reduce wait time significantly.

Matching Input to Actions

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

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

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

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.

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 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 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 this image into a free downloadable video clip" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms and devices.

Common Workflows

Quick edit: Upload → "turn this image into a free downloadable video clip" → Download MP4. Takes 20-40 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.