Ai Video Generator For Marketing

Get polished marketing videos ready to post, without touching a single slider. Upload your images or text (MP4, MOV, PNG, JPG, up to 500MB), say something li...

Security Scan

The skill's stated purpose (cloud video generation) mostly matches its instructions, but there are metadata/instruction inconsistencies (required config path vs registry, required env var vs fallback anonymous-token flow) and the skill instructs the agent to obtain and use runtime tokens from an external API — things you should review before installing.

Purpose & Capability

Name and description match the runtime instructions (cloud-rendering of videos via nemo backend). Requesting a NEMO_TOKEN and using the nemovideo API is coherent with a video-generation service. However the SKILL.md metadata lists a config path (~/.config/nemovideo/) while the registry metadata earlier indicated no required config paths — this mismatch should be resolved.

Instruction Scope

Instructions are mostly scoped to uploading media, creating sessions, SSE streaming, polling render status, and exporting results. They do instruct the agent to check environment for NEMO_TOKEN and, if missing, to POST to an anonymous-token endpoint to obtain a token — which effectively causes credential acquisition at runtime. The skill also tells the agent to read the skill's frontmatter and to detect install path for an X-Skill-Platform header (this requires some filesystem awareness). There are no instructions to read unrelated secrets or user files, but the token-fetch and install-path detection are noteworthy.

Install Mechanism

Instruction-only skill with no install spec or code to download — low install risk. Nothing is written to disk by an install step in the package metadata.

Credentials

Registry metadata declares NEMO_TOKEN as the required primary credential which is appropriate for a nemo API integration. But SKILL.md provides a fallback anonymous-token acquisition flow if NEMO_TOKEN is absent, and the frontmatter mentions a config path (~/.config/nemovideo/). The presence of both 'required env var' and a runtime token-acquisition path is inconsistent and unclear: will the skill use a user-provided token, create a short-lived anonymous token, or persist tokens into a config directory? The skill does instruct not to expose tokens in messages, but it's not explicit whether tokens are persisted to disk or only held in memory.

Persistence & Privilege

The skill does not request 'always:true' and does not ask to modify other skills or system-wide settings. It appears to rely on runtime session tokens and session IDs rather than demanding long-term elevated privileges.

What to consider before installing

What to check before installing: - The domain the skill calls is https://mega-api-prod.nemovideo.ai — verify you trust this service (privacy, data retention, where uploaded media goes). - Metadata mismatch: the registry says no required config paths, but SKILL.md frontmatter mentions ~/.config/nemovideo/. Ask the publisher whether the skill will read/write that path (token cache or logs). - Credential flow: the skill declares NEMO_TOKEN as required, but also describes obtaining an anonymous token via an API if none is present. Ask whether the skill will persist that anonymous token anywhere and whether it will reuse it across sessions. If you prefer to supply your own token, confirm that it will be used instead of anonymous tokens. - Network access: the skill depends on external network calls and uploads your media to a third-party backend. If your media is sensitive, do not use this skill without confirming the provider's terms and storage practices. - Attribution headers: the skill will attempt to detect install path to set X-Skill-Platform headers. Confirm whether the skill needs filesystem access for that detection and whether that could expose local data. If any answers are missing or you don't trust the endpoint/provider, treat this as risky and do not install. If you proceed, prefer supplying your own NEMO_TOKEN and ask the publisher to correct metadata inconsistencies and document token persistence explicitly.

Getting Started

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

Try saying:

• "generate three product photos and a brand tagline into a 1080p MP4"
• "create a 30-second promotional video for my product launch with background music and captions"
• "generating branded promotional videos from product images or scripts 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 Generator for Marketing — Generate Branded Promotional Videos

Drop your images or text 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 tagline, ask for create a 30-second promotional video for my product launch with background music and captions, 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 — shorter scripts under 60 seconds produce the most focused and shareable marketing clips.

Matching Input to Actions

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

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

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

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.

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.

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.

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

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

Common Workflows

Quick edit: Upload → "create a 30-second promotional video for my product launch with background music and captions" → 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 "create a 30-second promotional video for my product launch with background music and captions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across ad platforms like Meta and Google Ads.