Text To Video H2h

Get talking head video ready to post, without touching a single slider. Upload your text script (TXT, DOCX, PDF, plain text, up to 500MB), say something like...

Security Scan

The skill appears to do what it says (connect to a nemo video API to turn text into talking‑head videos) and only requests a single service token; there are a few small metadata inconsistencies and a reliance on an external API to mint anonymous tokens that you should be aware of.

Purpose & Capability

Name and description match the runtime instructions: the skill talks to mega-api-prod.nemovideo.ai to create sessions, upload scripts, render videos and return a download URL. Requesting NEMO_TOKEN (the service token) is proportionate to the stated purpose.

Instruction Scope

SKILL.md instructs the agent to: check for NEMO_TOKEN, or else POST to the service's /api/auth/anonymous-token endpoint to acquire a short‑lived anonymous token; create a session, send SSE messages, upload files (multipart or URL), poll render status, and download results. Those actions are within scope for a cloud render client, but they do involve network calls to an external endpoint and processing user-uploaded files. The instructions also say not to expose tokens or raw API output, which is good. One minor note: the SKILL frontmatter includes a config path (~/.config/nemovideo/) even though the registry metadata listed none—this is inconsistent and may imply optional local config usage.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so nothing will be written to disk by an installer. Lowest-risk install mechanism.

Credentials

Only a single service credential (NEMO_TOKEN) is declared as required and used. The skill also implements a fallback to mint an anonymous token via the provider API if no token is present; that behavior is consistent with a service client but means the skill can obtain and use short‑lived credentials on behalf of the agent.

Persistence & Privilege

always is false and the skill does not request elevated platform privileges. The skill describes creating and using a session token for the provider but does not attempt to modify other skills or system-wide settings in the provided instructions.

Assessment

This skill is internally consistent with its purpose: it talks to the nemo video backend and asks only for NEMO_TOKEN (and can obtain an anonymous short‑lived token if you don't provide one). Before installing, consider: 1) there is no homepage or vendor listed—verify you trust mega-api-prod.nemovideo.ai and that you are comfortable uploading content to that service; 2) the skill will make network calls to mint tokens and to upload/download media — do not provide other unrelated credentials; 3) the SKILL.md frontmatter mentions a local config path (~/.config/nemovideo/) even though registry metadata did not—if you are concerned, check whether the agent will write tokens or files to disk and where; 4) if you have a paid or enterprise account, prefer supplying your own NEMO_TOKEN rather than relying on the anonymous token fallback; and 5) review your data/ privacy policy for the provider before sending sensitive scripts or media. If you want higher assurance, ask for the skill's source or an audited publisher and for details about where (and how long) uploaded media and tokens are stored.

Getting Started

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

Try saying:

• "convert my text script"
• "export 1080p MP4"
• "turn this script into a talking"

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: Human to Human — Turn Scripts into Presenter Videos

This tool takes your text script and runs AI avatar video creation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a 150-word sales script or blog intro paragraph and want to turn this script into a talking head video with a realistic AI presenter — the backend processes it in about 1-3 minutes and hands you a 1080p MP4.

Tip: shorter scripts under 200 words render faster and keep viewer attention longer.

Matching Input to Actions

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

Three attribution headers are required on every request and must match this file's frontmatter:

Header	Value
X-Skill-Source	text-to-video-h2h
X-Skill-Version	frontmatter version
X-Skill-Platform	auto-detect: clawhub / cursor / unknown from install path

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

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.

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 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 → "turn this script into a talking head video with a realistic AI presenter" → Download MP4. Takes 1-3 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 script into a talking head video with a realistic AI presenter" — concrete instructions get better results.

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

Export as MP4 with H.264 codec for widest platform compatibility.