Portugues Photo Video Maker

turn photos and images into polished MP4 videos with this portugues-photo-video-maker skill. Works with JPG, PNG, HEIC, WebP files up to 200MB. Portuguese-sp...

Security Scan

The skill's requested access and runtime instructions are consistent with a cloud-based photo→video service, but there are a few small metadata/instruction inconsistencies and privacy considerations you should review before use.

Purpose & Capability

Name/description match the actions in SKILL.md: uploading images and requesting cloud renders via nemovideo.ai. Required credential (NEMO_TOKEN) is coherent with a cloud API token.

Instruction Scope

Instructions focus on session creation, uploads, SSE streaming, polling, and exports to the stated backend. The skill does not instruct the agent to read arbitrary system files or unrelated credentials in the visible instructions.

Install Mechanism

No install spec or code files — instruction-only skill (low install risk). Nothing will be downloaded or written by an installer step described in the package metadata.

Credentials

Only NEMO_TOKEN is declared as required, which fits the described API. However, SKILL.md frontmatter references a config path (~/.config/nemovideo/) not present in the registry metadata: the skill may look for or use local config files even though the registry summary listed no config paths. Also the skill will create/use an anonymous token if NEMO_TOKEN is absent (it instructs obtaining a token via the service's anonymous-token endpoint).

Persistence & Privilege

always:false (normal) and autonomous invocation allowed (platform default). The skill will perform automatic setup on first use (create an anonymous token if none provided) and may store/use session tokens — confirm how/where tokens are stored. No indication it modifies other skills or system-wide settings.

Assessment

This skill uploads your photos to an external service (mega-api-prod.nemovideo.ai) to render videos and will use or obtain a NEMO_TOKEN for API access (anonymous tokens are short-lived). Before using it: (1) be comfortable that your images will leave your device — do not upload sensitive photos unless you trust the service; (2) if you have an account, provide your NEMO_TOKEN instead of relying on anonymous tokens to keep control; (3) note the SKILL.md references a local config path (~/.config/nemovideo/) even though registry metadata did not — confirm whether the skill will read or write that path and whether you want that; (4) verify the backend domain and privacy policy if possible; and (5) because the skill runs remotely and may be invoked autonomously by the agent, consider only enabling it when you explicitly want photo-to-video conversions.

Getting Started

Got photos and images to work with? Send it over and tell me what you need — I'll take care of the AI video creation.

Try saying:

• "turn ten vacation photos in JPG format into a 1080p MP4"
• "criar um vídeo com minhas fotos e adicionar música de fundo"
• "turning photo collections into shareable videos in Portuguese for Portuguese-speaking 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.

Português Photo Video Maker — Turn Photos Into MP4 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 criar um vídeo com minhas fotos e adicionar música de fundo, 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 — organize your photos in order before uploading so the video sequence matches your story.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	portugues-photo-video-maker
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "criar um vídeo com minhas fotos e adicionar música de fundo" — 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.

Common Workflows

Quick edit: Upload → "criar um vídeo com minhas fotos e adicionar música de fundo" → 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.