Image To Online

Turn three product photos or a batch of travel shots into 1080p shareable video files just by typing what you need. Whether it's turning photo collections in...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud-backed photo→video service: it only needs a single service token and sends uploads to the stated API; nothing requested looks unrelated to the described purpose.

Purpose & Capability

Name/description, required env var (NEMO_TOKEN), config path (~/.config/nemovideo/), and the described API endpoints all align with a remote render service. No unrelated cloud credentials or unrelated binaries are requested.

Instruction Scope

Instructions stay largely within photo upload, session management, SSE streaming, and export flows. Two minor scope items to be aware of: (1) runtime asks to read this skill file's YAML frontmatter and to detect install path (~/.clawhub/, ~/.cursor/skills/) to populate an X-Skill-Platform header — both require reading local paths/files (benign for attribution but broader than purely 'upload images'). (2) The skill will POST to an external API and upload user files/URLs (expected for this service).

Install Mechanism

Instruction-only skill with no install spec and no downloads or extracted archives — lowest-risk install surface.

Credentials

Only a single service credential (NEMO_TOKEN) is declared and used. The skill also documents an anonymous-token flow if NEMO_TOKEN is absent; this is coherent with the service and avoids requesting unrelated secrets.

Persistence & Privilege

Skill does not request always:true, does not request system-wide config changes, and does not ask to modify other skills. It may store session tokens in its own session state or config path (~/.config/nemovideo/) which is reasonable for a client of the service.

Assessment

This skill appears to do what it says: it uploads images to nemovideo's API and returns rendered video files. Before installing/using it, consider: (1) Privacy — your images and any metadata will be sent to https://mega-api-prod.nemovideo.ai; avoid uploading sensitive images unless you trust that service. (2) Token behavior — if you don't provide a NEMO_TOKEN the skill will request an anonymous token from the service (100 free credits, temporary). (3) Local reads — the skill may read its own frontmatter and detect install paths (benign but means it will touch paths in your home dir). (4) No other credentials are requested. If you need higher assurance, ask the publisher for a homepage/privacy policy or test first with non-sensitive images.

Getting Started

Share your images and I'll get started on video creation. Or just tell me what you're thinking.

Try saying:

• "convert my images"
• "export 1080p MP4"
• "turn my photos into a shareable"

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 to Online — Convert Photos to Shareable Videos

Send me your images and describe the result you want. The video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload three product photos or a batch of travel shots, type "turn my photos into a shareable video with transitions and music", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: fewer images with longer durations per slide tend to look more polished than rapid-fire slideshows.

Matching Input to Actions

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

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

• X-Skill-Source: image-to-online
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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.

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.

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn my photos into a shareable video with transitions and music" — 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 social platforms.

Common Workflows

Quick edit: Upload → "turn my photos into a shareable video with transitions and music" → 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.