Ai Video For Social Media

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

Security Scan

The skill's instructions, required credential (NEMO_TOKEN), and cloud API usage are coherent with a cloud-based video-editing/exports service; no evidence of unrelated credential requests or suspicious install behavior was found, though there are a few minor inconsistencies and privacy considerations to review before installing.

Purpose & Capability

The skill's name/description (AI social video editing) matches the runtime instructions (upload video, create session, render/export via nemo API). The only mismatch is a metadata inconsistency: the registry overview lists no required config paths, but the SKILL.md frontmatter and metadata reference a config path (~/.config/nemovideo/) and require attribution headers, which implies the skill may read or reference local install/config information. This is plausible for tracking/attribution but is an inconsistency to be aware of.

Instruction Scope

SKILL.md instructs the agent to upload user video files, create sessions, poll status, and stream SSEs — all expected for this purpose. It also instructs detecting the agent install path (~/.clawhub, ~/.cursor/skills/) to populate an X-Skill-Platform header and may reference ~/.config/nemovideo/ for config — reading these paths is out-of-band relative to pure video-editing logic (but not obviously malicious). The skill explicitly says not to expose tokens/raw API output.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That is the lowest-risk category for install mechanism.

Credentials

The skill requests a single credential, NEMO_TOKEN, which is appropriate for an API-backed rendering service. It also documents an anonymous-token flow (POST to the service to obtain a short-lived token) if NEMO_TOKEN is absent. This is proportionate, but the token is sensitive: any supplied NEMO_TOKEN grants API access (including uploads and rendering), so users should ensure the environment variable corresponds to the intended account and be mindful of where tokens are stored.

Persistence & Privilege

The skill does not request 'always: true' and does not declare elevated platform privileges. It will manage ephemeral session_ids/tokens for rendering jobs and instructs polling and SSE handling; there is no instruction to modify other skills or system-wide settings. The metadata's referenced config path suggests it may check or use a local config directory, which is normal for credential/session caching but should be noted.

Assessment

This skill appears to do what it says: upload your video to nemo's cloud service and return edited/exported clips. Before installing or using it, consider: (1) All uploaded media will be sent to https://mega-api-prod.nemovideo.ai — don't upload sensitive or regulated content unless you trust the service and its privacy/terms. (2) NEMO_TOKEN is a secret: if you set one in your environment it grants API access (billing/exports); verify it's the correct account token. If you don't set one, the skill will call the service to create an anonymous short-lived token (100 free credits, 7-day expiry). (3) The SKILL.md references a local config path (~/.config/nemovideo/) and will try to detect install paths to set attribution headers — if you have stored credentials there, the skill may read them. (4) There is a minor metadata inconsistency (registry shows no config paths while the SKILL.md includes one); ask the publisher how local config and tokens are used/stored if you need tighter assurance. If privacy or account separation matters, use a disposable/limited token or test with non-sensitive content first.

Getting Started

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

Try saying:

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

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.

AI Video for Social Media — Create and Export Social Clips

Drop your raw video footage in the chat and tell me what you need. I'll handle the AI social video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute smartphone clip from a product launch, ask for cut this into a 30-second Instagram Reel with captions and background music, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — vertical 9:16 video works natively for TikTok and Reels without cropping.

Matching Input to Actions

User prompts referencing ai video for social media, 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: ai-video-for-social-media
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

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.

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)

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, AVI, WebM for the smoothest experience.

Export as MP4 with H.264 codec for the best compatibility across all social platforms.

Common Workflows

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