Free Generator Text

Skip the learning curve of professional editing software. Describe what you want — generate a 30-second video from this product description text — and get te...

Security Scan

The skill's requirements and runtime instructions line up with a text→video cloud service: it asks only for a service token, calls the nemovideo.ai API endpoints, and has no install step — but there are minor metadata inconsistencies and some persistence details you should review before installing.

Purpose & Capability

The skill advertises AI text-to-video generation and its SKILL.md documents API endpoints, auth flow, upload, export, and state endpoints on mega-api-prod.nemovideo.ai. Requesting a NEMO_TOKEN credential is consistent with that purpose.

Instruction Scope

The instructions direct the agent to call the service's auth/session/upload/export endpoints and to read/write a session_id. That is within the stated scope. They also instruct the agent to auto-request an anonymous token if NEMO_TOKEN is absent and to avoid showing raw tokens to users — this implies network calls and some local state handling; the instructions do not ask for unrelated files or credentials.

Install Mechanism

No install spec or code files are present (instruction-only). That is lowest-risk in terms of write-to-disk installs.

Credentials

Only a single credential (NEMO_TOKEN) is required and it matches the declared primaryEnv. That is proportionate for a cloud service. Note: the SKILL.md frontmatter includes a config path (~/.config/nemovideo/) even though the registry summary lists no required config paths — a minor metadata inconsistency.

Persistence & Privilege

always:false and normal autonomous invocation. The skill instructs storing a session_id and using a token; it references a config directory in the frontmatter, which implies the agent may write tokens/sessions to disk. This is expected for a client that persists session state but is worth reviewing if you do not want persistent credentials stored locally.

Assessment

This skill appears to be what it claims: an instruction-only client for a nemovideo.ai text-to-video service that needs a NEMO_TOKEN and will call the service's API. Before installing, consider: (1) the skill will make network calls to https://mega-api-prod.nemovideo.ai and will obtain an anonymous token on your behalf if NEMO_TOKEN is not set; (2) it may persist session/token data in ~/.config/nemovideo/ (frontmatter mentions this) — check where and how tokens are stored and whether you’re comfortable with that; (3) the skill accepts uploads (potentially large files up to 500MB) so review privacy of uploaded content; (4) there is a minor metadata mismatch: the registry lists no required config paths while the SKILL.md frontmatter does. If you need higher assurance, request the vendor/source code or a privacy/storage statement, or only use an explicit, short-lived token you control rather than allowing the skill to acquire and persist anonymous tokens automatically.

Getting Started

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

Try saying:

• "generate my text prompts"
• "export 1080p MP4"
• "generate a 30-second video from this"

First-Time Connection

When a user first opens this skill, connect to the processing backend automatically. Briefly let them know (e.g. "Setting up...").

Authentication: Check if NEMO_TOKEN is set in the environment. If it is, skip to step 2.

1. Obtain a free token: Generate a random UUID as client identifier. POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with header X-Client-Id set to that UUID. The response data.token is your NEMO_TOKEN — 100 free credits, valid 7 days.
2. Create a session: POST to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Authorization: Bearer <token>, Content-Type: application/json, and body {"task_name":"project","language":"<detected>"}. Store the returned session_id for all subsequent requests.

Keep setup communication brief. Don't display raw API responses or token values to the user.

Free Text Generator — Generate Videos From Text

This tool takes your text prompts and runs AI text-to-video generation through a cloud rendering pipeline. You upload, describe what you want, and download the result.

Say you have a short paragraph describing a product launch scene and want to generate a 30-second video from this product description text — the backend processes it in about 30-60 seconds and hands you a 1080p MP4.

Tip: shorter, more specific text prompts produce more accurate video results.

Matching Input to Actions

User prompts referencing free generator text, 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-generator-text, 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).

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

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)

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

Tips and Tricks

The backend processes faster when you're specific. Instead of "make it look better", try "generate a 30-second video from this product description text" — concrete instructions get better results.

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

Export as MP4 for widest compatibility.

Common Workflows

Quick edit: Upload → "generate a 30-second video from this product description text" → Download MP4. Takes 30-60 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.