Skill flagged — suspicious patterns detected

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

Image To Video Youtube

v1.0.0

Get YouTube-ready video ready to post, without touching a single slider. Upload your images (JPG, PNG, WEBP, HEIC, up to 200MB), say something like "turn my...

0· 58·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 susan4731-wilfordf/image-to-video-youtube.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Image To Video Youtube" (susan4731-wilfordf/image-to-video-youtube) from ClawHub.
Skill page: https://clawhub.ai/susan4731-wilfordf/image-to-video-youtube
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 image-to-video-youtube

ClawHub CLI

Package manager switcher

npx clawhub@latest install image-to-video-youtube
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
Name/description (convert images to YouTube-ready MP4s) aligns with the instructions and required credential (NEMO_TOKEN). However the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) that is not listed in the registry metadata; this mismatch should be clarified.
!
Instruction Scope
Runtime instructions legitimately describe uploading user images, creating sessions, sending SSE messages, and polling renders on the nemovideo.ai API. They also instruct deriving an attribution header (X-Skill-Platform) from the agent's install path (e.g., ~/.clawhub/ or ~/.cursor/skills/), which implies reading local install paths — a privacy/scope creep that is unnecessary for core functionality. The instructions otherwise do not ask for unrelated files or additional env vars.
Install Mechanism
No install spec and no code files — instruction-only skill. This lowers supply-chain risk because nothing is downloaded or written to disk by the skill package itself.
Credentials
Only one credential is required (NEMO_TOKEN), which is proportionate for calling the described third-party API. Note the SKILL.md can generate an anonymous token itself if NEMO_TOKEN is absent. The earlier metadata/registry mismatch about configPaths (~/.config/nemovideo/) is inconsistent and should be confirmed.
Persistence & Privilege
always is false and model invocation is allowed (normal). The skill does not request permanent/always-on privileges or modification of other skills. It will create session tokens on the third-party service (normal for a cloud render workflow).
What to consider before installing
This skill appears to call a third‑party cloud service (mega-api-prod.nemovideo.ai) to upload your images and produce videos, using a NEMO_TOKEN; that is coherent with its stated purpose. Before installing/using it: 1) Confirm the service origin and privacy policy — your images will be uploaded to an external provider. 2) Prefer using the anonymous token flow for non-sensitive images rather than placing a long‑lived secret in NEMO_TOKEN. 3) Ask the author to explain the configPath mismatch (~/.config/nemovideo/) and why the skill derives an attribution header from local install paths — that behavior requires reading local paths and may expose information about your environment. 4) Do not set NEMO_TOKEN to any high‑privilege credentials intended for other services. If you need higher assurance, request the skill's source/homepage or a publisher identity before proceeding.

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

Runtime requirements

🖼️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk974s94zxzb1s8sbh4sn5ctpwh84qf2q
58downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "convert five product or travel photos in JPG format into a 1080p MP4"
  • "turn my photos into a YouTube video with transitions and background music"
  • "converting photo collections into YouTube videos for YouTubers"

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.

Image to Video for YouTube — Convert Photos into YouTube 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 five product or travel photos in JPG format, ask for turn my photos into a YouTube video with transitions and background music, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — use 16:9 ratio images to avoid black bars in the final YouTube video.

Matching Input to Actions

User prompts referencing image to video youtube, 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 image-to-video-youtube, 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).

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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.

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)

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

Common Workflows

Quick edit: Upload → "turn my photos into a YouTube video with transitions and background music" → Download MP4. Takes 1-2 minutes 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 my photos into a YouTube 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 with H.264 codec for best YouTube upload compatibility.

Comments

Loading comments...