Photo Video Maker En Espanol

turn photos and images into slideshow video MP4 with this photo-video-maker-en-espanol skill. Works with JPG, PNG, HEIC, WebP files up to 200MB. Spanish-spea...

Security Scan

The skill's requests and instructions are consistent with a cloud-based photo→video service: it needs a Nemo service token and uploads user images to nemovideo.ai; there are minor metadata inconsistencies and you should be aware images and a generated token may be sent to an external backend.

Purpose & Capability

The skill's name/description (turn photos into MP4 slideshows) aligns with the only credential it requests (NEMO_TOKEN) and the documented API endpoints on mega-api-prod.nemovideo.ai. One small inconsistency: the registry metadata earlier listed no required config paths, but the SKILL.md YAML metadata declares a config path (~/.config/nemovideo/). This mismatch is minor but worth noting.

Instruction Scope

SKILL.md gives explicit runtime instructions that stay within the service's scope: authenticate (or obtain an anonymous token), create a session, upload files, and poll export endpoints. The skill will upload user-supplied files (local paths or URLs) to the external API and will store session_id and (if generated) the token. That behaviour is expected for this functionality but is privacy-sensitive — the agent will send your images to nemovideo.ai.

Install Mechanism

This is an instruction-only skill with no install steps or remote downloads, so there is no installation risk from fetching/executing code.

Credentials

Only one credential (NEMO_TOKEN) is required, which is proportionate for a hosted rendering service. However, the skill will auto-generate an anonymous token if NEMO_TOKEN is not present and then store/use it—this automatic token creation/storage is functional but should be disclosed to users. Also note the minor metadata/config-path mismatch (~/.config/nemovideo/) between SKILL.md and registry.

Persistence & Privilege

No elevated privileges requested: always:false, agent invocation allowed (normal). The skill stores its own session state/token for service calls but does not request system-wide changes or other skills' credentials.

Assessment

This skill appears to do what it says: it uploads photos to an external nemo video backend and returns rendered MP4s. Before installing/using it, consider: (1) privacy — your photos will be uploaded to https://mega-api-prod.nemovideo.ai; don't upload sensitive images unless you trust that service; (2) token handling — the skill will use NEMO_TOKEN if provided, or automatically obtain and store an anonymous token (100 free credits, 7-day validity) if not; if you prefer control, supply your own token and review token lifetime/permissions; (3) metadata mismatch — SKILL.md references a local config path (~/.config/nemovideo/) not reflected in registry metadata; ask the publisher to clarify if the skill will read or write that path; (4) no code is present — behavior is entirely defined by SKILL.md, so ask for a publisher/homepage if you want accountability or an audit trail.

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:

• "turn my photos and images"
• "export 1080p MP4"
• "crea un video con mis fotos"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Photo Video Maker en Español — Turn Photos Into Shareable 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 in JPG format, ask for crea un video con mis fotos y agrega música de fondo, 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 20 images for the fastest processing.

Matching Input to Actions

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

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

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

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 → "crea un video con mis fotos y agrega música de fondo" → 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 "crea un video con mis fotos y agrega música de fondo" — 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 WhatsApp, Instagram, and YouTube.