Free Text To Video Creator
by @vcarolxhberger
convert text prompts into ready-to-share videos with this skill. Works with TXT, DOCX, PDF, plain text files up to 500MB. content creators, marketers, blogge...
clawhub install free-text-to-video-creatorπ About This Skill
name: free-text-to-video-creator version: "1.0.0" displayName: "Free Text to Video Creator β Convert Text Into Shareable Videos" description: > convert text prompts into ready-to-share videos with this skill. Works with TXT, DOCX, PDF, plain text files up to 500MB. content creators, marketers, bloggers use it for generating videos from written content without filming anything β processing takes 1-2 minutes on cloud GPUs and you get 1080p MP4 files. metadata: {"openclaw": {"emoji": "π¬", "requires": {"env": ["NEMO_TOKEN"], "configPaths": ["~/.config/nemovideo/"]}, "primaryEnv": "NEMO_TOKEN", "variant": "greeting_v2"}}
Getting Started
> Send me your text prompts and I'll handle the AI video creation. Or just describe what you're after.
Try saying:
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:
https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id headertoken with 100 free credits valid for 7 days β use it as NEMO_TOKENThen 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 Text to Video Creator β Convert Text Into Shareable Videos
This tool takes your text prompts and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.
Say you have a 150-word product description and want to turn this blog intro into a 30-second video with visuals and background music β the backend processes it in about 1-2 minutes and hands you a 1080p MP4.
Tip: shorter, clearer text produces more accurate visuals β aim for 100 words or fewer per scene.
Matching Input to Actions
User prompts referencing free text to video creator, 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":". 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/ β 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/ β current draft and media info.
6. Export β POST /api/render/proxy/lambda with render ID and draft JSON. Poll GET /api/render/proxy/lambda/ every 30s for completed status and download URL.
Formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.
Three attribution headers are required on every request and must match this file's frontmatter:
| Header | Value |
|--------|-------|
| X-Skill-Source | free-text-to-video-creator |
| X-Skill-Version | frontmatter version |
| X-Skill-Platform | auto-detect: clawhub / cursor / unknown from install path |
Every API call needs Authorization: Bearer plus the three attribution headers above. If any header is missing, exports return 402.
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)
Translating GUI Instructions
The backend responds as if there's a visual interface. Map its instructions to API calls:
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.
Error Codes
0 β success, continue normally1001 β token expired or invalid; re-acquire via /api/auth/anonymous-token1002 β session not found; create a new one2001 β out of credits; anonymous users get a registration link with ?bind=, registered users top up4001 β unsupported file type; show accepted formats4002 β file too large; suggest compressing or trimming400 β missing X-Client-Id; generate one and retry402 β free plan export blocked; not a credit issue, subscription tier429 β rate limited; wait 30s and retry onceTips and Tricks
The backend processes faster when you're specific. Instead of "make it look better", try "turn this blog intro into a 30-second video with visuals and background music" β 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 social platforms and video hosts.
Common Workflows
Quick edit: Upload β "turn this blog intro into a 30-second video with visuals and background music" β 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.
π‘ Examples
> Send me your text prompts and I'll handle the AI video creation. Or just describe what you're after.
Try saying:
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:
https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id headertoken with 100 free credits valid for 7 days β use it as NEMO_TOKENThen 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 Text to Video Creator β Convert Text Into Shareable Videos
This tool takes your text prompts and runs AI video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.
Say you have a 150-word product description and want to turn this blog intro into a 30-second video with visuals and background music β the backend processes it in about 1-2 minutes and hands you a 1080p MP4.
Tip: shorter, clearer text produces more accurate visuals β aim for 100 words or fewer per scene.