Free Video Generator From Script

v1.0.0

Get script-based videos ready to post, without touching a single slider. Upload your written script (TXT, DOCX, PDF, plain text, up to 500MB), say something...

⭐ 0· 70·0 current·0 all-time

by@linmillsd7

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for linmillsd7/free-video-generator-from-script.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Free Video Generator From Script" (linmillsd7/free-video-generator-from-script) from ClawHub.
Skill page: https://clawhub.ai/linmillsd7/free-video-generator-from-script
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install free-video-generator-from-script

ClawHub CLI

Package manager switcher

npx clawhub@latest install free-video-generator-from-script

Security Scan

VirusTotal

Pending

View report →

OpenClaw

Benign

high confidence

✓

Purpose & Capability

Name/description match the declared requirements: the skill calls a nemovideo backend, needs a NEMO_TOKEN (primary credential), and references a nemovideo config path — all of which are proportional to cloud video rendering.

ℹ

Instruction Scope

SKILL.md explicitly instructs the agent to use NEMO_TOKEN (or obtain an anonymous token via POST), upload user files, stream SSE, poll render status, and include attribution headers (X-Skill-Source, X-Skill-Version, X-Skill-Platform). Those actions will transmit user content and environment-derived headers to mega-api-prod.nemovideo.ai; the header that detects install path could leak platform/install-location metadata.

✓

Install Mechanism

No install spec or code is present (instruction-only). Nothing is downloaded or written to disk by an installer — lowest install risk.

✓

Credentials

Only a single credential (NEMO_TOKEN) and a service-specific config path are declared. That aligns with the skill's stated cloud API usage; no unrelated secrets or multiple unrelated env vars are requested.

✓

Persistence & Privilege

always is false and the skill does not request permanent/privileged presence or modify other skills. Autonomous invocation is enabled by default but not combined with other high-risk factors here.

Assessment

This skill will send any uploaded scripts/media and a bearer token (NEMO_TOKEN or an anonymous token it fetches) to https://mega-api-prod.nemovideo.ai to render videos. There is no installer, but the service will receive files and some environment-derived headers (including a header that may reveal the agent's install path). Before installing or using: (1) avoid uploading sensitive or confidential material; (2) prefer using an anonymous token rather than your personal NEMO_TOKEN, or create a limited token you can revoke; (3) be aware exports run on the provider's cloud and may consume credits; and (4) consider verifying the service's privacy/terms (no homepage is provided) if you care about data retention. Overall the skill appears internally consistent, but treat the external API and uploaded content with normal caution.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

🎬 Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk97dvxwkeaxy3rq7a0tp8c43d184zjff

70downloads

0stars

1versions

Updated 1w ago

v1.0.0

MIT-0

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 my script into a video"

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.

Free Video Generator from Script — Turn Scripts into Shareable Videos

Drop your written script in the chat and tell me what you need. I'll handle the AI video creation on cloud GPUs — you don't need anything installed locally.

Here's a typical use: you send a a 200-word product launch script, ask for turn my script into a video with voiceover and matching visuals, and about 1-2 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — shorter scripts under 150 words render faster and keep viewers engaged.

Matching Input to Actions

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

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.

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

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

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 "turn my script into a video with voiceover and matching visuals" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across platforms and devices.

Common Workflows

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

Comments

Loading comments...