Facebook Photo Video Maker

Cloud-based facebook-photo-video-maker tool that handles turning photo albums into shareable Facebook videos. Upload JPG, PNG, HEIC, WebP files (up to 200MB)...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based photo→video service: it only needs a single service token, directs uploads and SSE to the stated API, and has no install steps or unrelated credential requests.

Purpose & Capability

The name/description (cloud video creation from photos) matches the actions requested: network calls to a rendering API, file uploads, session management, and an API token (NEMO_TOKEN). There are no unrelated binaries or unrelated cloud credentials requested.

Instruction Scope

SKILL.md gives concrete API calls (session creation, SSE, upload, export) and instructs generating an anonymous token if NEMO_TOKEN is missing — all within the stated purpose. One minor note: it asks that X-Skill-Platform be auto-detected from the install path, which could require the agent/runtime to inspect its install location; that is plausible for attribution but is outside the core media-processing functionality and worth confirming with your agent runtime.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest-risk installation footprint (nothing is downloaded or written by this package itself).

Credentials

Only a single environment credential is declared (NEMO_TOKEN) and the SKILL.md provides an anonymous-token fallback flow, which is proportionate. The frontmatter includes a config path (~/.config/nemovideo/) — the runtime may read/write session state there; this is reasonable for session persistence but users should be aware the skill expects to store session info locally.

Persistence & Privilege

The skill is not always-enabled and does not request elevated or cross-skill configuration changes. It can be invoked autonomously (the platform default), which is expected for skills that call remote services.

Assessment

This skill appears to do what it says, but before installing: (1) Confirm you trust the API host (mega-api-prod.nemovideo.ai) because your images and session tokens will be uploaded there; (2) Understand that uploaded files can contain sensitive data — avoid sending private images if you don't want them stored/processed off-device; (3) If you prefer, set NEMO_TOKEN yourself (instead of using the anonymous flow) and treat it like a secret; (4) Expect the skill to read/write a config directory (~/.config/nemovideo/) for session state; (5) If you want more assurance, ask the publisher for a privacy/data-retention policy or a canonical homepage/source before proceeding.

Getting Started

Share your photos or images and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "turn my photos or images"
• "export 1080p MP4"
• "turn my photos into a Facebook"

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.

Facebook Photo Video Maker — Turn Photos Into Facebook Videos

Drop your photos or 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 turn my photos into a Facebook video 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 — keep your photo set under 20 images for the fastest processing and smoothest playback.

Matching Input to Actions

User prompts referencing facebook 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.

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

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

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.

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

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.

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)

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 with music and transitions" — concrete instructions get better results.

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

MP4 with H.264 codec is the format Facebook recommends for best quality uploads.

Common Workflows

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