Ai Video For Marketing

create video clips or images into polished marketing videos with this skill. Works with MP4, MOV, JPG, PNG files up to 500MB. marketers use it for generating...

Security Scan

The skill's requests and runtime instructions match its stated purpose (cloud video rendering) — it asks only for a service token and describes API calls consistent with that purpose, but there are small metadata inconsistencies and privacy implications you should consider before uploading assets or providing tokens.

Purpose & Capability

The skill is a cloud-based video-processing integration and requires a single service credential (NEMO_TOKEN). That aligns with its description of uploading media and calling rendering/export endpoints. Nothing in the instructions requests unrelated cloud providers or unrelated credentials.

Instruction Scope

SKILL.md instructs the agent to upload user media and exchange tokens/sessions with mega-api-prod.nemovideo.ai (session creation, SSE chat, upload, render endpoints). This is coherent with video rendering, but it means user files and metadata are transmitted to an external backend — the instructions do not limit what media is sent. The skill also reads environment variables and detects install path to set attribution headers, which requires local path inspection (minor privacy/scope consideration).

Install Mechanism

There is no install spec and no code files — this is instruction-only, so nothing arbitrary is downloaded or written to disk by the installer. Risk from install mechanism is low.

Credentials

The only required credential is NEMO_TOKEN (declared as primary), which is proportionate for a cloud video service. However, the SKILL.md frontmatter mentions a configPaths entry (~/.config/nemovideo/) and the headers require detecting install path (~/.clawhub/, ~/.cursor/skills/) — these filesystem checks are not declared in the registry metadata and are worth clarifying. The skill also describes obtaining an anonymous token itself if NEMO_TOKEN is absent.

Persistence & Privilege

The skill is not always-enabled and uses normal autonomous invocation. It does not request elevated platform-wide privileges or attempt to modify other skills' configs according to the provided instructions.

Assessment

This skill sends any media you provide to an external service (mega-api-prod.nemovideo.ai) and uses a NEMO_TOKEN for authenticated calls. Before installing or using it: 1) Decide whether you are comfortable uploading the specific videos/images (they will leave your device). 2) Prefer giving an ephemeral/anonymous token or let the skill create an anonymous token rather than supplying a long-lived secret. 3) Ask the publisher (or inspect network logs) to confirm what is stored/retained and for how long, and review nemovideo.ai's privacy/terms. 4) Note the SKILL.md mentions reading install paths and a local config path (~/.config/nemovideo/) — confirm whether the skill will actually read local files and why. If you need stronger assurance, avoid supplying any production or highly sensitive media or credentials until the provider and data-handling policies are verified.

Getting Started

Share your video clips or images and I'll get started on AI marketing 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 promotional video with"

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 Marketing — Create and Export Marketing Videos

Drop your video clips or images in the chat and tell me what you need. I'll handle the AI marketing 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 logo file, ask for create a 30-second promotional 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 — square and vertical formats work great for social ad placements alongside standard 16:9.

Matching Input to Actions

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

Headers are derived from this file's YAML frontmatter. X-Skill-Source is ai-video-for-marketing, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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

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)

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 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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a 30-second promotional 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 ad platforms like Meta and Google.

Common Workflows

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