Free Text To Video Creator

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...

Security Scan

The skill's behavior mostly matches a text→video converter, but there are inconsistencies and a few operational choices that warrant caution (missing publisher info, a discrepant config-path claim, and instructions that hide technical activity and automatically mint/use tokens).

Purpose & Capability

Name/description (text→video) aligns with API endpoints and flows described in SKILL.md. The only mismatch: the registry metadata listed no required config paths, but the skill frontmatter declares a config path (~/.config/nemovideo/). That discrepancy should be clarified.

Instruction Scope

Instructions instruct the agent to obtain/use NEMO_TOKEN (or mint an anonymous token via a POST to https://mega-api-prod.nemovideo.ai), to include attribution headers, and to keep technical details out of chat. The 'hide technical details' guidance is notable: it encourages not revealing backend activity to users. The instructions also require adding an X-Skill-Source header with the skill name (fine functionally but reveals usage) and auto-detecting 'install path' for X-Skill-Platform (unclear how the agent will determine that). No instructions ask the agent to read unrelated system files, but the declared config path suggests reading/writing to ~/.config/nemovideo/ which is not explained elsewhere.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest install risk; all actions occur via network calls to the described API endpoints.

Credentials

The only declared credential is NEMO_TOKEN (primaryEnv), which is appropriate for a third‑party video API. However, SKILL.md also references a local config path (~/.config/nemovideo/) in its frontmatter while the registry reported none — this mismatch could mean the skill expects to read/write local config files, which should be justified. The token-creation flow (anonymous-token endpoint) is plausible, but confirm whether tokens get persisted locally.

Persistence & Privilege

always is false and the skill does not request elevated platform privileges. Autonomous invocation is allowed (platform default) but not combined with 'always:true' or broad credential access, so no additional privilege concerns detected.

What to consider before installing

Before installing or using: (1) Verify the publisher or a homepage — this skill has no identified source. (2) Confirm the config-path behavior — SKILL.md frontmatter references ~/.config/nemovideo/ but registry metadata does not; ask whether the skill will read/write that directory and what it stores. (3) Treat NEMO_TOKEN like access credentials: if you provide a personal token it may allow account actions and billable renders; prefer using an anonymous/test token and do not supply production credentials until you trust the provider. (4) Be aware the skill will upload content to https://mega-api-prod.nemovideo.ai (including files you send) — do not upload sensitive or private data until you confirm retention and privacy policies. (5) The skill instructs the agent to hide technical backend activity from the user — ask for transparency about what network calls will be made and whether tokens are persisted. (6) If you proceed, test with non-sensitive sample content and request explicit details about token storage, data retention, and the purpose of the ~/.config/nemovideo/ path. If the publisher/host can’t be identified or these questions aren’t answered, avoid giving real credentials or private data.

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 150-word product description into a 1080p MP4"
• "turn this blog intro into a 30-second video with visuals and background music"
• "generating videos from written content without filming anything for content creators, marketers, bloggers"

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 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":"<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.

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 <NEMO_TOKEN> 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:

• "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

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 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

Tips 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.