Ai Video Marketing Automator

Turn a 2-minute product demo recording into 1080p ready-to-publish marketing videos just by typing what you need. Whether it's automating promotional video c...

Security Scan

The skill's behavior mostly matches a cloud video-rendering service, but there are inconsistencies and privacy/operational concerns you should know before installing or using it.

Purpose & Capability

Name/description match the runtime instructions: it uploads user video, creates sessions, and requests renders from a remote GPU backend (mega-api-prod.nemovideo.ai). The single required credential (NEMO_TOKEN) is appropriate for a cloud service. However, metadata declares NEMO_TOKEN as required yet the instructions include an automatic anonymous-token flow (inconsistency). The skill also expects to detect install-paths (~/.clawhub, ~/.cursor/skills/) for X-Skill-Platform attribution but those paths were not declared in the configPaths metadata.

Instruction Scope

SKILL.md instructs the agent to upload user-supplied video to an external API, create sessions, poll for render status, and post files/URLs — which is expected for this purpose. Concerns: it reads filesystem install paths to set X-Skill-Platform (access to user home dirs), and it instructs generating/storing/using an anonymous token when NEMO_TOKEN is absent despite NEMO_TOKEN being listed as required. The skill will transmit user video and session state to a third-party endpoint — users should understand that uploaded media and metadata leave their machine.

Install Mechanism

Instruction-only skill with no install spec and no code files; nothing is written to disk by an installer. This is the lowest installation risk surface.

Credentials

Only NEMO_TOKEN is requested, which is proportionate for a cloud API. But there's a mismatch: metadata marks NEMO_TOKEN required while the instructions implement an anonymous-token acquisition flow (network call to get a short-lived token). No other credentials are requested, which is appropriate.

Persistence & Privilege

always is false and there is no install persistence. The skill can be invoked autonomously (platform default) but it does not request elevated persistent privileges or modify other skills' configs.

What to consider before installing

This skill appears to be what it says — a cloud-based video rendering helper — but exercise caution before installing or using it. Key points to consider: - Data privacy: any video you upload will be sent to https://mega-api-prod.nemovideo.ai. Do not upload sensitive or confidential footage unless you trust that domain and its operator and have reviewed their privacy/terms. The skill's owner is unknown. - Token behavior: the metadata declares a required NEMO_TOKEN, but the instructions will auto-request an anonymous token if none is present. That automatic flow is not inherently malicious but is inconsistent with the declared requirements; clarify whether you must supply your own token or if the skill will always create/hold ephemeral tokens. - Filesystem access: the instructions ask the agent to detect install paths (e.g., ~/.clawhub, ~/.cursor/skills/) which implies reading locations under your home directory. If you want to limit exposure, avoid running this skill in environments with sensitive files or use sandboxes. - Verify the service: the API host (mega-api-prod.nemovideo.ai) is not documented in the skill's source/homepage. If you rely on this service for business or sensitive content, ask the skill author for official documentation, privacy policy, and ownership details. If you decide to proceed: prefer providing your own service credentials only if you trust the operator, review what files you upload, and consider testing with non-sensitive sample videos first. If you want a higher-assurance option, request a self-hosted or open-source alternative from the author.

Getting Started

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

Try saying:

• "convert a 2-minute product demo recording into a 1080p MP4"
• "turn this footage into a 30-second promotional video with captions and a call-to-action"
• "automating promotional video creation from raw footage 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.

AI Video Marketing Automator — Automate and Export Marketing Videos

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

A quick example: upload a 2-minute product demo recording, type "turn this footage into a 30-second promotional video with captions and a call-to-action", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter source clips under 3 minutes produce the most focused marketing cuts.

Matching Input to Actions

User prompts referencing ai video marketing automator, 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 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.

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

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

API base: https://mega-api-prod.nemovideo.ai

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: {"urls":["<url>"],"source_type":"url"}

Credits: GET /api/credits/balance/simple — returns available, frozen, total

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, data.state.generated_media

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

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

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

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.

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)

Common Workflows

Quick edit: Upload → "turn this footage into a 30-second promotional video with captions and a call-to-action" → 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 "turn this footage into a 30-second promotional video with captions and a call-to-action" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across ad platforms and social media.