Text To Video No Limit

Get ready-to-share videos ready to post, without touching a single slider. Upload your text prompts (TXT, DOCX, PDF, SRT, up to 500MB), say something like "t...

Security Scan

The skill's requests and runtime instructions are consistent with a cloud text→video service: it needs a single NEMO_TOKEN and describes API calls to nemovideo.ai; nothing obviously unrelated is requested, but it will send user files and prompts to an external API and automatically create anonymous tokens if none are provided.

Purpose & Capability

Name/description (text→video) aligns with the declared requirement for a NEMO_TOKEN and with the SKILL.md, which solely documents an HTTP API to a video-rendering backend. No unrelated cloud providers or unrelated credentials are requested.

Instruction Scope

The SKILL.md instructs the agent to (a) use an existing NEMO_TOKEN or obtain an anonymous token by POSTing to an external API, (b) create sessions, upload user-provided files, stream SSE, and poll render status. Those actions are expected for a cloud renderer, but they do mean uploaded files, prompts, and any session state are transmitted to https://mega-api-prod.nemovideo.ai automatically. The skill also instructs automatic setup on first interaction (connect before doing anything else), so it will contact the external API autonomously unless prevented.

Install Mechanism

Instruction-only skill with no install spec and no code files — lowest-risk install model. Nothing is downloaded or written by an installer.

Credentials

Only NEMO_TOKEN is required (declared primaryEnv), which is appropriate for this service. The metadata also lists a config path (~/.config/nemovideo/) which is plausible for client config but is not referenced in the SKILL.md steps; this is a small inconsistency to be aware of (it suggests the skill may expect or read a local config in some environments).

Persistence & Privilege

always is false and the skill does not request elevated platform privileges. It will store session_id and tokens for its own operation (normal behavior), and it can be invoked autonomously by the agent (platform default).

Scan Findings in Context

[no-findings] expected: The static regex scanner found nothing because this is an instruction-only skill with no code files to analyze. This is expected but means runtime behavior is governed entirely by the SKILL.md instructions.

Assessment

This skill appears to do what it says: it will send your uploaded text/files and prompts to mega-api-prod.nemovideo.ai, create a session, and return a rendered video URL. Before installing, consider: (1) the service source has no homepage provided and the registry owner is unknown — if you care about privacy or provenance, verify the vendor or avoid uploading sensitive content; (2) the skill will auto-generate anonymous tokens if you haven't set NEMO_TOKEN, so it can begin contacting the external API on first use — disable or restrict the skill if you prefer manual approval; (3) metadata mentions a local config path (~/.config/nemovideo/) even though the instructions rely on an env var — expect the skill may look for local config in some setups; (4) only supply NEMO_TOKEN if you trust the service, otherwise rely on anonymous tokens but know they grant the service temporary credits and access to your uploads. If you need greater assurance, ask the publisher for a homepage, privacy policy, and more info on how uploaded content is stored/retained.

Getting Started

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

Try saying:

• "generate my text prompts"
• "export 1080p MP4"
• "turn this script into a 60-second"

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.

Text to Video No Limit — Generate Videos from Any Text

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 200-word product description, ask for turn this script into a 60-second video with visuals and background music, and about 1-3 minutes later you've got a MP4 file ready to download. The whole thing runs at 1080p by default.

One thing worth knowing — breaking long scripts into scenes gives the AI clearer structure and better visual results.

Matching Input to Actions

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

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

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

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

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.

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

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.

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)

Common Workflows

Quick edit: Upload → "turn this script into a 60-second video with visuals and background music" → 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 60-second video with visuals and background music" — concrete instructions get better results.

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

Export as MP4 for widest compatibility across social platforms and video hosts.