Image Creator Free

create text or images into generated image videos with this skill. Works with JPG, PNG, WEBP, GIF files up to 200MB. content creators use it for creating vid...

Security Scan

The skill's declared purpose (creating videos from images) matches the runtime instructions and required credential (NEMO_TOKEN); nothing indicates clear misdirection, but there are small metadata inconsistencies and privacy implications you should consider before installing.

Purpose & Capability

Name/description, endpoints, and actions all align with a cloud-based image-to-video rendering service. Requesting a single NEMO_TOKEN credential is coherent for an external API. Minor inconsistency: the registry metadata lists no config paths, but the SKILL.md frontmatter declares a config path (~/.config/nemovideo/). This is plausibly for storing anonymous tokens but should be clarified.

Instruction Scope

SKILL.md gives explicit, narrow runtime instructions (check env, obtain anonymous token if absent, create session, upload files, handle SSE and exports). These actions are consistent with the stated purpose. The agent is asked to read the skill's frontmatter and to detect install path to set an X-Skill-Platform header; this requires inspecting local paths and the skill file but is limited in scope. There is no instruction to read unrelated user files or system secrets.

Install Mechanism

Instruction-only skill with no install spec or code files — lowest disk-write risk. The skill will rely on network calls to the external nemovideo API but does not pull or install third-party binaries or archives.

Credentials

Only NEMO_TOKEN (primary credential) and an optional config path are declared, which matches a service-auth model. Small inconsistency: SKILL.md implements an anonymous-token flow when NEMO_TOKEN is absent (POST to /api/auth/anonymous-token), so treating NEMO_TOKEN as strictly required may be misleading. The declared credential is proportionate to the task.

Persistence & Privilege

always is false and the skill does not request permanent/privileged platform presence or modification of other skills. Autonomous invocation is enabled (platform default) but not combined with elevated privileges.

Assessment

This skill will upload whatever images/text you send to a third‑party API (mega-api-prod.nemovideo.ai) for server-side rendering — expect your media to leave your device. The skill expects or will obtain a NEMO_TOKEN; if you supply your own token it grants the skill the same access your token has, so treat it like any API key. Note the registry has no homepage and the owner is an opaque ID; SKILL.md also contains a config path (~/.config/nemovideo/) and an automatic anonymous-token flow, which are minor inconsistencies worth asking the publisher to clarify. Before installing consider: (1) Do you trust the external domain to receive your media? (2) Do you want to provide your own NEMO_TOKEN or allow the skill to request an anonymous token? (3) Ask the publisher for a homepage or source code, and prefer skills from known publishers if you need to protect sensitive images. If you have strict privacy requirements, do not use this skill.

Getting Started

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

Try saying:

• "create three product photos and a brand description into a 1080p MP4"
• "create a short video slideshow from these product images with smooth transitions"
• "creating videos from AI-generated or uploaded images for free for content creators"

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.

Image Creator Free — Create Videos from Images

Send me your text or images and describe the result you want. The AI image generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload three product photos and a brand description, type "create a short video slideshow from these product images with smooth transitions", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: using fewer images per video speeds up generation significantly.

Matching Input to Actions

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

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.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: image-creator-free
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

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.

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 → "create a short video slideshow from these product images 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a short video slideshow from these product images 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.