Free Text Into Video

Skip the learning curve of professional editing software. Describe what you want — turn this blog intro into a 30-second video with visuals and background mu...

Security Scan

The skill's functionality (text→video via nemo API) mostly matches the requested credential, but the SKILL.md references local config paths and install-path detection that are not declared in the registry metadata — an inconsistency worth clarifying before install.

Purpose & Capability

Name and description (convert text to short videos) align with the runtime instructions and required credential (NEMO_TOKEN). The endpoints, upload/export flows, and use of a single service credential are coherent. However, the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/) that the registry listing did not declare; this mismatch suggests the skill may expect to access a local config directory even though the registry metadata omitted it.

Instruction Scope

Instructions are explicit about obtaining/using a NEMO_TOKEN (use env var or request anonymous token via the API), creating sessions, uploading files, reading SSE streams, and polling exports — all consistent with a cloud render service. They also instruct deriving an attribution header X-Skill-Platform from the agent install path, which implies reading environment/paths to detect install location; that behavior is not clearly justified and widens the scope beyond simple API calls.

Install Mechanism

No install spec and no code files — instruction-only skill. This is the lowest install risk (nothing written to disk by an installer).

Credentials

Only one credential is requested (NEMO_TOKEN), which is proportionate for a cloud-rendering service. Minor concern: the SKILL.md metadata references a local config path (~/.config/nemovideo/) while the registry requirements did not; if the skill actually reads that path it would be additional access not declared up-front.

Persistence & Privilege

The skill is not 'always' included and uses normal autonomous invocation. It asks to save a session_id for job tracking (expected for long-running cloud jobs) but does not request system-wide configuration changes or other skills' credentials.

What to consider before installing

This skill appears to do what it says: it sends your text/files to a nemo-video cloud API and returns rendered videos, and it only needs a NEMO_TOKEN. Before installing, confirm two things: (1) whether the skill will read or write a local config directory (~/.config/nemovideo/) or otherwise access your install path — the SKILL.md mentions that but the registry omitted it, so ask the publisher to clarify; (2) verify the remote domain (mega-api-prod.nemovideo.ai), the privacy/retention of uploaded content, and how anonymous tokens/credits are handled. Avoid uploading sensitive private data until you confirm retention and access policies, and keep any NEMO_TOKEN secret. If you want stronger assurances, ask the skill author to explicitly declare required config paths and to document exactly what local paths the agent will read/write.

Getting Started

Got written text prompt to work with? Send it over and tell me what you need — I'll take care of the AI video creation.

Try saying:

• "convert a 150-word product description paragraph into a 1080p MP4"
• "turn this blog intro into a 30-second video with visuals and background music"
• "turning written content into short shareable videos for marketers, content creators, educators"

Automatic Setup

On first interaction, connect to the processing API before doing anything else. Show a brief status like "Setting things up...".

Token: If NEMO_TOKEN environment variable is already set, use it and skip to Session below.

Free token: Generate a UUID as client identifier, then POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id: <uuid>. The response field data.token becomes your NEMO_TOKEN (100 credits, 7-day expiry).

Session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer auth and body {"task_name":"project"}. Save session_id from the response.

Confirm to the user you're connected and ready. Don't print tokens or raw JSON.

Free Text Into Video — Convert Text to Video Clips

Drop your written text prompt 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 blog intro into a 30-second 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 produces more accurate scene generation.

Matching Input to Actions

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

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

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)

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"	Query session state
"drag/drop" / "拖拽"	Send edit via SSE
"preview in timeline"	Show track summary
"Export button" / "导出"	Execute 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

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.

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, copied text for the smoothest experience.

Export as MP4 for widest compatibility across social platforms.