Photo Video Maker Italiano

Italian-speaking content creators create photos and images into slideshow video MP4 using this skill. Accepts JPG, PNG, HEIC, MP4 up to 500MB, renders on clo...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based photo→video service; nothing indicates it's trying to do unrelated or hidden work.

Purpose & Capability

The skill claims to render photos into slideshow MP4s on a cloud GPU service and all declared runtime actions (auth, session creation, upload, render/export endpoints) target a single external API (mega-api-prod.nemovideo.ai). Requesting a single service token (NEMO_TOKEN) is proportional to that purpose.

Instruction Scope

The SKILL.md gives detailed API workflows (create session, SSE chat, upload, export) and only asks to handle user media and session tokens. It instructs the agent to read this file's YAML frontmatter and to detect install path to set attribution headers — these require reading skill metadata and possibly the agent's install path. This is reasonable for adding attribution headers but is a minor scope expansion (reading its own metadata and install location). There are no instructions to read unrelated system files or other environment variables.

Install Mechanism

No install spec or code files are present; this is an instruction-only skill. Nothing will be downloaded or written to disk by an installer step.

Credentials

The only required credential is NEMO_TOKEN (declared as primaryEnv), which matches the described API usage. One inconsistency: the SKILL.md frontmatter metadata lists a config path (~/.config/nemovideo/) while the registry metadata reported 'Required config paths: none'. Accessing a per-service config directory could be reasonable (cached tokens/settings), but the mismatch between registry metadata and the skill frontmatter should be clarified before trusting the skill to read that path.

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It instructs saving session_id for ongoing jobs and to reuse an existing NEMO_TOKEN if present — standard behavior for a session-based cloud service.

Scan Findings in Context

[no-findings] expected: The static regex scanner had no code files to analyze. This is expected for an instruction-only skill; absence of findings is not evidence of safety beyond what the SKILL.md describes.

Assessment

This skill appears to do what it says: it uploads user media to a nemovideo cloud API and returns rendered MP4s. Before installing or using it: 1) Confirm you trust the external domain (mega-api-prod.nemovideo.ai) and understand their privacy/storage policy for uploaded images/videos. 2) Be aware the skill will use a NEMO_TOKEN (you can provide one or let it obtain an anonymous ephemeral token). 3) Ask the publisher to clarify the config-path discrepancy (the skill's frontmatter references ~/.config/nemovideo/ while registry metadata did not) if you want to prevent any filesystem reads. 4) Avoid sending highly sensitive images unless you have verified the service's data-retention and access controls.

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"
• "crea un video dalle mie foto"

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.

Photo Video Maker Italiano — Crea video dalle tue foto

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 in JPG format, ask for crea un video dalle mie foto con musica di sottofondo e transizioni, 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 — keep photo sets under 30 images for faster processing.

Matching Input to Actions

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

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

1. Session — POST /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. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /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: photo-video-maker-italiano
• 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 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)

Backend Response Translation

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

Backend says	You 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

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.

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=<id>, 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "crea un video dalle mie foto con musica di sottofondo e transizioni" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across Italian social platforms.

Common Workflows

Quick edit: Upload → "crea un video dalle mie foto con musica di sottofondo e transizioni" → 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.