Image To Video Finder

v1.0.0

Get matched video results ready to post, without touching a single slider. Upload your images (JPG, PNG, WEBP, BMP, up to 200MB), say something like "find th...

⭐ 0· 61·0 current·0 all-time

by@whitejohnk-26

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for whitejohnk-26/image-to-video-finder.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Image To Video Finder" (whitejohnk-26/image-to-video-finder) from ClawHub.
Skill page: https://clawhub.ai/whitejohnk-26/image-to-video-finder
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install image-to-video-finder

ClawHub CLI

Package manager switcher

npx clawhub@latest install image-to-video-finder

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

high confidence

✓

Purpose & Capability

Name/description, declared env var (NEMO_TOKEN), and declared config path (~/.config/nemovideo/) align with a cloud video‑matching service. No unrelated credentials, binaries, or install steps are requested.

ℹ

Instruction Scope

SKILL.md instructs the agent to POST to the service endpoints, upload user images, create an anonymous token if none is provided, open sessions, stream SSE responses, and poll render status. These actions are consistent with the stated purpose but are privacy‑sensitive because all images and session metadata are sent to the external API; the skill also instructs storing a session_id for subsequent requests.

✓

Install Mechanism

Instruction-only skill with no install spec or code files — nothing is written to disk by an installer. Lowest install risk.

✓

Credentials

Only a single credential (NEMO_TOKEN) is declared as required and used for API calls. The skill will auto‑obtain an anonymous token if NEMO_TOKEN is not set, which is consistent with the described flow. The declared config path matches the service and is proportionate.

✓

Persistence & Privilege

always is false and the skill does not request elevated platform privileges. It asks to store session_id for continuity, which is reasonable for a session-based cloud render workflow and limited in scope.

Assessment

This skill appears to do what it claims, but it routes all uploaded images and session metadata to a third‑party API (https://mega-api-prod.nemovideo.ai). Before installing or using it: 1) Do not upload sensitive or private images — treat uploads as sent to an external service. 2) If you care about linkage, prefer providing your own NEMO_TOKEN (if you obtain one from the vendor) rather than relying on the anonymously generated token. 3) Ask the publisher for a homepage/privacy policy and confirmation of data retention/usage, since the skill metadata has no source or homepage. 4) If your platform policy restricts outbound network calls, confirm this endpoint is allowed. If you want higher assurance, request the vendor's documentation or a signed privacy/terms statement before using production or sensitive content.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🔍 Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk97e1bybrkee8d98vjm1gqfhen84y8ej

61downloads

0stars

1versions

Updated 1w ago

v1.0.0

MIT-0

Getting Started

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

Try saying:

"find my images"
"export 1080p MP4"
"find the video this image is"

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.

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.
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 Video Finder — Find Videos From Images

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

A quick example: upload a screenshot from a movie scene, type "find the video this image is from", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: cropped or watermarked images may reduce match accuracy — use the clearest frame possible.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
`/api/tasks/me/with-session/nemo_agent`	POST	Start a new editing session. Body: `{"task_name":"project","language":"<lang>"}`. Returns `session_id`.
`/run_sse`	POST	Send a user message. Body includes `app_name`, `session_id`, `new_message`. Stream response with `Accept: text/event-stream`. Timeout: 15 min.
`/api/upload-video/nemo_agent/me/<sid>`	POST	Upload a file (multipart) or URL.
`/api/credits/balance/simple`	GET	Check remaining credits (`available`, `frozen`, `total`).
`/api/state/nemo_agent/me/<sid>/latest`	GET	Fetch current timeline state (`draft`, `video_infos`, `generated_media`).
`/api/render/proxy/lambda`	POST	Start export. Body: `{"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}`. Poll status every 30s.

Accepted file types: 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-finder`
`X-Skill-Version`	frontmatter `version`
`X-Skill-Platform`	auto-detect: `clawhub` / `cursor` / `unknown` from install path

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "find the video this image is from" — concrete instructions get better results.

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

PNG images retain more detail than JPG and tend to produce more accurate matches.

Common Workflows

Quick edit: Upload → "find the video this image is from" → 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.

Comments

Loading comments...