Best Copywriter Video

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

Security Scan

The skill's declared purpose (cloud video editing/copywriting) aligns with the single credential it requests and the API calls it instructs; nothing in the instructions appears to be doing unrelated or covert work, though there are a couple of minor metadata/instruction mismatches you should be aware of.

Purpose & Capability

Name/description match the runtime instructions: the SKILL.md describes uploading video, calling a cloud rendering API, editing voiceover/copy, and returning a processed MP4. Requesting a single API token (NEMO_TOKEN) is proportional to that purpose.

Instruction Scope

Instructions are focused on connecting to the nemo cloud API, managing sessions, uploading video, streaming SSE responses, and exporting results. They also instruct the agent to derive attribution headers from the YAML frontmatter and to detect the install path (e.g., ~/.clawhub/ or ~/.cursor/skills/) to set X-Skill-Platform. Detecting an install path implies reading well-known skill-installation paths; this is explainable for constructing headers but is broader filesystem access than a trivial API-only skill. The instructions also include a fallback anonymous-token flow (POST to /api/auth/anonymous-token) when NEMO_TOKEN is absent, which is reasonable but results in the agent calling an external endpoint and using returned tokens.

Install Mechanism

No install spec or code files are present; this is instruction-only, which is lowest risk. Nothing will be downloaded or written to disk by an installer step in the package metadata itself.

Credentials

Only one required environment variable (NEMO_TOKEN) is declared and used as the bearer token for the service — appropriate for a cloud API integration. The SKILL.md also references a config path (~/.config/nemovideo/) in its YAML frontmatter; registry metadata in the summary reported no required config paths, which is a minor inconsistency. The skill will also generate a UUID client id when needed and call the anonymous-token endpoint; no additional unrelated secrets are requested.

Persistence & Privilege

always:false and defaults for invocation are used. The skill does not request persistent platform-level privileges. It does rely on server-side sessions and tokens for render jobs (normal for cloud rendering).

Assessment

This skill appears to be what it says: a cloud video-editing/copywriting integration that requires an API token and uploads your video to nemo's rendering backend. Before installing or using it: - Be aware that video/audio files are uploaded to https://mega-api-prod.nemovideo.ai — do not use sensitive or private footage unless you trust that service and its privacy policy. - Provide a scoped or short‑lived NEMO_TOKEN if possible. If you omit NEMO_TOKEN the skill will obtain an anonymous token by calling the public anonymous-token endpoint (this is expected behavior but still results in network calls and data leaving your device). - The SKILL.md instructs the agent to inspect install paths and a config directory (~/.config/nemovideo/). The package registry summary did not list required config paths, so ask the publisher to clarify whether the skill will read or write that config directory and what it contains. - Confirm the endpoint domain (mega-api-prod.nemovideo.ai) is legitimate for your organization before giving any credentials. - If you have compliance concerns, test with non-sensitive sample videos first and monitor network activity. If you want higher assurance, request additional details from the publisher (privacy policy, endpoint ownership, what is stored server-side, retention of uploaded media, and whether the skill ever forwards data to other domains).

Getting Started

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

Try saying:

• "create a 60-second talking-head product demo clip into a 1080p MP4"
• "rewrite the voiceover script to be more persuasive and sync it to the video"
• "generating sales and marketing videos with professional copywriting 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.

Best Copywriter Video — Create Persuasive Marketing Videos

This tool takes your raw video footage and runs AI copywriting video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 60-second talking-head product demo clip and want to rewrite the voiceover script to be more persuasive and sync it to the video — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter clips with a clear call-to-action tend to convert better — keep videos under 90 seconds.

Matching Input to Actions

User prompts referencing best copywriter video, 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.

Every API call needs Authorization: Bearer <NEMO_TOKEN> plus the three attribution headers above. If any header is missing, exports return 402.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is best-copywriter-video, X-Skill-Version comes from the version field, and X-Skill-Platform is detected from the install path (~/.clawhub/ = clawhub, ~/.cursor/skills/ = cursor, otherwise unknown).

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

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)

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "rewrite the voiceover script to be more persuasive and sync it to 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 across ad platforms and social media.

Common Workflows

Quick edit: Upload → "rewrite the voiceover script to be more persuasive and sync it to the video" → 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.