Free Video Generator By Script

generate written script into script-based videos with this skill. Works with TXT, DOCX, PDF, copied text files up to 500MB. marketers, content creators, educ...

Security Scan

The skill's declared intent (turn scripts into videos) matches its API usage, but it uploads user files and issues tokens to an external, unknown service and includes metadata that may cause the agent to leak environment/install-path details — so review before use.

Purpose & Capability

The skill claims to convert scripts to videos and its runtime instructions call a video-processing API (session creation, SSE, upload, render) that coherently matches that purpose. The only oddities: the registry metadata lists a config path (~/.config/nemovideo/) that isn't referenced in detail in the SKILL.md, and the skill source is unknown (no homepage), so provenance is limited.

Instruction Scope

Instructions tell the agent to upload local files (multipart uploads with files=@/path) and to POST messages and drafts to a remote API — this is expected for a renderer but also means any file the agent is asked to upload could be transmitted off-host. The skill also instructs deriving headers (including X-Skill-Platform) from install paths, which may cause the agent to surface local install-path information to the remote service. The SKILL.md does not explicitly restrict which local paths may be used, creating a potential for accidental exfiltration of sensitive files if the agent is asked to upload arbitrary paths.

Install Mechanism

No install spec and no code files — instruction-only skill. This is lower-risk because nothing is written to disk by the skill itself. The scanner had no code to analyze.

Credentials

The skill only requires a single credential, NEMO_TOKEN, which is proportional to calling a third-party API. It also documents a fallback: generating an anonymous token via the service's anonymous-token endpoint if no token is set. Metadata declares a config path (~/.config/nemovideo/); while plausible for a video tool, this could be used to read stored credentials if the agent were instructed to do so — the SKILL.md does not explicitly require reading that path, but the presence of the configPaths value should be noted.

Persistence & Privilege

always is false and the skill is user-invocable with normal autonomous-invocation allowed. The skill asks the agent to save session_id values for the session lifecycle, which is reasonable for a long-running render workflow. There is no indication it modifies other skills or requests permanent elevated privileges.

What to consider before installing

This skill is largely coherent for generating videos, but it uploads user files and talks to an external API at mega-api-prod.nemovideo.ai (source unknown). Before installing: (1) Only upload non-sensitive files (do not allow automatic upload of system files like ~/.ssh, credentials, or config directories). (2) Prefer setting your own NEMO_TOKEN tied to an account you control rather than relying on anonymous tokens. (3) Be aware the skill may include headers that reveal local install-path metadata; if you care about leaking environment details, avoid enabling this skill. (4) If you need stronger assurance, ask the publisher for provenance/terms/privacy or avoid sending private content to this service.

Getting Started

Share your written script and I'll get started on AI video creation. Or just tell me what you're thinking.

Try saying:

• "generate my written script"
• "export 1080p MP4"
• "turn this script into a video"

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 Video Generator by Script — Turn Scripts Into Shareable Videos

Send me your written script and describe the result you want. The AI video creation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a 200-word product launch script, type "turn this script into a video with visuals and voiceover", and you'll get a 1080p MP4 back in roughly 1-2 minutes. All rendering happens server-side.

Worth noting: shorter scripts under 150 words produce tighter, faster-rendering videos.

Matching Input to Actions

User prompts referencing free video generator by script, 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.

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

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.

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.

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)

Error Handling

Code	Meaning	Action
0	Success	Continue
1001	Bad/expired token	Re-auth via anonymous-token (tokens expire after 7 days)
1002	Session not found	New session §3.0
2001	No credits	Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account"
4001	Unsupported file	Show supported formats
4002	File too large	Suggest compress/trim
400	Missing X-Client-Id	Generate Client-Id and retry (see §1)
402	Free plan export blocked	Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export."
429	Rate limit (1 token/client/7 days)	Retry in 30s once

Common Workflows

Quick edit: Upload → "turn this script into a video with visuals and voiceover" → 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn this script into a video with visuals and voiceover" — concrete instructions get better results.

Max file size is 500MB. Stick to TXT, DOCX, PDF, copied text for the smoothest experience.

Export as MP4 for widest compatibility across social and web platforms.