Ai Video For Affiliate Marketing

create product images or clips into affiliate promo videos with this skill. Works with MP4, MOV, JPG, PNG files up to 500MB. affiliate marketers use it for g...

Security Scan

The skill appears to do what its name says (upload media and call a third‑party rendering API), but there are some inconsistencies and unclear behaviors (metadata vs. SKILL.md, automatic anonymous token creation, and unspecified local storage) that you should understand before installing or using it.

Purpose & Capability

The declared purpose (creating affiliate promo videos) aligns with the runtime instructions: the SKILL.md describes uploading media and calling a remote rendering API. Requesting a single token (NEMO_TOKEN) is appropriate for this integration. Minor inconsistency: the registry metadata presented to you said "Required config paths: none," but the SKILL.md frontmatter includes configPaths ["~/.config/nemovideo/"], which suggests the skill expects a local config directory.

Instruction Scope

Instructions are focused on the remote nemovideo API (session creation, SSE chat, upload, export). Notable behaviors: (1) If NEMO_TOKEN is missing, the instructions direct the agent to automatically request an anonymous token from the service (network call). (2) The skill instructs the agent to "store the returned session_id" for subsequent requests but does not specify where or how to persist it. (3) It directs the agent to read this file's YAML frontmatter and to detect an install path (e.g., ~/.clawhub/ or ~/.cursor/skills/) to set X-Skill-Platform — that requires checking local filesystem paths. These are plausible for the feature but worth noting because they involve network activity, token handling, and local file/dir checks.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest-risk pattern for installation (nothing is pulled or executed on disk by an installer). All runtime actions are API calls described in the SKILL.md.

Credentials

Only one required env var (NEMO_TOKEN) is declared and used as the Authorization bearer token for the service, which is proportionate. However, the skill will create an anonymous token for you if NEMO_TOKEN is not present, which means it will make network requests to obtain and then use temporary credentials (100 free credits, 7 days). Consider whether you want the agent to obtain and store such tokens automatically.

Persistence & Privilege

The skill is not always: true and does not request elevated platform privileges. It does indicate a config path (~/.config/nemovideo/) in its frontmatter and instructs storing session_id for ongoing calls; where and how that state is persisted is not specified. That ambiguity is relevant because it affects whether tokens or session identifiers might be written to disk.

What to consider before installing

This skill sends your uploaded media and instructions to a third‑party service (mega-api-prod.nemovideo.ai) for cloud GPU rendering — that's expected for a video-rendering skill but means you should expect your media and metadata to leave your machine. Before enabling: (1) Decide whether you want the agent to auto-request an anonymous token on your behalf (it will make network calls and receive a 7-day token). (2) Ask or check whether session tokens or the skill's config are written to ~/.config/nemovideo/ (the frontmatter mentions it but the registry metadata did not). (3) Review the service's privacy/security policy if you care about affiliate links or product images being uploaded. (4) If you prefer control, set NEMO_TOKEN yourself (rather than allowing anonymous-token creation) and confirm where session state is stored or persisted. The skill is not clearly malicious, but these unclear storage and automatic-network behaviors warrant caution.

Getting Started

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

Try saying:

• "create my product images or clips"
• "export 1080p MP4"
• "create a 30-second promo video with"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

AI Video for Affiliate Marketing — Create Affiliate Promo Videos Fast

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

A quick example: upload three product photos and a affiliate link description, type "create a 30-second promo video with voiceover and call-to-action for my affiliate product", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: keep your video under 60 seconds for better click-through rates on affiliate links.

Matching Input to Actions

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

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

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

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "create a 30-second promo video with voiceover and call-to-action for my affiliate product" — 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 and social media.

Common Workflows

Quick edit: Upload → "create a 30-second promo video with voiceover and call-to-action for my affiliate product" → 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.