Skill flagged — suspicious patterns detected

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

Italiano Photo Video Maker

v1.0.0

create photos and images into photo slideshow video with this italiano-photo-video-maker skill. Works with JPG, PNG, HEIC, MP4 files up to 200MB. Italian con...

0· 64·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/italiano-photo-video-maker.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Italiano Photo Video Maker" (whitejohnk-26/italiano-photo-video-maker) from ClawHub.
Skill page: https://clawhub.ai/whitejohnk-26/italiano-photo-video-maker
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 italiano-photo-video-maker

ClawHub CLI

Package manager switcher

npx clawhub@latest install italiano-photo-video-maker
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
The skill name/description match its behavior: it uploads images/video and requests a NEMO_TOKEN to call nemovideo.ai endpoints. One inconsistency: registry metadata listed no config paths, but the SKILL.md frontmatter declares a config path (~/.config/nemovideo/). Reading a service config directory is plausible for a client but the registry/manifest disagreement is worth verifying.
Instruction Scope
SKILL.md gives explicit step-by-step API flows (session creation, SSE for chat, upload, export/poll), which are appropriate for a cloud render service. It also instructs the agent to: read this file's YAML frontmatter at runtime and detect install path to set an X-Skill-Platform header — these require access to the agent's environment/paths but are limited in scope. No instructions ask the agent to read unrelated system files or arbitrary environment variables.
Install Mechanism
Instruction-only skill with no install spec and no code files — minimal on-disk installation risk.
Credentials
Only NEMO_TOKEN is declared as required and used as a Bearer token for the service. The skill includes a documented anonymous-token fallback flow so it can operate without a pre-provisioned token. No unrelated credentials are requested.
Persistence & Privilege
always:false and no instructions to modify other skills or system-wide settings. The skill will perform network requests and upload user media to the nemovideo.ai backend (expected for this purpose).
Assessment
This skill will upload any photos/videos you provide to mega-api-prod.nemovideo.ai and needs a NEMO_TOKEN (or will obtain a temporary anonymous token). Confirm you trust that external service before sending sensitive images. Note the SKILL.md includes a config-path declaration (~/.config/nemovideo/) even though the registry metadata didn't — ask the publisher which is correct. If you supply a permanent NEMO_TOKEN, ensure it has only the scopes you intend; otherwise, use the anonymous flow for limited, short-lived access. Finally, because this is instruction-only, runtime behavior depends on the agent making the described API calls — review network/privacy policies for the platform if you need stronger guarantees.

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

Runtime requirements

🇮🇹 Clawdis
EnvNEMO_TOKEN
Primary envNEMO_TOKEN
latestvk97dz5n1n6ffw0ttnnsz1yg05184mv1a
64downloads
0stars
1versions
Updated 2w ago
v1.0.0
MIT-0

Getting Started

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

Try saying:

  • "create my photos and images"
  • "export 1080p MP4"
  • "create a slideshow video with Italian"

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.

Italiano Photo Video Maker — Turn Photos Into Videos

Drop your photos and 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 ten vacation photos from Italy, ask for create a slideshow video with Italian music and 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 — fewer photos per video means faster processing and smoother transitions.

Matching Input to Actions

User prompts referencing italiano photo video maker, 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

  1. SessionPOST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
  2. Chat (SSE)POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
  3. UploadPOST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
  4. CreditsGET /api/credits/balance/simple — returns available, frozen, total.
  5. StateGET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
  6. ExportPOST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Skill attribution — read from this file's YAML frontmatter at runtime:

  • X-Skill-Source: italiano-photo-video-maker
  • X-Skill-Version: from frontmatter version
  • X-Skill-Platform: detect from install path (~/.clawhub/clawhub, ~/.cursor/skills/cursor, else unknown)

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

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)

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

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.

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 → "create a slideshow video with Italian 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a slideshow video with Italian music and transitions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across Italian social platforms.

Comments

Loading comments...