Video Script Bak

save video script text into backed up scripts with this skill. Works with MP4, MOV, TXT, DOCX files up to 200MB. content creators use it for backing up video...

Security Scan

The skill's requests and runtime instructions are largely consistent with its stated purpose (backing up/generating video-script-based media on a remote rendering backend), but there are a few minor metadata inconsistencies and expected privacy implications you should be aware of before use.

Purpose & Capability

The name/description match the instructions: the skill uploads script text and media to a remote rendering backend and returns rendered files. The single required credential (NEMO_TOKEN) is appropriate for a hosted service. Minor mismatch: the registry listed no required config paths, but the SKILL.md frontmatter declares a configPath (~/.config/nemovideo/). This is a metadata inconsistency that should be clarified.

Instruction Scope

All runtime instructions center on communicating with the nemovideo API endpoints and handling SSE/rendering workflow — consistent with the purpose. The skill instructs automatic anonymous token acquisition, creation of sessions, uploading files (up to 200MB), and polling exports. This requires sending user-provided script text and media to an external service (mega-api-prod.nemovideo.ai), which is expected for this functionality but has privacy implications. The SKILL.md also instructs hiding raw API responses and token values from the user, and to store session_id for later use; where/how the token/session are stored is not specified.

Install Mechanism

No install spec and no code files — instruction-only skill. Nothing is downloaded or written by the skill itself per the package contents, which reduces installation risk.

Credentials

Only one environment variable is required (NEMO_TOKEN), which fits the described external API usage. The skill describes generating an anonymous token automatically if not present. Be aware that generated tokens grant credits and are valid for a limited time; the SKILL.md suggests storing tokens/session_ids (and a config path appears in the frontmatter), so token persistence behavior should be confirmed before installing. No other unrelated credentials are requested.

Persistence & Privilege

The skill is not marked always:true and does not request system-wide privileges. It does instruct storing a session_id/token (persistence limited to the service) but does not ask to modify other skills or system configurations. Autonomous invocation is allowed (platform default).

Assessment

This skill appears to do what it says: it will send your script text and optional media files to an external rendering service (mega-api-prod.nemovideo.ai) and return rendered assets. Before installing or using it: (1) confirm you are comfortable uploading the (possibly sensitive) script/media to that external domain; (2) ask the publisher where the token and session_id will be stored (frontmatter mentions ~/.config/nemovideo/ but registry metadata omitted config paths); (3) if you prefer control, provide your own NEMO_TOKEN rather than letting the skill auto-create one; (4) avoid sending personally identifiable or secret data to the skill until you verify the backend/owner and privacy policy. The source is unknown and the package is unreviewed — exercise the usual caution.

Getting Started

Send me your video script text and I'll handle the script backup generation. Or just describe what you're after.

Try saying:

• "save a completed 3-minute YouTube video script into a 1080p MP4"
• "save and back up my video script so I can restore it later"
• "backing up video scripts before editing or publishing for content creators"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Video Script Backup — Save and Restore Video Scripts

Send me your video script text and describe the result you want. The script backup generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a completed 3-minute YouTube video script, type "save and back up my video script so I can restore it later", and you'll get a 1080p MP4 back in roughly under 30 seconds. All rendering happens server-side.

Worth noting: back up your script before making major edits so you can restore the original at any time.

Matching Input to Actions

User prompts referencing video script bak, 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.

All calls go to https://mega-api-prod.nemovideo.ai. The main endpoints:

1. Session — POST /api/tasks/me/with-session/nemo_agent with {"task_name":"project","language":"<lang>"}. Gives you a session_id.
2. Chat (SSE) — POST /run_sse with session_id and your message in new_message.parts[0].text. Set Accept: text/event-stream. Up to 15 min.
3. Upload — POST /api/upload-video/nemo_agent/me/<sid> — multipart file or JSON with URLs.
4. Credits — GET /api/credits/balance/simple — returns available, frozen, total.
5. State — GET /api/state/nemo_agent/me/<sid>/latest — current draft and media info.
6. Export — POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/<id> every 30s for completed status and download URL.

Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

Headers are derived from this file's YAML frontmatter. X-Skill-Source is video-script-bak, 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).

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

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)

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

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result	Process internally, don't forward
heartbeat / empty data:	Keep waiting. Every 2 min: "⏳ Still working..."
Stream closes	Process final response

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

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 → "save and back up my video script so I can restore it later" → Download MP4. Takes under 30 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 "save and back up my video script so I can restore it later" — 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.