Copywriter Generator

Skip the learning curve of professional editing software. Describe what you want — generate a 60-second video ad script with voiceover copy for a skincare pr...

Security Scan

The skill's requirements and runtime instructions are coherent with a remote video/copy generation service; it only needs an API token and instructs the agent how to talk to that service.

Purpose & Capability

The skill is a remote copy/video generation wrapper and legitimately requires a service token (NEMO_TOKEN) and network calls to the nemovideo API. Minor packaging inconsistency: the registry metadata reported no required config paths, while the SKILL.md frontmatter lists a config path (~/.config/nemovideo/). This looks like a documentation/metadata mismatch rather than a functional red flag, but it's worth noting.

Instruction Scope

SKILL.md confines runtime behavior to authenticating (using NEMO_TOKEN or obtaining an anonymous token), creating a session, uploading media, streaming SSE messages, polling render state, and returning results — all consistent with the described purpose. It does instruct the agent to read the skill's frontmatter and to detect install paths (~/.clawhub/, ~/.cursor/skills/) to set X-Skill-Platform, which implies reading some local paths/metadata; this is reasonable for attribution but is broader than purely network-only behavior.

Install Mechanism

No install spec and no code files — instruction-only skill. This is lower risk because nothing is downloaded or written to disk by an installer.

Credentials

Only NEMO_TOKEN is declared as required and is the primary credential; that matches the service interactions described. The skill also supports obtaining an anonymous temporary token if NEMO_TOKEN is absent. No unrelated credentials or broad environment access are requested.

Persistence & Privilege

always:false and no indication the skill requests persistent system-wide privileges or modifies other skills. Autonomous invocation is allowed (platform default) but is not combined with any unusual privileges here.

Assessment

This skill appears to do what it claims — it talks to a third-party nemovideo API and needs your NEMO_TOKEN (or will obtain a temporary anonymous token) to render videos. Before installing or using it: (1) Confirm you trust the domain (mega-api-prod.nemovideo.ai) and review its privacy/terms because uploaded media (up to 200MB) will be sent to that service. (2) Only supply an API token you control; treat NEMO_TOKEN like a password and rotate/revoke it if unsure. (3) Be aware the skill will add attribution headers (skill source/version/platform) to requests and may read its own frontmatter and detect install paths for that purpose. (4) The metadata mismatch about config paths is likely harmless but verify the skill won't access any other local files you care about. If you need stronger assurances, ask the author for a privacy policy, the exact token scopes, and confirmation they won't persist or share uploaded content outside the service.

Getting Started

Share your text brief or script and I'll get started on AI copy generation. Or just tell me what you're thinking.

Try saying:

• "generate my text brief or script"
• "export 1080p MP4"
• "generate a 60-second video ad script"

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.

Copywriter Generator — Generate Video Scripts and Copy

Send me your text brief or script 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 30-word product description brief, type "generate a 60-second video ad script with voiceover copy for a skincare product", and you'll get a 1080p MP4 back in roughly 20-40 seconds. All rendering happens server-side.

Worth noting: shorter, more specific briefs produce tighter and more usable copy.

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
/api/tasks/me/with-session/nemo_agent	POST	Start a new editing session. Body: {"task_name":"project","language":"<lang>"}. Returns session_id.
/run_sse	POST	Send a user message. Body includes app_name, session_id, new_message. Stream response with Accept: text/event-stream. Timeout: 15 min.
/api/upload-video/nemo_agent/me/<sid>	POST	Upload a file (multipart) or URL.
/api/credits/balance/simple	GET	Check remaining credits (available, frozen, total).
/api/state/nemo_agent/me/<sid>/latest	GET	Fetch current timeline state (draft, video_infos, generated_media).
/api/render/proxy/lambda	POST	Start export. Body: {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll status every 30s.

Accepted file types: 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: copywriter-generator
• 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.

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 60-second video ad script with voiceover copy for a skincare product" — concrete instructions get better results.

Max file size is 200MB. Stick to MP4, MOV, TXT, DOCX for the smoothest experience.

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "generate a 60-second video ad script with voiceover copy for a skincare product" → 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.