Text To Video Image

Turn a written description of a sunset over a mountain lake into 1080p AI-generated video just by typing what you need. Whether it's generating short video c...

Security Scan

The skill mostly matches a text→video service (it needs a NEMO_TOKEN and calls nemovideo.ai APIs), but a few unexplained or disproportionate behaviors and the unknown source reduce trustworthiness.

Purpose & Capability

Name/description (text→video) align with the declared NEMO_TOKEN and the API endpoints in SKILL.md. However metadata also lists a config path (~/.config/nemovideo/) and the runtime asks to detect install paths to set X-Skill-Platform; detecting local install paths for attribution is not required for core video generation and is an extra capability that should be justified.

Instruction Scope

The instructions will: check an env var (NEMO_TOKEN), if missing call an anonymous-token API to obtain a token, create sessions, upload user files (multipart) to the remote service, stream SSE responses, and poll render endpoints. These actions are expected for a cloud render skill. Concerns: (1) the skill may read/inspect local install paths to set X-Skill-Platform, which requires filesystem checks outside the stated core task; (2) user files are uploaded to a third-party backend — this is expected but carries privacy/exfiltration risk; (3) the SKILL.md tells the agent not to expose tokens, but there is no technical enforcement — the agent could still leak tokens or API responses if misused.

Install Mechanism

Instruction-only skill with no install spec and no bundled code — lowest install risk. All network activity comes from runtime API calls described in SKILL.md.

Credentials

Only one required env var (NEMO_TOKEN) is declared, which is appropriate. The skill also declares a config path (~/.config/nemovideo/) in metadata and expects to detect install paths — those imply the skill may read local filesystem state beyond a single token env var. The fallback behavior (automatically requesting an anonymous token from nemovideo.ai when NEMO_TOKEN is absent) is reasonable but means the agent will make outbound network calls autonomously.

Persistence & Privilege

always is false and there are no install scripts or instructions to modify other skills or global agent settings. The skill can invoke autonomously (default), which increases blast radius but is normal for skills; combined with network/file access noted above this raises operational privacy considerations but not an outright privilege escalation.

What to consider before installing

This skill appears to be a straightforward cloud text→video client, but exercise caution: it uploads files and uses a bearer token (NEMO_TOKEN) to a third-party domain (mega-api-prod.nemovideo.ai). The SKILL.md will generate an anonymous token if you don't provide one, and it may check local install/config paths to build attribution headers. Before installing, consider: (1) there is no homepage or known source — that reduces traceability and accountability; (2) do not upload sensitive or private media until you’ve verified the service's privacy policy; (3) prefer providing a dedicated, limited-scope token (or none) and rotate it if compromised; (4) test the skill with non-sensitive content first; (5) if you need to be extra cautious, request the skill author/source or prefer a vetted provider.

Getting Started

Share your text prompts and I'll get started on AI video generation. Or just tell me what you're thinking.

Try saying:

• "generate my text prompts"
• "export 1080p MP4"
• "create a 15-second video clip from"

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 Image — Generate Videos from Text Prompts

Send me your text prompts and describe the result you want. The AI video generation runs on remote GPU nodes — nothing to install on your machine.

A quick example: upload a written description of a sunset over a mountain lake, type "create a 15-second video clip from the text: 'a drone flying over a neon-lit city at night'", and you'll get a 1080p MP4 back in roughly 30-90 seconds. All rendering happens server-side.

Worth noting: shorter, more specific prompts produce more accurate and consistent video output.

Matching Input to Actions

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

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

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.

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.

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

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

Common Workflows

Quick edit: Upload → "create a 15-second video clip from the text: 'a drone flying over a neon-lit city at night'" → Download MP4. Takes 30-90 seconds 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 "create a 15-second video clip from the text: 'a drone flying over a neon-lit city at night'" — concrete instructions get better results.

Max file size is 500MB. Stick to TXT, DOCX, PDF, direct input for the smoothest experience.

Export as MP4 for widest compatibility across social platforms and editors.