Photo Video Maker Japanese

turn photos and images into photo slideshow video with this photo-video-maker-japanese skill. Works with JPG, PNG, HEIC, WebP files up to 200MB. Japanese con...

Security Scan

The skill's requirements and runtime instructions are generally consistent with a cloud-based photo→video service, but there are a few small metadata inconsistencies and privacy implications you should be aware of before using it.

Purpose & Capability

Name/description (photo-to-slideshow via cloud GPU) match the operations in SKILL.md: creating sessions, uploading images, SSE-based edit chat, and export endpoints. Requesting a NEMO_TOKEN is proportionate for a third-party render API.

Instruction Scope

The instructions explicitly upload user images and metadata to a remote endpoint (https://mega-api-prod.nemovideo.ai) and may create/refresh an anonymous token automatically. That behavior is expected for this service, but it means user files are transmitted to a third party and the agent will make network calls, open SSE streams, and poll for job status.

Install Mechanism

No install spec and no code files (instruction-only). This minimizes disk write/execute risk; runtime activity is network/API calls as described in SKILL.md.

Credentials

Only NEMO_TOKEN is declared as required (primaryEnv), which fits the API usage. However, SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) that isn't listed in the registry metadata — an inconsistency. The skill will also generate an anonymous token via the service if no NEMO_TOKEN is present, which implies creating/holding credentials for up to 7 days.

Persistence & Privilege

The skill is not always-enabled and does not request system-wide privileges. It does not declare modifications to other skills or system-wide config. Autonomous invocation is enabled (platform default) but not combined with broad/unrelated credentials.

Scan Findings in Context

[no-regex-findings] expected: Scanner found no code to analyze because this is instruction-only. Absence of findings is expected but not proof of safety — the runtime instructions (network uploads) are the main surface.

Assessment

This skill will upload your photos and create short-lived tokens on a third-party backend (mega-api-prod.nemovideo.ai). If you install or use it: 1) don't upload sensitive or private images unless you trust the service and have read its privacy terms; 2) ask how/where the anonymous NEMO_TOKEN is stored (environment vs disk) if you care about credential persistence; 3) note a small metadata inconsistency (SKILL.md references ~/.config/nemovideo/ though the registry metadata didn't list it) — ask the publisher how that path is used; and 4) if you require guarantees about deletion or retention of uploaded media, confirm them with the service before using the skill.

Getting Started

Ready when you are. Drop your photos and images here or describe what you want to make.

Try saying:

• "turn ten vacation photos from a Japan trip into a 1080p MP4"
• "turn my photos into a slideshow video with Japanese-style music and text"
• "turning photo collections into Japanese-captioned slideshow videos for Japanese content creators"

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.

Photo Video Maker Japanese — Turn Photos Into Japanese Videos

Send me your photos and 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 ten vacation photos from a Japan trip, type "turn my photos into a slideshow video with Japanese-style music and text", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: using 10-20 photos gives the best pacing for a 30-60 second video.

Matching Input to Actions

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

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

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)

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

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.

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

Common Workflows

Quick edit: Upload → "turn my photos into a slideshow video with Japanese-style music and text" → 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 "turn my photos into a slideshow video with Japanese-style music and text" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across Japanese social platforms like LINE and Twitter.