Best Photo To Video Ai

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — turn these photos into a slideshow video with transitions and background m...

⭐ 0· 103·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/best-photo-to-video-ai.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Best Photo To Video Ai" (whitejohnk-26/best-photo-to-video-ai) from ClawHub.
Skill page: https://clawhub.ai/whitejohnk-26/best-photo-to-video-ai
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 best-photo-to-video-ai

ClawHub CLI

Package manager switcher

npx clawhub@latest install best-photo-to-video-ai

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Suspicious

medium confidence

✓

Purpose & Capability

The skill claims to convert photos into videos and its runtime instructions describe uploading images, starting render sessions, polling render status, and returning a download URL — all expected for this purpose. Requesting a single service token (NEMO_TOKEN) is proportional to the described cloud API use.

ℹ

Instruction Scope

Instructions limit actions to authenticating, creating a session, uploading files, streaming SSE for generation, checking credits/state, and triggering exports. They do not request unrelated system files or other env vars. However the skill mandates sending user files (photos/videos/audio) to an external API — a legitimate functional need but also a privacy-exposing action that the user should be aware of.

✓

Install Mechanism

This is an instruction-only skill with no install spec and no code files; nothing is written to disk by the skill itself. That is the lowest install risk.

Credentials

The only declared env var is NEMO_TOKEN which fits the service model. Concerns: the skill will accept an anonymous token created via an API call (short-lived, 7-day), but the SKILL.md frontmatter also lists a configPath (~/.config/nemovideo/) which is not reflected in the registry metadata — mismatched metadata could indicate sloppy packaging or that the skill expects to read/write a local config directory (not declared).

✓

Persistence & Privilege

The skill is not marked always:true and does not request persistent system-wide privileges. It does instruct saving a session_id for jobs, which is normal for job tracking. Autonomous invocation is allowed (platform default) but not in itself a new concern.

What to consider before installing

This skill appears to implement a cloud-based photo→video workflow and asks for a single service token (NEMO_TOKEN) and for you to upload your media to https://mega-api-prod.nemovideo.ai. Before installing or using it: 1) Verify the service owner and see a real homepage/privacy policy/contact info — the skill metadata has no homepage and the publisher is unknown. 2) Be cautious about uploading sensitive photos to an unknown third-party API. 3) Note the SKILL.md frontmatter includes a config path (~/.config/nemovideo/) even though the registry metadata did not — ask the author whether the skill will read/write local config files. 4) Prefer using short-lived or anonymous tokens for testing (the skill supports anonymous tokens), and avoid giving permanent credentials you use elsewhere. 5) If you need stronger assurance, ask the publisher for source code, a privacy policy, or a verifiable homepage; otherwise consider local/offline tools or a known vendor for sensitive content.

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

Runtime requirements

🖼️ Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk97057c13ssa4j8fwj63m9esed854ktg

103downloads

0stars

1versions

Updated 1w ago

v1.0.0

MIT-0

Getting Started

Send me your photos, images and I'll handle the AI video creation. Or just describe what you're after.

Try saying:

"convert five vacation photos in JPG format into a 1080p MP4"
"turn these photos into a slideshow video with transitions and background music"
"turning photo collections into shareable videos for social media creators, marketers"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Best Photo to Video AI — Convert Photos into Shareable Videos

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

Here's a typical use: you send a five vacation photos in JPG format, ask for turn these photos into a slideshow video with transitions and background music, and about 30-60 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — using 5-10 photos gives the best pacing for a short video.

Matching Input to Actions

User prompts referencing best photo to video ai, 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`	`best-photo-to-video-ai`
`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.

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.

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

Common Workflows

Quick edit: Upload → "turn these photos into a slideshow video with transitions and background 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn these photos into a slideshow video with transitions and background 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.

Comments

Loading comments...