← Back to Skills Marketplace
51
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install text-to-video-examples
Description
Turn a 3-sentence product description into 1080p generated video clips just by typing what you need. Whether it's generating videos from written scripts or p...
Usage Guidance
This skill plausibly implements a text→video API and only asks for a single service token, but exercise caution because: (1) the source and homepage are missing — you can't easily verify the provider; (2) the SKILL.md and registry metadata disagree about config paths (registry says none; the skill references ~/.config/nemovideo/), which is unexplained; (3) the runtime instructions allow uploading arbitrary files and instruct probing install paths, which could expose sensitive data if the agent is granted broad filesystem access. Before installing: verify the skill's provenance (official docs or vendor), confirm what NEMO_TOKEN can do and how long it lasts, avoid uploading sensitive files, prefer using an ephemeral or least-privilege token (revoke when done), and ask the skill author to explain the configPath discrepancy and precisely how/where tokens/sessions are stored.
Capability Analysis
Type: OpenClaw Skill
Name: text-to-video-examples
Version: 1.0.0
The skill is a legitimate integration for a text-to-video service hosted at nemovideo.ai. It defines standard API workflows for authentication, session management, file uploads, and video rendering. While it includes logic to detect the host platform (e.g., Cursor or OpenClaw) for attribution headers and manages a NEMO_TOKEN environment variable, these actions are transparently documented in SKILL.md and align with the stated purpose of the tool. No evidence of data exfiltration, malicious execution, or harmful prompt injection was found.
Capability Assessment
Purpose & Capability
Name/description match the runtime instructions: the SKILL.md describes a remote video-rendering API and the skill requests a single service token (NEMO_TOKEN). However the package has no homepage, unknown source/owner, and the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata claimed no required config paths — this mismatch is unexplained.
Instruction Scope
The instructions direct the agent to call external API endpoints (session creation, SSE streaming, uploads, rendering) and to upload files via multipart (files=@/path). Upload operations necessarily require reading file paths the user supplies; that is expected for a video upload feature, but it also creates an exfiltration vector if the agent is allowed to read arbitrary files. The skill also instructs detecting install paths (~/.clawhub/, ~/.cursor/skills/) and reading this file's YAML frontmatter for attribution headers, which implies filesystem probing beyond the service's API. These behaviors are within a video service's plausible needs, but they increase risk and should be justified/limited.
Install Mechanism
This is an instruction-only skill with no install spec and no code files — nothing will be downloaded or written by an installer. That is lower risk compared to skills that fetch and extract remote archives.
Credentials
Only one env var is declared (NEMO_TOKEN), which is appropriate for a hosted video API. However, the SKILL.md describes generating an anonymous token via an API and treating the returned token as NEMO_TOKEN (100 credits, 7-day expiry), and the frontmatter references a config path (~/.config/nemovideo/) that the registry did not declare. The discrepancy between declared config paths and the SKILL.md metadata is a red flag. Also, because the skill accepts uploads, the token grants the service ability to act on uploaded data — ensure you understand what that token permits and how long it remains valid.
Persistence & Privilege
The skill is not always-included and uses normal autonomous invocation defaults. It will create and use session IDs and tokens for the remote API, which is expected. There is no claim it will modify other skills or system-wide settings. Monitor where it persists the anonymous token/session if it does so.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install text-to-video-examples - After installation, invoke the skill by name or use
/text-to-video-examples - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of "Text to Video Examples" skill — quickly convert short product descriptions or text prompts into AI-generated 1080p video clips.
- Simple workflow: upload text, specify video requirements, receive downloadable MP4 in 1–2 minutes.
- Automatic setup connects to the video processing API and handles session management.
- Supports quick edits, batch processing, and iterative refinement; tracks timeline state for smooth user experience.
- Handles user prompts for export, credits, status, and uploads via intent-based routing.
- Comprehensive error handling and helpful feedback for format support, token issues, and export permissions.
Metadata
Frequently Asked Questions
What is Text To Video Examples?
Turn a 3-sentence product description into 1080p generated video clips just by typing what you need. Whether it's generating videos from written scripts or p... It is an AI Agent Skill for Claude Code / OpenClaw, with 51 downloads so far.
How do I install Text To Video Examples?
Run "/install text-to-video-examples" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Text To Video Examples free?
Yes, Text To Video Examples is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Text To Video Examples support?
Text To Video Examples is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Text To Video Examples?
It is built and maintained by tk8544-b (@tk8544-b); the current version is v1.0.0.
More Skills