Free Copywriter Video

generate text or brief into copywritten promo videos with this skill. Works with TXT, DOCX, PDF, MP4 files up to 200MB. marketers use it for generating marke...

Security Scan

The skill's requests and runtime instructions are coherent with a cloud video-rendering integration (it needs a NEMO API token and makes network calls to nemovideo.ai); there are a few minor metadata inconsistencies and privacy considerations to review before installing.

Purpose & Capability

The name/description (generate promo videos from text) match the instructions: calls to a remote 'nemovideo' API, upload endpoints, render/export flows, and a single service token (NEMO_TOKEN). Requesting one API token for the external video service is proportionate to the stated purpose.

Instruction Scope

The SKILL.md instructs the agent to perform network actions (create session, post SSE messages, upload user files, start exports) and to read its own YAML frontmatter and detect install path to build attribution headers. These are reasonable for a GUI-mapped connector, but the skill will send user files and text to an external service (mega-api-prod.nemovideo.ai). The instructions also say to save session_id but do not specify where to persist it, which is vague but not inherently malicious.

Install Mechanism

There is no install specification and no code files: this is an instruction-only skill. That minimizes on-disk footprint and execution of third-party code; runtime network calls are the primary risk vector.

Credentials

Only a single credential (NEMO_TOKEN) is required, which is appropriate for a service-backed video renderer. Minor inconsistency: the registry metadata reported 'Required config paths: none' but the skill's frontmatter lists a config path (~/.config/nemovideo/). This mismatch should be clarified since the skill may expect or create that directory to store session or config data.

Persistence & Privilege

The skill does not request always:true and does not ask to modify other skills or system-wide settings. It will request network access and may persist session state (session_id / tokens) but there is no evidence it requires elevated privileges or permanent system presence beyond its own config area.

Assessment

This skill appears to legitimately wrap a third-party video-rendering API and will upload the text/files you provide to mega-api-prod.nemovideo.ai. Before installing or using it: 1) Decide whether you are comfortable sending potentially sensitive text, documents, or video files to that external service. 2) If you prefer control, supply your own NEMO_TOKEN (from the service) rather than letting the skill request an anonymous token. 3) Note the skill may create or use ~/.config/nemovideo/ to store session data—confirm you don’t mind that directory being written. 4) The skill’s source/homepage is not provided; if you need more assurance, ask the publisher for a privacy policy or contact info and verify the API domain. 5) The SKILL.md is otherwise coherent, but it’s vague about where session tokens are persisted—avoid sending secrets or highly sensitive files unless you trust the destination. If you want, I can draft a short checklist of what to avoid sending or a sample prompt that keeps data minimal.

Getting Started

Send me your text or brief and I'll handle the AI video creation. Or just describe what you're after.

Try saying:

• "generate a short product description or marketing brief into a 1080p MP4"
• "turn this product description into a 30-second promotional video with voiceover and captions"
• "generating marketing videos from written copy without hiring a copywriter for marketers"

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.

Free Copywriter Video — Generate videos from written copy

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

Say you have a short product description or marketing brief and want to turn this product description into a 30-second promotional video with voiceover and captions — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

Tip: shorter, punchier input copy produces tighter and more effective video scripts.

Matching Input to Actions

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: free-copywriter-video
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else 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

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute 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 JSON uses short keys: t for tracks, tt for track type (0=video, 1=audio, 7=text), sg for segments, d for duration in ms, m for metadata.

Example timeline summary:

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 "turn this product description into a 30-second promotional video with voiceover and captions" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across ad platforms and social media.

Common Workflows

Quick edit: Upload → "turn this product description into a 30-second promotional video with voiceover and captions" → 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.