Video Editing With Logo

add video clips into logo-branded videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. marketers use it for adding a brand logo watermar...

Security Scan

The skill's requests and instructions align with its stated purpose (sending videos to a cloud render service and adding a logo); it mainly needs one API token and makes network calls to that service, which is coherent — but review privacy and token handling before use.

Purpose & Capability

The name and description (add a logo overlay to videos) match the instructions: uploading video files, creating a session, sending SSE messages, and requesting renders from a cloud API. The single declared credential (NEMO_TOKEN) and the external API host are consistent with a cloud render backend. Minor metadata mismatch: the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata showed no required config paths.

Instruction Scope

The runtime instructions direct the agent to perform network calls to https://mega-api-prod.nemovideo.ai (anonymous-token, session creation, upload, SSE, render/poll) and to upload user files to that service — this is expected for a cloud video-editing skill. The doc also asks the agent to auto-generate anonymous tokens when NEMO_TOKEN is not present and to include attribution headers. Users should be aware that your uploaded media and any generated/anonymous tokens will be sent to an external service.

Install Mechanism

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

Credentials

Only one required environment variable is declared (NEMO_TOKEN), which is appropriate for authenticating to the backend. The skill also documents a fallback anonymous-token flow (network call to obtain a temporary token) — that's coherent but worth noting because the agent will obtain/store a token on behalf of the user if none is supplied. Tokens grant the ability to perform uploads and renders on the service, so treat them as sensitive.

Persistence & Privilege

always is false and the skill doesn't request permanent platform-wide privileges. The instructions describe creating and using a session token for its own operations; there is no request to modify other skills or global agent settings.

Assessment

This skill uploads your videos to an external cloud service (mega-api-prod.nemovideo.ai) to apply a logo overlay. Before installing or using it: (1) Confirm you are comfortable with the service receiving your media (privacy and IP concerns). (2) Provide only a token (NEMO_TOKEN) you intend to grant upload/render rights to; if you don't provide one the skill will call the service to create an anonymous temporary token, which also allows uploads. (3) Note the minor metadata mismatch (a config path is present in the SKILL.md frontmatter but not in registry metadata) — harmless but worth verifying. (4) Check pricing/limits and retention policies (the skill mentions credits, free tier limits, and possible 402 export blocks). If any of these raise concerns, avoid supplying permanent credentials and consider testing with non-sensitive sample videos first.

Getting Started

Ready when you are. Drop your video clips here or describe what you want to make.

Try saying:

• "add a 60-second product demo video into a 1080p MP4"
• "add my logo to the top-right corner of the video"
• "adding a brand logo watermark to videos for marketers"

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.

Video Editing With Logo — Add Logo Overlay to Videos

Drop your video clips in the chat and tell me what you need. I'll handle the AI logo overlay on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 60-second product demo video, ask for add my logo to the top-right corner of the video, and about 20-40 seconds later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — use a PNG logo with a transparent background for the cleanest overlay result.

Matching Input to Actions

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

Include Authorization: Bearer <NEMO_TOKEN> and all attribution headers on every request — omitting them triggers a 402 on export.

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

Header	Value
X-Skill-Source	video-editing-with-logo
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 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 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 → "add my logo to the top-right corner of the video" → Download MP4. Takes 20-40 seconds 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 "add my logo to the top-right corner of the video" — 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.