Generate Ai Video For Marketing

generate images or clips into marketing video MP4 with this skill. Works with MP4, MOV, JPG, PNG files up to 500MB. marketers use it for creating promotional...

Security Scan

The skill's declared requests and runtime instructions are internally consistent with a cloud-based AI video creation tool, but the package has no published source/homepage which lowers confidence and merits caution around uploads and token use.

Purpose & Capability

Name/description (generate marketing videos from images/clips) align with the declared requirement (NEMO_TOKEN) and the SKILL.md which documents API endpoints for upload, session, render, and credits. There are no unrelated environment variables or unexpected binaries requested.

Instruction Scope

SKILL.md stays on-topic: it describes authenticating, creating sessions, uploading user media, streaming SSE for edits, and exporting MP4s. It does instruct generating anonymous tokens if NEMO_TOKEN is absent and to read/install-paths to set an X-Skill-Platform header, which are reasonable for attribution but do require filesystem/path inspection and network calls.

Install Mechanism

Instruction-only skill with no install spec or downloaded code, so nothing is written or executed on disk by an installer. This is the lowest-risk install posture.

Credentials

Only NEMO_TOKEN is required and is the declared primary credential; that's proportionate for a cloud API. The skill also documents creating an anonymous token via the backend if the env var is missing — this implies the agent will make network calls to mint tokens and may persist them in the declared config path (~/.config/nemovideo/).

Persistence & Privilege

always:false and no request to modify other skills or system-wide settings. The skill may store session tokens or client IDs under its own config path as described, which is normal for this type of integration.

Assessment

This skill appears to do what it says: it uploads user media to a cloud backend and returns rendered MP4s. Before installing, confirm you trust the backend domain (mega-api-prod.nemovideo.ai) because your uploaded images/clips and any account token (NEMO_TOKEN) will be sent to that service. Note the skill will try to mint an anonymous token if none is provided and may write session data to ~/.config/nemovideo/. If you need stronger assurance, ask the publisher for a homepage/source repo and a privacy/billing policy and avoid uploading sensitive assets until you verify the service.

Getting Started

Share your images or clips and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "generate my images or clips"
• "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.

Generate AI Video for Marketing — Create Marketing Videos from Assets

Send me your images or clips and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload three product photos and a brand logo, type "create a 30-second promotional video with text overlays and background music", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: using fewer than five assets speeds up generation significantly.

Matching Input to Actions

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

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.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is generate-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.

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

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

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.

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 social and ad platforms.