Skill flagged — suspicious patterns detected

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

Pixverse Ai Image To Video

v1.0.0

Get animated video clips ready to post, without touching a single slider. Upload your static images (JPG, PNG, WEBP, HEIC, up to 20MB), say something like "a...

0· 70·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 francemichaell-15/pixverse-ai-image-to-video.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Pixverse Ai Image To Video" (francemichaell-15/pixverse-ai-image-to-video) from ClawHub.
Skill page: https://clawhub.ai/francemichaell-15/pixverse-ai-image-to-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 pixverse-ai-image-to-video

ClawHub CLI

Package manager switcher

npx clawhub@latest install pixverse-ai-image-to-video
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill's declared purpose (convert static images to short videos) matches the runtime instructions and the single required credential (NEMO_TOKEN). However, the SKILL.md metadata includes a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — this mismatch is an incoherence that should be clarified.
Instruction Scope
SKILL.md stays within the stated scope: it describes authenticating (using NEMO_TOKEN or obtaining an anonymous token), session creation, uploading images, SSE-based messaging, polling render status, and downloading outputs. It does not instruct reading unrelated system files or harvesting unrelated environment variables.
Install Mechanism
This is an instruction-only skill with no install spec or code files, so nothing is written to disk by an installer. That reduces installation risk.
Credentials
Only one credential (NEMO_TOKEN) is requested, which is proportional. The skill will also obtain an anonymous token if none is present. The noteable concern is the metadata discrepancy mentioning a config path that could imply reading/writing ~/.config/nemovideo/ (not declared elsewhere). Confirm whether the skill will persist tokens or other data to that path.
Persistence & Privilege
always:false and no install hooks are present. The skill does not request permanent agent-wide privileges and does not instruct modifying other skills or global agent configuration. Still verify whether it persists session or token data locally given the configPath inconsistency in SKILL.md.
What to consider before installing
What to consider before installing: 1) Source & domain: the skill uses an external API (mega-api-prod.nemovideo.ai) and the skill's homepage/source are unknown — verify the service and its privacy policy before uploading any private or sensitive images. 2) Metadata mismatch: SKILL.md references a config path (~/.config/nemovideo/) not declared in the registry metadata — ask the publisher whether the skill will read or write that directory or persist tokens. 3) Credentials: the skill needs a NEMO_TOKEN (or will obtain an anonymous token). Prefer using the anonymous flow or a scoped/temporary token if available; avoid supplying long‑lived credentials you use elsewhere. 4) Data exfiltration risk: the service necessarily uploads images to a remote server; do not use with confidential images unless you trust the provider. 5) Ask the publisher for provenance (homepage/source repo) and a privacy/retention statement; if you cannot verify the service, treat the skill as untrusted and avoid installing or uploading sensitive content.

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

Runtime requirements

🎞️ Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk9729s4fnhe3qf5fy7apx5b26d84p9k8
70downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "convert my static images"
  • "export 1080p MP4"
  • "animate this image into a 5-second"

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.

PixVerse AI Image to Video — Convert Images Into Video Clips

Drop your static images in the chat and tell me what you need. I'll handle the AI video generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a single product photo or illustrated scene, ask for animate this image into a 5-second video with smooth motion, and about 30-90 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — images with clear subjects and simple backgrounds animate more naturally.

Matching Input to Actions

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

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

HeaderValue
X-Skill-Sourcepixverse-ai-image-to-video
X-Skill-Versionfrontmatter version
X-Skill-Platformauto-detect: clawhub / cursor / unknown from install path

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.

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.

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 → "animate this image into a 5-second video with smooth motion" → Download MP4. Takes 30-90 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 "animate this image into a 5-second video with smooth motion" — concrete instructions get better results.

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

Use PNG for images with transparency to get cleaner animation edges.

Comments

Loading comments...