Free Free Image

Turn a search query for nature background photos into 1080p image-based videos just by typing what you need. Whether it's turning free stock images into vide...

Security Scan

The skill's declared purpose (turn images into short videos via a cloud backend) matches most of its instructions, but there are inconsistencies (metadata vs registry) and a few implementation details that warrant caution before installing.

Purpose & Capability

The skill claims to convert images to 1080p videos using a cloud rendering backend and only requires a NEMO_TOKEN — that is broadly coherent. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata says no required config paths, creating an inconsistency about whether the skill will read/write a local config directory.

Instruction Scope

Runtime instructions tell the agent to check for NEMO_TOKEN, otherwise obtain an anonymous token by POSTing to https://mega-api-prod.nemovideo.ai and then use that token for session creation, uploading files (multipart or URL), SSE message streaming, and polling render status. These actions are consistent with the stated purpose, but they involve transmitting user files and session tokens to an external, unverified API and may read local files (uploads) and potentially a local config path (per frontmatter). The SKILL.md also requests auto-detection of an install path for X-Skill-Platform, which could require reading environment/agent paths.

Install Mechanism

Instruction-only skill with no install spec or code files — nothing will be written to disk by an installer. This minimizes supply-chain risk, but runtime network calls will occur.

Credentials

Only NEMO_TOKEN is declared as required (primary credential), which fits the cloud API usage. The SKILL.md also describes acquiring an anonymous NEMO_TOKEN itself. The frontmatter includes a configPaths entry (~/.config/nemovideo/) not declared in the registry, which could imply local storage/access to credentials or state; that is not justified by the registry metadata and is a proportionality concern.

Persistence & Privilege

always:false and autonomous invocation defaults are normal. The skill instructs keeping session_id for operations and may store or reuse tokens (implied by the config path in frontmatter). There is no explicit request to modify other skills or system-wide settings.

What to consider before installing

This skill appears to do what it says (upload images to a cloud service and return videos), but proceed carefully: 1) Expect your images to be uploaded to https://mega-api-prod.nemovideo.ai — do not install if you cannot accept that external processing. 2) The SKILL.md implies it may read/write ~/.config/nemovideo/ (registry metadata disagrees) — ask the publisher how/where tokens and session data are stored before installing. 3) If you prefer not to let the skill request an anonymous token on your behalf, provide your own NEMO_TOKEN only after verifying the service and its privacy/retention policy. 4) The skill's source and homepage are unknown; prefer skills with a verifiable publisher and documentation. If you want to proceed, test with non-sensitive images and monitor network activity or audit the agent's stored config to confirm where tokens and session_ids are kept.

Getting Started

Share your images and I'll get started on free image sourcing. Or just tell me what you're thinking.

Try saying:

• "convert my images"
• "export 1080p MP4"
• "find and use a free stock"

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.

Free Image — Convert Free Images to Video

This tool takes your images and runs free image sourcing through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a search query for nature background photos and want to find and use a free stock image as a video background — the backend processes it in about 20-40 seconds and hands you a 1080p MP4.

Tip: higher resolution images produce sharper video output.

Matching Input to Actions

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

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 → "find and use a free stock image as a video background" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "find and use a free stock image as a video background" — 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.