← Back to Skills Marketplace
Text To Video Api
by
vcarolxhberger
· GitHub ↗
· v1.0.0
· MIT-0
82
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install text-to-video-api
Description
Turn a 200-word product description script into 1080p generated video files just by typing what you need. Whether it's generating videos programmatically fro...
Usage Guidance
This skill appears to be a straightforward wrapper for a third-party text→video API and requests a single API token (NEMO_TOKEN), which is reasonable. Before installing: 1) Verify the backend domain (mega-api-prod.nemovideo.ai) and the vendor's reputation — this skill will POST your scripts and media to that service. 2) Prefer using an anonymous/short-lived token (the skill supports generating one) rather than placing a long-lived secret in your environment. 3) Ask the author to clarify the config-path claim (~/.config/nemovideo/) and how X-Skill-Platform is auto-detected — confirm the skill will not read unrelated files or secrets. 4) Remember uploads may include sensitive content (product IP, audio), so check the vendor's retention and privacy policies. If you cannot verify the backend or resolve the metadata/configPath inconsistency, treat the skill cautiously.
Capability Analysis
Type: OpenClaw Skill
Name: text-to-video-api
Version: 1.0.0
The skill bundle provides a legitimate integration for an AI video generation service hosted at `mega-api-prod.nemovideo.ai`. The instructions in `SKILL.md` guide the agent through standard API interactions, including authentication (using `NEMO_TOKEN` or an anonymous fallback), session management, and file uploads. There are no indicators of data exfiltration, unauthorized command execution, or malicious prompt injection; the requested environment variables and file access (`~/.config/nemovideo/`) are strictly aligned with the tool's stated purpose.
Capability Assessment
Purpose & Capability
Name/description (convert text scripts to 1080p video) align with the endpoints and workflows described in SKILL.md: session creation, SSE messages, upload, render/export. Requesting a single API token (NEMO_TOKEN) is expected for a cloud video service.
Instruction Scope
Instructions are primarily network calls to the nemovideo API (expected). However the frontmatter asks for configPaths (~/.config/nemovideo/) and requires detection of an install path to set X-Skill-Platform; it's unclear whether the agent must read filesystem/install paths to auto-detect platform. The doc also instructs to 'Keep the technical details out of the chat,' which reduces transparency about what data (session IDs, request failures) might be hidden from the user. Nothing in the instructions directs the agent to read unrelated system secrets, but the platform-detection step is vague and could imply reading environment/install metadata.
Install Mechanism
No install spec and no code files — instruction-only skill. This is the lowest install risk (no packages downloaded or archives extracted).
Credentials
The skill declares a single primary credential (NEMO_TOKEN), which is appropriate for an API-based service. However there is an inconsistency: the registry metadata provided to you lists no required config paths, while the SKILL.md frontmatter includes ~/.config/nemovideo/ in metadata.requires.configPaths. That discrepancy should be resolved. Also, the skill recommends obtaining an anonymous token by POSTing to the vendor endpoint and then using that token as NEMO_TOKEN; consider using short-lived/anonymous tokens rather than uploading a long-lived secret, and verify what privileges that token grants and whether it will be stored.
Persistence & Privilege
always:false (no forced inclusion) and no install-time persistence are set. The skill can be invoked autonomously (default), which is normal for skills; this by itself is not a red flag. There is no indication the skill modifies other skills or system-wide settings.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install text-to-video-api - After installation, invoke the skill by name or use
/text-to-video-api - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
text-to-video-api v1.0.0
- Initial release: generate 1080p videos from 200-word text scripts via API or direct prompts.
- Supports uploading video, image, or audio files; batch and iterative video editing workflows included.
- Automatic token management: uses NEMO_TOKEN if present, otherwise fetches 7-day demo token.
- Streamlined export, timeline preview, credits checking, and cloud rendering with status updates in chat.
- Error handling for authentication, credits, rate limits, and file support; clear guidance for resolution.
- Supports plain text, docx, media uploads; exports MP4 by default, with visual and audio track customization.
Metadata
Frequently Asked Questions
What is Text To Video Api?
Turn a 200-word product description script into 1080p generated video files just by typing what you need. Whether it's generating videos programmatically fro... It is an AI Agent Skill for Claude Code / OpenClaw, with 82 downloads so far.
How do I install Text To Video Api?
Run "/install text-to-video-api" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Text To Video Api free?
Yes, Text To Video Api is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Text To Video Api support?
Text To Video Api is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Text To Video Api?
It is built and maintained by vcarolxhberger (@vcarolxhberger); the current version is v1.0.0.
More Skills