Create Ai Video For Marketing

Get marketing video MP4 ready to post, without touching a single slider. Upload your images or footage (MP4, MOV, JPG, PNG, up to 500MB), say something like...

Security Scan

The skill's runtime instructions mostly match a cloud video-rendering purpose, but there are inconsistencies (declared requirements vs. runtime fallback and config-path metadata) and it will upload user media and manage auth tokens for an external service — you should review data handling and the provenance of the backend before installing.

Purpose & Capability

The SKILL.md behavior (upload media, create render jobs, poll for export) aligns with the stated goal of producing marketing MP4s. However, registry metadata presented to you lists no config paths while the skill's own frontmatter requires ~/.config/nemovideo/ and declares NEMO_TOKEN as primary — yet the instructions also implement an anonymous-token fallback. Marked as a note because 'required' vs 'optional via anonymous-token' and the duplicated/inconsistent config metadata are incoherent.

Instruction Scope

Instructions explicitly tell the agent to read the skill's frontmatter, detect install path, read NEMO_TOKEN from environment (or POST to an external anonymous-token endpoint), upload user files to https://mega-api-prod.nemovideo.ai, open SSE streams, and keep session IDs. Those actions are expected for a cloud video service, but they involve reading local files/paths and sending potentially sensitive user media to a third-party endpoint — the scope is broader than a purely local helper and contains explicit network I/O.

Install Mechanism

Instruction-only skill with no install spec and no code files. This minimizes on-disk risk; nothing will be downloaded or installed by the skill itself according to the provided metadata.

Credentials

The registry lists only NEMO_TOKEN as required (primary credential), which matches the service auth. But SKILL.md both expects NEMO_TOKEN and instructs the agent to generate/use an anonymous token if none is present — an inconsistency. The frontmatter also references a config path (~/.config/nemovideo/) that the registry summary said was 'none' — unclear whether the skill will read that path or why it's required. Overall, the credential request is plausible for this service, but the metadata/instruction mismatch and implied filesystem access are concerning and should be clarified.

Persistence & Privilege

always:false and no install means the skill does not demand permanent presence or elevated platform privileges. It will store session tokens in-memory for the session, which is normal. Autonomous invocation is allowed but that is the platform default and not by itself a red flag.

What to consider before installing

This skill will upload any images or video you send to mega-api-prod.nemovideo.ai and use a Bearer token (NEMO_TOKEN) for auth; if you don't provide one it will obtain an anonymous token for you. Before installing, confirm: (1) Do you trust the backend domain and its privacy/retention policy? Uploaded media and generated tokens will leave your device. (2) Clarify the metadata mismatch: why does the skill declare a required config path in its frontmatter while the registry shows none, and is NEMO_TOKEN truly required or optional (anonymous fallback)? (3) If you need stronger control, prefer supplying your own token or avoid using the skill for sensitive media. If you want me to approve or re-evaluate after you provide the service's privacy policy, terms of service, or the skill's source/homepage, I can reassess with higher confidence.

Getting Started

Got images or footage to work with? Send it over and tell me what you need — I'll take care of the AI video creation.

Try saying:

• "create three product photos and a brand logo into a 1080p MP4"
• "create a 30-second marketing video with text overlays and background music"
• "generating promotional videos from product images or brand assets for marketers"

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.

Create AI Video for Marketing — Generate Marketing Videos from Assets

Drop your images or footage 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 three product photos and a brand logo, ask for create a 30-second marketing video with text overlays 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 — using square or 16:9 images gives the cleanest output for ads.

Matching Input to Actions

User prompts referencing create ai video for marketing, 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: create-ai-video-for-marketing
• 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

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.

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 "create a 30-second marketing 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 for widest compatibility across social and ad platforms.

Common Workflows

Quick edit: Upload → "create a 30-second marketing 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.