Text To Video Creator Free

convert text prompts into ready-to-share videos with this skill. Works with TXT, DOCX, PDF, copied text files up to 500MB. content creators use it for genera...

Security Scan

The skill's declared token requirement and API calls match a text→video service, but metadata and runtime instructions contain inconsistent/unclear requests to read local config/install paths that could expose local secrets — ask for clarification before installing or providing credentials.

Purpose & Capability

The skill's name and description (text→video) align with the runtime actions: it calls a nemo-video backend, creates sessions, uploads files, and renders MP4s. Requesting a NEMO_TOKEN as the primary credential is coherent. However, the YAML frontmatter inside SKILL.md declares a config path (~/.config/nemovideo/) and install-path detection that is not reflected in the registry metadata (registry reported no required config paths). This mismatch is unexplained and worth asking about.

Instruction Scope

Most instructions are scoped to the nemo video API endpoints (session creation, SSE, upload, render, credits). Accepts local file uploads (multipart @/path) which is expected for a video tool. Concerning parts: it instructs the agent to read the skill's YAML frontmatter at runtime and to detect an install path (checking ~/.clawhub/ or ~/.cursor/skills/), and SKILL.md metadata mentions reading ~/.config/nemovideo/. Those operations involve inspecting local filesystem paths and could surface other local config or tokens if implemented broadly.

Install Mechanism

No install spec or code files are present (instruction-only). This minimizes direct code installation or arbitrary third-party downloads.

Credentials

The only declared required env var is NEMO_TOKEN, which is appropriate. But SKILL.md's frontmatter also lists a config path (~/.config/nemovideo/) in its 'requires' metadata, while the registry lists no required config paths — an inconsistency. If the runtime implementation actually reads that config directory, it could access other tokens or local config unexpectedly. The anonymous-token fallback flow is documented (POST to the API) which is reasonable, but granting any long-lived token should be done cautiously.

Persistence & Privilege

The skill does not request always:true and does not declare persistence or system-wide modification. It appears to operate per-session against a cloud API; autonomous invocation is allowed (platform default) but not otherwise privileged.

What to consider before installing

This skill mostly behaves like a front-end for nemo-video cloud APIs and asking for NEMO_TOKEN is expected. Before installing or using it, verify the following: (1) Confirm why SKILL.md metadata lists ~/.config/nemovideo/ and install-path detection — ask the author whether the skill will read local config directories and what it will look for. (2) Do not provide sensitive or long-lived credentials unless you trust the source; if possible use an ephemeral/anonymous token or a limited-scope token. (3) Avoid uploading local files you don't want sent to a third-party cloud. (4) Because the package has no homepage or published source, request the source code or a privacy/security policy from the publisher; lack of a trusted origin raises risk. If the author confirms the config-path entry is unused or limited to reading only the skill's own frontmatter, the skill is more coherent; if it reads arbitrary ~/.config/* files, treat it as unsafe.

Getting Started

Send me your text prompts and I'll handle the AI video creation. Or just describe what you're after.

Try saying:

• "convert a 100-word product description into a 1080p MP4"
• "turn this blog paragraph into a 30-second video with visuals and music"
• "generating videos from written content without recording footage for 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.

Text to Video Creator Free — Convert Text into Shareable Videos

Drop your text prompts 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 100-word product description, ask for turn this blog paragraph into a 30-second video with visuals and music, 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, clearer text produces more accurate visuals.

Matching Input to Actions

User prompts referencing text to video creator free, 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.

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

Skill attribution — read from this file's YAML frontmatter at runtime:

• X-Skill-Source: text-to-video-creator-free
• X-Skill-Version: from frontmatter version
• X-Skill-Platform: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

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.

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

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.

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)

Common Workflows

Quick edit: Upload → "turn this blog paragraph into a 30-second video with visuals and 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn this blog paragraph into a 30-second video with visuals and music" — 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 platforms.