Maker Facebook

create video clips or images into Facebook-ready videos with this skill. Works with MP4, MOV, JPG, PNG files up to 500MB. marketers and small business owners...

Security Scan

The skill's requested inputs and runtime instructions are consistent with a cloud video-rendering integration; nothing obvious is asking for unrelated credentials or installing unexpected components, though there are minor metadata inconsistencies and privacy considerations around sending files to a third‑party API.

Purpose & Capability

The name/description (Facebook video maker) matches the runtime instructions (upload media, create sessions, request renders) and the single required credential (NEMO_TOKEN). One minor inconsistency: the registry metadata provided to you listed no config paths, while the skill's frontmatter metadata declares a configPaths entry (~/.config/nemovideo/) — this is likely an authoring mismatch but doesn't change the core capability.

Instruction Scope

SKILL.md instructs the agent to obtain or use a NEMO_TOKEN, create sessions, upload user media, stream SSE edits, poll render status, and include attribution headers. These actions are within the described purpose. Two things to be aware of: (1) the skill asks the agent to detect an install path (~/.clawhub or ~/.cursor/skills) to set X-Skill-Platform — that requires reading the filesystem/environment and could leak environment details; (2) user media (up to 500MB) is uploaded to an external domain (mega-api-prod.nemovideo.ai), so sensitive content will leave the local machine. The instructions explicitly say not to print tokens or raw JSON, which is good.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk. Nothing is downloaded or written as part of installation.

Credentials

Only one environment variable (NEMO_TOKEN) is required and it directly maps to the API's Bearer auth. The skill also offers an anonymous-token flow to generate a token at runtime. No unrelated secrets or broad credential access are requested.

Persistence & Privilege

always:false and normal autonomous invocation behavior. The skill instructs saving a session_id and using tokens for requests (normal for a session-based API). It does not request persistent system-wide privileges or modifications to other skills.

Assessment

This skill appears to do what it says: it uploads media to a third‑party render service and returns a rendered MP4. Before installing or using it, consider: (1) Review the privacy/security policy of mega-api-prod.nemovideo.ai — any files you upload will be transmitted to that service. Avoid uploading sensitive videos or audio. (2) The skill needs a NEMO_TOKEN (or will request an anonymous token); treat that token like a credential and don’t paste it into public logs. (3) The skill may read local paths to determine X-Skill-Platform — if you’re uncomfortable with tools probing your home directory or environment, decline. (4) The registry/frontmatter mismatch for config paths looks like an authoring error; if you need higher assurance, ask the publisher for the source or a privacy statement before proceeding.

Getting Started

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

Try saying:

• "create my video clips or images"
• "export 1080p MP4"
• "create a 30-second Facebook ad video"

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 Video Maker — Create and Export Facebook Videos

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

Say you have three product photos and a logo file and want to create a 30-second Facebook ad video with text overlays and background music — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: square 1:1 or vertical 4:5 formats perform better in Facebook feeds.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: maker-facebook
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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

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.

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

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)

Common Workflows

Quick edit: Upload → "create a 30-second Facebook ad video with text overlays and background music" → Download MP4. Takes 1-2 minutes 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 "create a 30-second Facebook ad video with text overlays and background music" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for best Facebook upload compatibility.