Text To Free

v1.0.0

convert text prompt into generated video clips with this skill. Works with TXT, DOCX, PDF, plain text files up to 200MB. content creators use it for generati...

⭐ 0· 91·0 current·0 all-time

by@vynbosserman65

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for vynbosserman65/text-to-free.

Previewing Install & Setup.

Prompt PreviewInstall & Setup

Install the skill "Text To Free" (vynbosserman65/text-to-free) from ClawHub.
Skill page: https://clawhub.ai/vynbosserman65/text-to-free
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: NEMO_TOKEN
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install text-to-free

ClawHub CLI

Package manager switcher

npx clawhub@latest install text-to-free

Security Scan

VirusTotal

Benign

View report →

OpenClaw

Benign

medium confidence

✓

Purpose & Capability

The skill claims to convert text to video and requires a single credential (NEMO_TOKEN) and an optional config path under ~/.config/nemovideo/ — these align with a cloud backend video service. No unrelated env vars or binaries are requested.

ℹ

Instruction Scope

SKILL.md explicitly instructs the agent to check for NEMO_TOKEN, or obtain an anonymous token by POSTing to the service's anonymous-token endpoint, create sessions, stream SSE, upload files, and poll render status. It does not direct reading arbitrary local files or unrelated credentials, but it will upload user-provided media/text to the external API and manage tokens/sessions. Minor inconsistency: metadata lists a config path and install-path-based header logic even though this is an instruction-only skill with no install steps; this is unexpected but not critical.

✓

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is written to disk by the skill itself. Network interaction is the primary runtime behavior.

ℹ

Credentials

Only NEMO_TOKEN is declared as required and is the primary credential; the skill also describes generating anonymous tokens via the public API if no token is present. This is proportionate to a cloud video service, but be aware that obtaining/using tokens will enable the remote service to process uploaded files and prompts.

✓

Persistence & Privilege

The skill is not always-enabled and does not request elevated platform privileges. It creates short-lived sessions and tokens for the service and can orphan backend render jobs if a session is closed — this is normal for cloud render services but worth noting.

Assessment

Before installing, consider: (1) This skill uploads prompts and any files you provide to an external service (mega-api-prod.nemovideo.ai). Don't send sensitive/private data unless you trust that service. (2) The skill will look for or create a NEMO_TOKEN (it can auto-generate an anonymous token with limited credits); only provide a long-lived token if you trust the provider. (3) There is no homepage or provenance information—verify who runs this API and read their privacy/terms if possible. (4) Render jobs run on cloud GPUs and may continue or be orphaned if you close the session; check expected billing/credit behavior. (5) Because this is instruction-only (no local code), the main risk is network-based data exposure — prefer a sandboxed environment or a disposable token if you want to test it. If you need higher assurance, ask the publisher for a homepage, privacy policy, and service documentation before use.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

📝 Clawdis

EnvNEMO_TOKEN

Primary envNEMO_TOKEN

latestvk9717jdt3fwr0f0tsrfc2944v984mcfp

91downloads

0stars

1versions

Updated 2w ago

v1.0.0

MIT-0

Getting Started

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

Try saying:

"convert my text prompt"
"export 1080p MP4"
"generate a 30-second video from this"

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 Free Video — Generate Videos from Text

This tool takes your text prompt and runs AI 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 text description about a sunrise over a city — the backend processes it in about 1-2 minutes and hands you a 1080p MP4.

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

Matching Input to Actions

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

Base URL: https://mega-api-prod.nemovideo.ai

Endpoint	Method	Purpose
`/api/tasks/me/with-session/nemo_agent`	POST	Start a new editing session. Body: `{"task_name":"project","language":"<lang>"}`. Returns `session_id`.
`/run_sse`	POST	Send a user message. Body includes `app_name`, `session_id`, `new_message`. Stream response with `Accept: text/event-stream`. Timeout: 15 min.
`/api/upload-video/nemo_agent/me/<sid>`	POST	Upload a file (multipart) or URL.
`/api/credits/balance/simple`	GET	Check remaining credits (`available`, `frozen`, `total`).
`/api/state/nemo_agent/me/<sid>/latest`	GET	Fetch current timeline state (`draft`, `video_infos`, `generated_media`).
`/api/render/proxy/lambda`	POST	Start export. Body: `{"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}`. Poll status every 30s.

Accepted file types: 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 text-to-free, 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.

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

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)

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 text description about a sunrise over a city" — concrete instructions get better results.

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

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

Common Workflows

Quick edit: Upload → "generate a 30-second video from this text description about a sunrise over a city" → 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.

Comments

Loading comments...