Video Editor With Ai Image

v1.0.0

Skip the learning curve of professional editing software. Describe what you want — combine these images into a smooth video with transitions and background m...

0· 50·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

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

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Video Editor With Ai Image" (whitejohnk-26/video-editor-with-ai-image) from ClawHub.
Skill page: https://clawhub.ai/whitejohnk-26/video-editor-with-ai-image
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 video-editor-with-ai-image

ClawHub CLI

Package manager switcher

npx clawhub@latest install video-editor-with-ai-image
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description claim a cloud AI image→video editor and the SKILL.md exclusively describes calls to a remote rendering API, session creation, uploads, and exports. The sole credential requested (NEMO_TOKEN) is appropriate for a hosted service.
Instruction Scope
Instructions describe reading NEMO_TOKEN from environment (or obtaining an anonymous token via the service's auth endpoint), creating sessions, uploading media, using SSE for generation, polling render status, and returning download URLs. These actions are within the stated scope, but they will upload user media to an external server and require the agent to perform network requests; the SKILL explicitly instructs not to expose tokens in output.
Install Mechanism
There is no install spec and no code files — the skill is instruction-only, so nothing is downloaded or written to disk during install.
Credentials
Only NEMO_TOKEN is declared/used which is proportionate. Minor inconsistency: the SKILL.md frontmatter metadata references a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — this is a mismatch to flag. The skill also supports auto-creating an anonymous token if none is present, so it does not strictly require a pre-provided secret.
Persistence & Privilege
always:false and default autonomous invocation are set (normal). The skill's instructions keep session IDs for requests but do not request persistent system-wide privileges, nor do they modify other skills or system configs.
Assessment
This skill appears to do what it claims: it uploads images/video to a remote backend (mega-api-prod.nemovideo.ai) and uses a NEMO_TOKEN to authenticate. Before installing/using it, consider the following: - Privacy: media you upload will be sent to a third-party service; do not upload sensitive or private content unless you trust the service and its terms/privacy policy. - Tokens: the skill will look for NEMO_TOKEN and will obtain an anonymous token if none is set (100 free credits, 7-day expiry). Decide whether you prefer to create/manage your own account token rather than rely on an anonymous one. - Config path mismatch: the SKILL.md mentions ~/.config/nemovideo/ in metadata though the registry listing did not — confirm whether the skill will read/write that path if you are concerned about local configuration files. - Headers and attribution: the skill requires custom headers (X-Skill-Source/Version/Platform); this is normal but these headers will be sent with requests to the service. - Audit outbound traffic: if you need assurance, monitor network calls or review the service's privacy/retention policy; request explicit confirmation from the skill before uploading any file. Overall, nothing indicates misdirection or hidden capabilities, but the usual caution about uploading data to external services applies.

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

Runtime requirements

🖼️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk97ez2sd1nqeajn5208f4tadpn85j16v
50downloads
0stars
1versions
Updated 2d ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "create my images or video clips"
  • "export 1080p MP4"
  • "combine these images into a smooth"

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.

Video Editor with AI Image — Turn Images into Videos

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

A quick example: upload five product photos in JPG format, type "combine these images into a smooth video with transitions and background music", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: using images with consistent aspect ratios produces smoother transitions.

Matching Input to Actions

User prompts referencing video editor with ai image, aspect ratio, text overlays, or audio tracks get routed to the corresponding action via keyword and intent classification.

User says...ActionSkip 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.

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

Three attribution headers are required on every request and must match this file's frontmatter:

HeaderValue
X-Skill-Sourcevideo-editor-with-ai-image
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

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.

Error Handling

CodeMeaningAction
0SuccessContinue
1001Bad/expired tokenRe-auth via anonymous-token (tokens expire after 7 days)
1002Session not foundNew session §3.0
2001No creditsAnonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001Unsupported fileShow supported formats
4002File too largeSuggest compress/trim
400Missing X-Client-IdGenerate Client-Id and retry (see §1)
402Free plan export blockedSubscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429Rate limit (1 token/client/7 days)Retry in 30s once

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

SSE Event Handling

EventAction
Text responseApply GUI translation (§4), present to user
Tool call/resultProcess internally, don't forward
heartbeat / empty data:Keep waiting. Every 2 min: "⏳ Still working..."
Stream closesProcess 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.

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 → "combine these images into a smooth 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 "combine these images into a smooth video with transitions and background music" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.

Comments

Loading comments...