Media Copywriter Generator

generate video clips or images into copy-enhanced videos with this skill. Works with MP4, MOV, AVI, WebM files up to 500MB. marketers use it for generating a...

Security Scan

The skill's requests and runtime instructions align with its stated purpose (uploading media and calling a nemo video render API); minor metadata inconsistencies and the fact it will send user media to an external service are the main things to check before use.

Purpose & Capability

The skill claims to create copy-enhanced videos and all required operations (session creation, SSE messaging, upload, render/export) match that purpose. One inconsistency: the SKILL.md frontmatter mentions a config path (~/.config/nemovideo/) and lists NEMO_TOKEN as required, but the registry metadata provided with this evaluation reported no required config paths — this mismatch should be resolved but does not by itself indicate maliciousness.

Instruction Scope

Runtime instructions are narrowly scoped to: use NEMO_TOKEN (or fetch an anonymous token), create a session, stream messages, upload media files, and poll export status. The agent is instructed to send user media to the documented nemo API endpoints and not to read unrelated system files. The frontmatter's mention of an install path / config path and the requirement to auto-detect X-Skill-Platform from an install path could imply reading local paths, so confirm whether the agent implementation will actually access ~/.config or install paths.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so it does not download or install third-party packages or write executable artifacts to disk. That is the lowest-risk install model.

Credentials

The only credential required is NEMO_TOKEN (declared as the primary credential), which is appropriate for a third-party cloud render service. The instructions also define an anonymous-token flow if no token is present, which contacts https://mega-api-prod.nemovideo.ai to obtain a short-lived token — expected but worth noting. No unrelated secrets or broad credential access are requested.

Persistence & Privilege

The skill does not request permanent presence (always: false) and does not ask to modify other skills or system-wide agent settings. Autonomous invocation is allowed (platform default) but not combined with any unusually broad privileges.

Assessment

This skill appears to do what it says, but before installing: 1) Verify you're comfortable uploading media and any associated metadata to the domain https://mega-api-prod.nemovideo.ai (check their privacy/terms). 2) Provide NEMO_TOKEN only if you trust the service; if you don't have one, the skill will obtain an anonymous token from that domain — understand what that implies for retention and privacy. 3) Ask the publisher or inspect runtime logs to confirm the skill does not read unrelated local config paths (the SKILL.md references ~/.config/nemovideo/ and auto-detecting an install path). 4) Do not supply other secrets (AWS, GitHub, etc.). 5) If you need higher assurance, request the publisher provide an explicit privacy/data-flow statement or a hosted API documentation link for the nemo endpoints used.

Getting Started

Send me your video clips or images and I'll handle the AI copy generation. Or just describe what you're after.

Try saying:

• "generate a 60-second product demo video into a 1080p MP4"
• "write engaging captions and ad copy for this video to use across social media"
• "generating ad copy and captions for 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.

Media Copywriter Generator — Generate Copy for Videos

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

A quick example: upload a 60-second product demo video, type "write engaging captions and ad copy for this video to use across social media", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: shorter videos yield more focused and usable copy suggestions.

Matching Input to Actions

User prompts referencing media copywriter generator, 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.

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

Header	Value
X-Skill-Source	media-copywriter-generator
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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.

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.

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

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)

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 → "write engaging captions and ad copy for this video to use across social media" → 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 "write engaging captions and ad copy for this video to use across social media" — 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.