Photo Video Maker Facebook

Cloud-based photo-video-maker-facebook tool that handles creating Facebook slideshow videos from photos. Upload JPG, PNG, HEIC, WebP files (up to 200MB), des...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud video-rendering service: it needs one service token (NEMO_TOKEN), talks only to the nemovideo API, and has no installable code — but you should note a small metadata mismatch and consider how tokens/sessions are stored.

Purpose & Capability

The skill is a cloud photo→video service and only requests one service credential (NEMO_TOKEN) and uses endpoints under mega-api-prod.nemovideo.ai, which is coherent with the described purpose. Minor inconsistency: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata reported no required config paths — this suggests the skill expects to read or write a local config directory but the registry declaration didn't reflect that.

Instruction Scope

The SKILL.md instructs the agent to check NEMO_TOKEN, or obtain an anonymous token from the nemovideo API, create and store a session_id, upload files, and poll render endpoints. These actions stay within the stated domain (render service). The noteworthy scope item is that the skill asks the agent to persist tokens/session IDs (and frontmatter hints at a config path), which may lead to local storage of credentials/session state — the instructions do not detail where or how long to persist them.

Install Mechanism

This is an instruction-only skill with no install spec or code to download. That is the lowest-risk install mechanism and consistent with the provided SKILL.md.

Credentials

Only one environment variable (NEMO_TOKEN) is declared and is appropriate for an API-backed video service. The skill also implements anonymous-token generation if NEMO_TOKEN is missing; that behavior is reasonable but means the agent will receive and be asked to store a bearer token it obtained itself. If you prefer control, supply your own NEMO_TOKEN rather than letting the skill create one.

Persistence & Privilege

The skill does not request always:true and does not modify other skills. However it explicitly instructs storing a session_id and potentially the anonymous token for subsequent requests; consider whether you are comfortable with the agent persisting those credentials/session identifiers and where they will be stored (frontmatter references a config path). Autonomous invocation remains enabled (default), so stored credentials could be used by the agent without asking if you grant that permission.

Assessment

This skill appears to do what it says: it talks to a nemovideo cloud API and needs one bearer token. Before installing: 1) note the source/homepage is missing — verify the service if you care about provenance; 2) prefer supplying your own NEMO_TOKEN rather than letting the skill create and store an anonymous token; 3) ask/verify where the agent will persist the token/session_id (the SKILL.md hints at ~/.config/nemovideo/); and 4) if you do not want the agent to use stored tokens autonomously, avoid enabling persistent/autonomous use or remove the token when finished.

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 with captions into a 1080p MP4"
• "turn my photos into a Facebook video slideshow with music and transitions"
• "creating Facebook slideshow videos from photos for Facebook users and social media marketers"

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 for Facebook — Turn Photos into Facebook 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 with captions, ask for turn my photos into a Facebook video slideshow with music and transitions, 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 — Facebook plays videos silently by default, so add text overlays to convey your message without sound.

Matching Input to Actions

User prompts referencing photo video maker facebook, 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	photo-video-maker-facebook
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 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)

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

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 "turn my photos into a Facebook video slideshow with music and transitions" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for smooth Facebook playback and fast upload.

Common Workflows

Quick edit: Upload → "turn my photos into a Facebook video slideshow 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.