Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Ai Video Maker Free Image

v1.0.0

turn free images into image-based video with this skill. Works with JPG, PNG, WEBP, GIF files up to 200MB. content creators use it for creating videos from f...

0· 60·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 tk8544-b/ai-video-maker-free-image.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Ai Video Maker Free Image" (tk8544-b/ai-video-maker-free-image) from ClawHub.
Skill page: https://clawhub.ai/tk8544-b/ai-video-maker-free-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 ai-video-maker-free-image

ClawHub CLI

Package manager switcher

npx clawhub@latest install ai-video-maker-free-image
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
!
Purpose & Capability
Name/description match the runtime instructions (remote GPU rendering via nemovideo API). Requiring NEMO_TOKEN is proportionate. However the SKILL.md metadata references a config path (~/.config/nemovideo/) and the instructions derive an X-Skill-Platform from local install paths (~/.clawhub/, ~/.cursor/skills/). The registry metadata (provided to you) listed no config paths, so there's an inconsistency about whether the skill expects to inspect local config/install locations.
!
Instruction Scope
Instructions are specific about API endpoints (mega-api-prod.nemovideo.ai), session creation, SSE, upload endpoints and polling for renders — all coherent for a cloud render service. But the doc also instructs the agent to 'detect' install path to set X-Skill-Platform (implies reading home directories), and to derive request headers from YAML frontmatter. Asking the agent to read local install/config paths is scope creep relative to a pure image→video transform and could expose local metadata not needed for rendering.
Install Mechanism
Instruction-only skill with no install spec and no code files. This is low-risk from an installation perspective because nothing is written to disk by an installer.
Credentials
The only declared required credential is NEMO_TOKEN (primaryEnv), which is reasonable for a hosted API. The SKILL.md also provides a fallback anonymous-token flow (generates a UUID and POSTs for an anonymous token), which reduces need for long-lived secrets. The inconsistency about configPaths in the SKILL.md metadata (versus registry metadata) is notable — a config path could contain additional secrets/config the skill might read if implemented.
Persistence & Privilege
always:false and user-invocable:true. The skill does not request permanent presence or elevated platform privileges. Autonomous invocation is allowed (default) but not in itself a flagged concern.
What to consider before installing
This skill appears to be a thin instruction-only integration for a cloud rendering API (mega-api-prod.nemovideo.ai) and only needs a NEMO_TOKEN to operate — that is reasonable. Before installing/using it, consider: 1) Source verification: the skill's source/homepage is unknown; prefer skills from known authors or with a homepage. 2) Token use: only provide a short-lived or limited NEMO_TOKEN if possible; the skill can request an anonymous starter token per its instructions, which is safer than giving a long-lived secret. 3) Local path access: the SKILL.md implies detecting install/config paths (~/.clawhub, ~/.cursor, ~/.config/nemovideo). Ask the maintainer why local path detection is needed and confirm the agent will not read arbitrary files in your home directory. 4) Privacy of uploads: images you upload will be sent to the external API; avoid uploading sensitive images unless you trust the service. 5) Clarify the configPaths inconsistency: the registry metadata you were shown lists no config paths, but the SKILL.md includes one — ask for clarification. If the author can confirm no local files beyond the user-provided images will be read and provide a verifiable homepage/repo, this would raise confidence to high.

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

Runtime requirements

🖼️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk978r82apkz4dey5jex5aqpks584z48f
60downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "turn three free stock photos of a city skyline into a 1080p MP4"
  • "turn these free images into a 30-second promotional video with music and transitions"
  • "creating videos from free images without paid assets for content creators"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

  • Generate a UUID as client identifier
  • POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
  • The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

AI Video Maker Free Image — Turn Free Images Into Videos

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

A quick example: upload three free stock photos of a city skyline, type "turn these free images into a 30-second promotional video with music and transitions", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: using fewer high-resolution images produces smoother, faster results than many low-quality ones.

Matching Input to Actions

User prompts referencing ai video maker free 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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is ai-video-maker-free-image, 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).

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

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.

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.

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

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

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

Tips and Tricks

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

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

Export as MP4 for widest compatibility across social platforms.

Common Workflows

Quick edit: Upload → "turn these free images into a 30-second promotional 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...