Video Joypix

create images or clips into animated photo videos with this skill. Works with MP4, MOV, JPG, PNG files up to 200MB. social media creators use it for turning...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud video-processing integration and don't ask for unrelated secrets or installs, aside from a small metadata/config-path mismatch in the manifest.

Purpose & Capability

The skill requests a single API credential (NEMO_TOKEN) and calls a nemovideo.ai API, which aligns with its stated purpose of cloud video rendering. Minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported 'required config paths: none'. This is likely harmless but should be clarified.

Instruction Scope

Runtime instructions are limited to authenticating with the provider, creating a session, uploading user files, polling SSE, and exporting results. The skill does not instruct reading unrelated system files or other environment variables. It does reference detecting install paths to populate an attribution header (non-sensitive), which is extraneous but not clearly malicious.

Install Mechanism

This is an instruction-only skill with no install spec or code files. Nothing will be written to disk by an installer step — lowest risk for install mechanism.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is proportional for a cloud API. The SKILL.md suggests generating an anonymous token via the provider API if none is present. The earlier-mentioned config-path in frontmatter could imply reading a local config if implemented, so confirm whether the skill will attempt to read or persist files under ~/.config/nemovideo/.

Persistence & Privilege

The skill does not request elevated or permanent platform privileges (always:false). It asks the agent to save a session_id for the active session, which is normal for conversational session continuity; nothing indicates it will modify other skills or system-wide settings.

Assessment

This skill appears coherent for a cloud-based video rendering service. Before installing, consider: 1) the skill will send your uploaded media to https://mega-api-prod.nemovideo.ai — don't upload sensitive content unless you trust that service; 2) it needs a NEMO_TOKEN (you can supply one or let the skill request an anonymous token from the provider); 3) clarify whether it will read or write files under ~/.config/nemovideo/ (SKILL.md mentions that path but registry metadata does not); 4) check the provider's privacy/terms at nemovideo.ai if you care about retention/processing; and 5) if you want to prevent autonomous invocation, toggle disable-model-invocation on the agent (the skill currently can be invoked by the agent by default).

Getting Started

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

Try saying:

• "create five product photos and a logo file into a 1080p MP4"
• "turn these photos into a 30-second video with music and transitions"
• "turning photo collections into shareable videos for social media creators"

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.

Video JoyPix — Turn Photos Into Shareable Videos

This tool takes your images or clips and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have five product photos and a logo file and want to turn these photos into a 30-second video with music and transitions — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: using fewer than 10 images keeps processing fast and transitions clean.

Matching Input to Actions

User prompts referencing video joypix, 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.

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

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.

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

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 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

Common Workflows

Quick edit: Upload → "turn these photos into a 30-second video with 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 "turn these photos into a 30-second video with music and transitions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across all social platforms.