Text To Video Hd Free

Skip the learning curve of professional editing software. Describe what you want — turn this text into a 30-second HD explainer video with visuals and backgr...

Security Scan

The skill's declared purpose (convert text to HD video) matches the network calls and token usage, but there are inconsistencies in metadata and a few runtime behaviors (auto-creating/storing tokens, probing install paths, and uploading arbitrary local files) that merit caution before installing.

Purpose & Capability

The skill claims to convert text into HD videos and the SKILL.md describes API endpoints, session creation, uploads, credits, and export flows that align with that purpose. Requesting NEMO_TOKEN as the primary credential is reasonable. However, the SKILL.md frontmatter declares a config path (~/.config/nemovideo/) while the registry metadata lists no required config paths — this registry vs. runtime metadata mismatch is inconsistent and should be clarified.

Instruction Scope

Most runtime instructions stay within the video-generation domain (create session, upload file, stream SSE, poll render). Potentially sensitive actions are described: auto-generating an anonymous token by POSTing to the external API if NEMO_TOKEN is absent, saving and reusing session_id and possibly storing tokens in ~/.config/nemovideo/, and detecting install path to set X-Skill-Platform (which implies reading local filesystem paths). Those are plausible for operation but extend the skill's scope beyond purely stateless API calls and mean the agent will access local filesystem and persist tokens.

Install Mechanism

This is instruction-only (no install spec, no code files). That is lower risk from a code-install perspective: nothing is downloaded or written by an installer script in the skill bundle itself. The runtime behavior still causes network calls and may write tokens to disk per the instructions.

Credentials

Only NEMO_TOKEN is declared as required, which fits the described API usage. However, the SKILL.md instructs the agent to create an anonymous token if NEMO_TOKEN is missing and to persist session/token state (metadata indicates ~/.config/nemovideo/). The registry metadata earlier said 'Required config paths: none' whereas the skill frontmatter requests a config path. That inconsistency (the skill planning to read/write a config directory without it being declared in registry metadata) is a proportionality/visibility concern: users should be aware where credentials may be stored.

Persistence & Privilege

always:false (no forced presence) and default autonomous invocation are normal. The skill will create sessions and tokens and may persist them to a config path, but it does not request escalated system privileges or claim to modify other skills. Autonomous network access combined with token persistence increases blast radius if misused, so consider that when enabling autonomous invocation.

What to consider before installing

This skill appears to do what it says (call a NemoVideo API to render videos) but there are a few things to check before installing: 1) Confirm the external API domain (mega-api-prod.nemovideo.ai) is trustworthy for your use and that you’re comfortable sending text and files there. 2) Be aware the skill will look for NEMO_TOKEN and, if missing, will create an anonymous token by POSTing to the service and may store tokens/session state under ~/.config/nemovideo/ — verify and control that storage location. 3) The skill may read install paths to set X-Skill-Platform and will upload local files you provide; avoid sending sensitive documents or secrets. 4) The registry metadata and the in-file metadata disagree about required config paths — ask the publisher to clarify where data/tokens are stored and to provide a privacy/retention statement. If you need higher assurance, request source code or an official integration reference from the service before granting the skill network or filesystem access.

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 paragraph into a 1080p MP4"
• "turn this text into a 30-second HD explainer video with visuals and background music"
• "converting written content into shareable HD videos for content creators, marketers, students"

Quick Start Setup

This skill connects to a cloud processing backend. On first use, set up the connection automatically and let the user know ("Connecting...").

Token check: Look for NEMO_TOKEN in the environment. If found, skip to session creation. Otherwise:

• Generate a UUID as client identifier
• POST https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with X-Client-Id header
• Extract data.token from the response — this is your NEMO_TOKEN (100 free credits, 7-day expiry)

Session: POST https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Keep the returned session_id for all operations.

Let the user know with a brief "Ready!" when setup is complete. Don't expose tokens or raw API output.

Text to Video HD Free — Convert Text into HD 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 150-word product description paragraph, ask for turn this text into a 30-second HD explainer video with visuals and background 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 prompts produce more accurate and visually consistent video output.

Matching Input to Actions

User prompts referencing text to video hd 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.

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

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

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 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 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

Common Workflows

Quick edit: Upload → "turn this text into a 30-second HD explainer 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.

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "turn this text into a 30-second HD explainer video with visuals and background 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 YouTube, social media, and presentations.