← Back to Skills Marketplace
mhogan2013-9

Image To Video Honor 400

by mhogan2013-9 · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
62
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install image-to-video-honor-400
Description
convert images into animated photo videos with this skill. Works with JPG, PNG, HEIC, WEBP files up to 200MB. Honor 400 smartphone users use it for convertin...
README (SKILL.md)

Getting Started

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

Try saying:

  • "convert three Honor 400 smartphone photos into a 1080p MP4"
  • "turn my Honor 400 photos into a smooth promotional video with transitions"
  • "converting Honor 400 phone images into shareable videos for Honor 400 smartphone users"

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.

  1. 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.
  2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer \x3Ctoken>, Content-Type: application/json, and body {"task_name":"project","language":"\x3Cdetected>"}. 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 Honor 400 — Convert Photos Into Shareable Videos

Drop your 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 three Honor 400 smartphone photos, ask for turn my Honor 400 photos into a smooth promotional video with transitions, 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 — use 5-10 images for the smoothest slideshow pacing.

Matching Input to Actions

User prompts referencing image to video honor 400, 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":"\x3Clang>"}. 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/\x3Csid> POST Upload a file (multipart) or URL.
/api/credits/balance/simple GET Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/\x3Csid>/latest GET Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda POST Start export. Body: {"id":"render_\x3Cts>","sessionId":"\x3Csid>","draft":\x3Cjson>,"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-honor-400
X-Skill-Version frontmatter version
X-Skill-Platform auto-detect: clawhub / cursor / unknown from install path

All requests must include: Authorization: Bearer \x3CNEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

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=\x3Cid>, 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

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 "turn my Honor 400 photos into a smooth promotional video with 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 my Honor 400 photos into a smooth promotional video with 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.

Usage Guidance
Before installing: (1) Understand that your images and metadata will be uploaded to mega-api-prod.nemovideo.ai for processing — verify you are comfortable with that third party handling your media. (2) Ask the publisher to explain where the anonymous token and session_id are stored (disk path, lifetime, and whether tokens persist beyond 7 days). (3) Resolve the metadata inconsistency about ~/.config/nemovideo/ so you know whether files/credentials will be written to your home directory. (4) Prefer an explicit opt-in prompt before the skill automatically requests a token or uploads files. (5) Because the skill's source/homepage is unknown, exercise extra caution: if privacy or provenance matters, only proceed after getting a verifiable publisher/endpoint and privacy terms.
Capability Analysis
Type: OpenClaw Skill Name: image-to-video-honor-400 Version: 1.0.0 The skill is a functional integration for the `nemovideo.ai` service, designed to convert images to video. It provides clear instructions for the AI agent to handle authentication via anonymous tokens, manage sessions, and process file uploads. No evidence of malicious intent, data exfiltration, or unauthorized execution was found; the behavior is consistent with the stated purpose of providing cloud-based video rendering.
Capability Assessment
Purpose & Capability
The skill name/description (image→video conversion) aligns with the declared primary credential (NEMO_TOKEN) and the runtime instructions for a cloud render pipeline. However, the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata shows no required config paths — an internal inconsistency that should be clarified.
Instruction Scope
The SKILL.md instructs the agent to automatically contact an external backend (https://mega-api-prod.nemovideo.ai) on first use, obtain an anonymous token if NEMO_TOKEN is not present, create sessions, upload user files, and poll render status. This is coherent with the stated purpose but constitutes automatic network activity and third‑party handling of user images and metadata; there is no explicit user-consent step described. The file upload and token issuance behavior should be made explicit to users.
Install Mechanism
Instruction-only skill with no install spec or downloaded code, which minimizes on-disk risk. No installers, package pulls, or archive extraction are present.
Credentials
Only NEMO_TOKEN is required, which is proportionate to a cloud API integration. The SKILL.md also instructs generating and using an anonymous token when none is set and storing a session_id; the exact storage location and lifecycle for the token/session are not specified. The frontmatter's mention of a config path (~/.config/nemovideo/) is not reflected in the registry metadata — clarify whether the skill will write credentials/config to disk.
Persistence & Privilege
The skill does not request 'always: true' and is user-invocable only. It does, however, describe persisting session_id and using tokens that can remain valid for days, and it will autonomously perform network calls on first use if no token is present. That autonomous network activity increases privacy exposure but is not an elevated platform privilege by itself.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install image-to-video-honor-400
  3. After installation, invoke the skill by name or use /image-to-video-honor-400
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of Image to Video Honor 400 — Convert Photos Into Shareable Videos: - Converts JPG, PNG, HEIC, and WEBP images (up to 200MB) into 1080p MP4 videos, optimized for Honor 400 smartphone users. - Simple upload and prompt-based workflow; cloud GPU processing produces results in 30–60 seconds. - Handles authentication and session creation automatically on first use (with 100 free credits for 7 days). - Supports advanced features: add transitions, overlays, aspect ratio changes, audio tracks, and more from natural language prompts. - Error handling and status updates included; supports querying credit balance, export status, and timeline previews. - Provides clear mapping between user requests and backend actions for a streamlined editing experience.
Metadata
Slug image-to-video-honor-400
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is Image To Video Honor 400?

convert images into animated photo videos with this skill. Works with JPG, PNG, HEIC, WEBP files up to 200MB. Honor 400 smartphone users use it for convertin... It is an AI Agent Skill for Claude Code / OpenClaw, with 62 downloads so far.

How do I install Image To Video Honor 400?

Run "/install image-to-video-honor-400" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Image To Video Honor 400 free?

Yes, Image To Video Honor 400 is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Image To Video Honor 400 support?

Image To Video Honor 400 is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Image To Video Honor 400?

It is built and maintained by mhogan2013-9 (@mhogan2013-9); the current version is v1.0.0.

💬 Comments