For Marketing Video Editing With

Cloud-based for-marketing-video-editing-with tool that handles editing product and brand videos for social media campaigns. Upload MP4, MOV, AVI, WebM files...

Security Scan

The skill's behavior mostly matches a cloud video-editing integration, but there are small incoherences (metadata vs registry and assumptions about local config/install paths) and it will upload user videos and request/handle tokens for an external service — verify before use.

Purpose & Capability

The skill's name, description, and runtime instructions consistently describe a cloud-based video editing service that accepts uploads and returns rendered MP4s; asking for a single API token (NEMO_TOKEN) is proportional. However, the SKILL.md frontmatter claims a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this discrepancy is unexplained.

Instruction Scope

SKILL.md instructs the agent to obtain or use NEMO_TOKEN, create sessions, upload user media, stream SSE chat, poll for renders, and save session_id. Those actions are expected for a remote render service. The file does not instruct the agent to read arbitrary system files or unrelated credentials. It does assume the agent can 'auto-detect' an install path for X-Skill-Platform and references a local config path in metadata — these assumptions may be inconsistent for an instruction-only skill and could cause the agent to access paths that aren't necessary.

Install Mechanism

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

Credentials

Only one environment variable (NEMO_TOKEN) is declared, which is reasonable for an API-backed service. The SKILL.md frontmatter also lists a config path (~/.config/nemovideo/) which was not reflected in the registry requirements; if the skill actually reads that path it would expand its scope and access local files, so this mismatch should be clarified before trusting it with sensitive data.

Persistence & Privilege

The skill is not marked always:true and does not request persistent system-wide privileges. It does instruct saving transient session_id and using tokens for API calls, which is typical and not excessive on its face.

What to consider before installing

This skill appears to be a straightforward cloud video-editing integration, but there are a few things to check before installing or using it: 1) Confirm the service domain (mega-api-prod.nemovideo.ai) and its privacy/data-retention policy — you will be uploading video files to that external endpoint. 2) Ask the publisher why SKILL.md metadata lists ~/.config/nemovideo/ (a local config path) while the registry shows no config paths; clarify whether the agent will read or write any local files. 3) Be cautious with sensitive footage — prefer test or anonymized clips until you trust the service. 4) If you don't already have a trusted NEMO_TOKEN, the skill’s anonymous-token flow issues ephemeral tokens; confirm how/where tokens and session IDs are stored by your agent. If the publisher cannot explain the config-path mismatch or provide a privacy/terms link, treat the skill as higher risk and avoid uploading confidential material.

Getting Started

Share your raw video clips and I'll get started on AI marketing editing. Or just tell me what you're thinking.

Try saying:

• "edit my raw video clips"
• "export 1080p MP4"
• "trim the footage, add branded text"

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.

For Marketing Video Editing With — Edit and Export Marketing Videos

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

A quick example: upload a 60-second product demo recording, type "trim the footage, add branded text overlays, and include a call-to-action at the end", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: keep clips under 2 minutes for faster processing and snappier marketing content.

Matching Input to Actions

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

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

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

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

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.

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

Common Workflows

Quick edit: Upload → "trim the footage, add branded text overlays, and include a call-to-action at the end" → 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 footage, add branded text overlays, and include a call-to-action at the end" — 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 and social media.