Best Video Script Writer

Turn a 2-minute product explainer brief into 1080p ready-to-use scripts just by typing what you need. Whether it's generating video scripts from a topic or b...

Security Scan

The skill's instructions broadly match a cloud video-rendering service, but its name/description (a 'script writer') and registry metadata don't fully align with what it actually does, and the runtime instructions ask the agent to read local install metadata and to obtain/use a bearer token for an external API — things you should understand before enabling it.

Purpose & Capability

The name/description emphasize generating video scripts, but the instructions describe a full cloud render/upload/export pipeline (creating sessions, uploading media, starting renders, polling status and returning MP4 URLs). Requiring an API token for a cloud render service is reasonable, but the capability is broader than the advertised 'script writer' and may surprise users expecting only text/script output.

Instruction Scope

The SKILL.md directs network calls to an external API (mega-api-prod.nemovideo.ai), file uploads, SSE stream handling, and instructs the agent to read the SKILL.md YAML frontmatter and detect install paths (~/.clawhub, ~/.cursor/skills/) at runtime. Reading install paths and frontmatter is beyond simple script-writing and accesses local environment/metadata — that is scope creep and a privacy surface worth noting.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing is written to disk by an installer. That is lower risk than an install-from-URL package.

Credentials

The skill requests a single credential (NEMO_TOKEN) which is appropriate for calling a proprietary cloud API. However, the token is used to create sessions and perform renders/uploads on behalf of the user — giving this token grants the skill ability to act on the associated account. The SKILL.md's frontmatter also references a config path (~/.config/nemovideo/) that isn't reflected in the registry metadata, a minor inconsistency to be aware of.

Persistence & Privilege

The skill is not always-enabled and does not request system-wide persistent privileges. It does create and use short-lived session tokens on the service, which is normal for this kind of integration.

What to consider before installing

This skill will call an external video-rendering API and may upload your files; it asks for (or will acquire) a bearer token (NEMO_TOKEN) that allows actions and exports on your account. Before enabling: verify you trust the domain (mega-api-prod.nemovideo.ai) and its privacy/terms; consider using an anonymous/free token rather than a long-lived account token; be aware the skill will read its own frontmatter and try to detect install paths (it may see user environment metadata); and note the advertised 'script writer' functionality actually performs full render/export operations. If you need only text/script generation, consider a skill that does not upload or render media. If anything is unclear, ask the publisher for a privacy/usage policy or a scoped API token that limits actions.

Getting Started

Send me your topic or brief and I'll handle the AI script generation. Or just describe what you're after.

Try saying:

• "generate a 2-minute product explainer brief into a 1080p MP4"
• "write a 60-second YouTube script about our new fitness app with a hook and call to action"
• "generating video scripts from a topic or brief for YouTubers, marketers, content creators"

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 Video Script Writer — Generate Scripts for Any Video

Drop your topic or brief in the chat and tell me what you need. I'll handle the AI script generation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 2-minute product explainer brief, ask for write a 60-second YouTube script about our new fitness app with a hook and call to action, 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 — include your target audience and tone in the prompt for tighter, more on-brand scripts.

Matching Input to Actions

User prompts referencing best video script writer, 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: best-video-script-writer
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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

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 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 "write a 60-second YouTube script about our new fitness app with a hook and call to action" — 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.

Common Workflows

Quick edit: Upload → "write a 60-second YouTube script about our new fitness app with a hook and call to action" → 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.