Ai Video For Marketing Free

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

Security Scan

The skill's requirements and runtime instructions are consistent with a cloud video-rendering integration: it legitimately needs a NEMO_TOKEN and to upload user media to the external nemo API, and it does not request unrelated credentials or perform unexpected installs.

Purpose & Capability

The skill is described as a cloud video-rendering service and only requests a single service token (NEMO_TOKEN) and an optional config path under ~/.config/nemovideo/. These requirements match the stated purpose of calling the nemo backend API for uploads, session creation, rendering, and downloads.

Instruction Scope

SKILL.md instructs the agent to use NEMO_TOKEN (or acquire an anonymous token), create sessions, upload user-provided files (multipart or URL), drive SSE-based edit flows, and poll for render results — all consistent with a remote render service. It also asks the agent to read this skill's frontmatter and detect install path (~/.clawhub/ or ~/.cursor/skills/) to set attribution headers; reading the install path and the skill file is not strictly necessary for core function and is a minor scope expansion but not inherently malicious. Important: the instructions transmit user media and metadata to an external API (mega-api-prod.nemovideo.ai).

Install Mechanism

There is no install spec and no code files — the skill is instruction-only, so nothing is written to disk by an installer. This is the lowest-risk install model.

Credentials

Only one credential (NEMO_TOKEN) is required and declared as primary, which is proportionate for a remote service that requires bearer auth. The SKILL.md does not request additional unrelated secrets. It does reference a config path for nemo-specific config (~/.config/nemovideo/), which aligns with the service.

Persistence & Privilege

always is false and the skill does not request persistent platform-wide privileges. It asks the agent to read the skill frontmatter and detect install path for attribution headers, but it does not attempt to modify other skills or system-wide configs.

Scan Findings in Context

[no-findings] expected: The skill is instruction-only and contained only SKILL.md; the regex scanner had no code to analyze. Absence of findings is expected for such skills and is not evidence of safety by itself.

Assessment

This skill sends any media you provide to an external service (mega-api-prod.nemovideo.ai) and uses a NEMO_TOKEN for authentication. Before installing or using it: 1) Do not set NEMO_TOKEN to credentials that grant broad access to other services or sensitive data; prefer an account/token scoped for this use or use the anonymous token flow. 2) Be aware that uploaded media and metadata will leave your machine and be processed by nemo's servers—don’t upload confidential material unless you trust their terms/privacy. 3) The skill reads its own frontmatter and may probe standard install paths to populate attribution headers; this is mostly harmless but if you are concerned, confirm the skill only reads (not writes) those locations. 4) Verify the API domain and check the provider's privacy/retention policy if you plan to upload user/customer content. If you want higher assurance, ask the skill owner for a privacy statement or a self-hosting option.

Getting Started

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

Try saying:

• "create my raw footage or images"
• "export 1080p MP4"
• "turn these product images into a"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

AI Video for Marketing Free — Create and Export Marketing Videos

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

A quick example: upload three product photos and a logo file, type "turn these product images into 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: square and vertical formats work great for social ads — no extra steps needed.

Matching Input to Actions

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

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

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

• X-Skill-Source: ai-video-for-marketing-free
• 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

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.

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn these product images into 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 → "turn these product images into 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.