Social Video

Get shareable social clips ready to post, without touching a single slider. Upload your raw video clips (MP4, MOV, WebM, AVI, up to 500MB), say something lik...

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud-based video editing service: it only needs a NEMO_TOKEN, uploads media to a named API, and uses session tokens for render jobs.

Purpose & Capability

The name/description (AI social video editing) match the SKILL.md actions (upload, SSE chat, export, poll render). Requesting a single NEMO_TOKEN for remote API access is appropriate. Minor inconsistency: the registry metadata listed no required config paths, while the SKILL.md frontmatter's openclaw metadata includes a configPaths entry (~/.config/nemovideo/). This is a small mismatch in metadata but does not contradict the declared purpose.

Instruction Scope

The instructions confine themselves to authenticating (anonymous-token if needed), creating a session, uploading files, driving edit actions via SSE/API, polling exports, and returning download URLs. There is no instruction to read unrelated local files or secrets. The skill does ask the agent to detect install path to set an attribution header (X-Skill-Platform), which requires checking known path locations — reasonable for attribution but worth noting.

Install Mechanism

No install spec or code files are present (instruction-only). No downloads, package installs, or disk writes are specified by the skill itself.

Credentials

Only one credential is declared (NEMO_TOKEN) and that is the primary credential used for the described API workflow. The SKILL.md also mentions a config path in its frontmatter (see purpose_capability) which could imply reading local config; the runtime instructions themselves only check for NEMO_TOKEN in the environment and create an anonymous token if missing. Reauth and token storage behavior is expected for this functionality but means the agent will perform network calls to obtain/refresh tokens.

Persistence & Privilege

always:false and model invocation not disabled (normal). The skill does request storing a session_id and using tokens for subsequent requests (normal for a session-based API). It does not request persistent system-wide privileges or modify other skills.

Assessment

This skill sends your uploaded media and session tokens to https://mega-api-prod.nemovideo.ai for cloud rendering — that's expected for a hosted video editor. Before installing: 1) Confirm you trust the nemovideo.ai service (no homepage is provided here). 2) Understand that video/audio files and the NEMO_TOKEN (anonymous or provided) will be transmitted to that external API; avoid uploading sensitive content. 3) Note the skill can auto-create anonymous tokens and refresh them, so the agent will make outbound authentication requests without additional prompts. 4) If you need stricter privacy, require a vetted service or review network endpoints and retention/privacy policy from the vendor. Finally, the SKILL.md frontmatter mentions a local config path (~/.config/nemovideo/) even though registry metadata omitted it — ask the publisher which local files (if any) the skill will access or store.

Getting Started

Share your raw video clips and I'll get started on AI social video editing. Or just tell me what you're thinking.

Try saying:

• "create my raw video clips"
• "export 1080p MP4"
• "cut this into a 30-second Instagram"

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.

Social Video — Create and Export Social Clips

Send me your raw video clips and describe the result you want. The AI social video editing runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 2-minute smartphone recording from an event, type "cut this into a 30-second Instagram Reel with captions and background music", and you'll get a 1080p MP4 back in roughly 30-60 seconds. All rendering happens server-side.

Worth noting: vertical 9:16 framing works best for TikTok, Reels, and Shorts exports.

Matching Input to Actions

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

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

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

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

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

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

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 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 "cut this into a 30-second Instagram Reel with captions and background music" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for widest compatibility across social platforms.

Common Workflows

Quick edit: Upload → "cut this into a 30-second Instagram Reel with captions and background music" → 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.