Ai Video Editor For Marketing

Get polished marketing videos ready to post, without touching a single slider. Upload your raw video footage (MP4, MOV, AVI, WebM, up to 500MB), say somethin...

Security Scan

The skill's requirements and runtime instructions are coherent with a cloud video-editing service: it only asks for a service token and describes API calls to that service, with no install steps or unrelated credential requests — but the service domain and owner are unknown so exercise normal caution before uploading sensitive footage.

Purpose & Capability

Name/description (cloud AI video editing) match the declared env var (NEMO_TOKEN) and the SKILL.md API endpoints for uploading, rendering, and exporting videos. Requesting a service token is expected for a hosted editing service.

Instruction Scope

Instructions stick to session creation, upload, SSE messaging, polling render status, and download — all consistent with a remote render pipeline. Minor scope mismatch: metadata lists a config path (~/.config/nemovideo/) but the runtime instructions do not require reading it. The docs also show multipart uploads using local file paths (e.g., -F "files=@/path"), which assumes the agent can access a local path; in practice user-supplied chat file uploads or URLs would be used. This could cause an agent implementation to attempt filesystem access if not implemented carefully.

Install Mechanism

Instruction-only skill with no install steps and no code files — lowest installation risk.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is proportionate for a hosted API. The SKILL.md includes a fallback to request an anonymous token from the service if no env var is present — this is consistent with expected behavior and does not require unrelated secrets.

Persistence & Privilege

The skill does not request always:true, does not modify other skills, and has no install-time persistence; autonomous invocation is allowed by default but is not combined with other broad privileges here.

Assessment

This skill appears to be what it claims: a cloud-based AI video editor that needs a NEMO_TOKEN to call its API. Before installing/using: 1) Verify you trust the service domain (mega-api-prod.nemovideo.ai) and the skill owner because uploaded videos will be transmitted to that API. 2) Avoid uploading sensitive or confidential footage unless you understand the service's privacy/retention policy. 3) If you don't have a paid token, the skill will request an anonymous token automatically — prefer using temporary/anonymous tokens if you want to limit long-term access. 4) Note the SKILL.md shows multipart uploads using local file paths; confirm how your agent provides files (chat upload vs. local filesystem) to avoid unintended local file reads. If you need higher assurance, ask the publisher for a homepage/privacy statement or a known service identity before proceeding.

Getting Started

Send me your raw video footage and I'll handle the AI marketing video editing. Or just describe what you're after.

Try saying:

• "edit a 2-minute product demo recording into a 1080p MP4"
• "trim the pauses, add branded captions, and cut a 30-second version for Instagram ads"
• "turning raw footage into ready-to-publish marketing videos for marketers"

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

AI Video Editor for Marketing — Edit and Export Marketing Videos

Drop your raw video footage in the chat and tell me what you need. I'll handle the AI marketing video editing on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute product demo recording, ask for trim the pauses, add branded captions, and cut a 30-second version for Instagram ads, 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 — keeping clips under 90 seconds gives you faster processing and tighter ad-ready output.

Matching Input to Actions

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

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.

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	ai-video-editor-for-marketing
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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 Codes

• 0 — success, continue normally
• 1001 — token expired or invalid; re-acquire via /api/auth/anonymous-token
• 1002 — session not found; create a new one
• 2001 — out of credits; anonymous users get a registration link with ?bind=<id>, registered users top up
• 4001 — unsupported file type; show accepted formats
• 4002 — file too large; suggest compressing or trimming
• 400 — missing X-Client-Id; generate one and retry
• 402 — free plan export blocked; not a credit issue, subscription tier
• 429 — rate limited; wait 30s and retry 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 → "trim the pauses, add branded captions, and cut a 30-second version for Instagram ads" → 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 "trim the pauses, add branded captions, and cut a 30-second version for Instagram ads" — 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 like Meta and Google.