Ai Photo Video

v1.0.0

Get animated photo videos ready to post, without touching a single slider. Upload your images or photos (JPG, PNG, HEIC, WEBP, up to 200MB), say something li...

⭐ 0· 107·0 current·0 all-time

by@francemichaell-15

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for francemichaell-15/ai-photo-video.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Ai Photo Video" (francemichaell-15/ai-photo-video) from ClawHub.
Skill page: https://clawhub.ai/francemichaell-15/ai-photo-video
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 ai-photo-video

ClawHub CLI

Package manager switcher

npx clawhub@latest install ai-photo-video

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

medium confidence

✓

Purpose & Capability

Name/description (convert photos to short videos) align with required artifact: a single service credential (NEMO_TOKEN), API endpoints for upload/render, and a config path for session state. The declared primaryEnv (NEMO_TOKEN) is appropriate for a cloud rendering service. The skill does not request unrelated cloud or system credentials.

ℹ

Instruction Scope

SKILL.md instructs the agent to obtain or use NEMO_TOKEN, create sessions, upload files, stream SSE events, poll render status, and save session_id. It also references detection of install path to set X-Skill-Platform and a config path (~/.config/nemovideo/) for state. These actions are expected for the stated purpose, but the agent will upload user media to an external domain (mega-api-prod.nemovideo.ai) — users should expect their images/audio to leave their machine. The skill does not instruct reading unrelated files or other environment variables.

✓

Install Mechanism

No install spec or code files are included (instruction-only), so nothing is written to disk by an installer. This is the lowest-risk install pattern.

✓

Credentials

Only a single token (NEMO_TOKEN) is declared and used as the bearer token for API calls. That is proportionate for a hosted rendering API. The skill's instructions also support generating an anonymous token via an anonymous-token endpoint (ephemeral). No unrelated secrets or multiple tokens are requested.

✓

Persistence & Privilege

always is false and autonomous invocation is allowed (platform default). The skill references storing session_id and possibly config under ~/.config/nemovideo/, which matches the declared configPaths; this is reasonable for saving session state and does not attempt to modify other skills or system-wide settings.

Assessment

This skill appears coherent for a cloud photo→video service, but installing it will cause your uploaded images/audio to be sent to the external domain (mega-api-prod.nemovideo.ai). Before using it: 1) Verify the service/source if you need confidentiality — there's no homepage or publisher info in the registry metadata. 2) Prefer the anonymous-token flow if you don't want to bind a long-lived account token. 3) Do not reuse sensitive credentials as NEMO_TOKEN. 4) Understand that session IDs and uploaded media may be stored on the provider's servers. If you need higher assurance, ask the author for a homepage, privacy policy, or official SDK/ docs before proceeding.

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

Runtime requirements

🖼️ Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk979awrb18tnt6hy1aybyzgg3d855fxz

107downloads

0stars

1versions

Updated 1w ago

v1.0.0

MIT-0

Getting Started

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

Try saying:

"convert my images or photos"
"export 1080p MP4"
"turn these photos into a 30-second"

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.

AI Photo Video — Convert Photos Into Shareable Videos

This tool takes your images or photos and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have five product photos in JPG format and want to turn these photos into a 30-second slideshow video with music and transitions — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: using 5-10 photos gives the best pacing for short-form videos.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is ai-photo-video, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise 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.

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn these photos into a 30-second slideshow video with music and transitions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms.

Common Workflows

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

Comments

Loading comments...