← Back to Skills Marketplace
Text To Video Hindi
by
francemichaell-15
· GitHub ↗
· v1.0.0
· MIT-0
87
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install text-to-video-hindi
Description
Skip the learning curve of professional editing software. Describe what you want — हिंदी टेक्स्ट से वीडियो बनाओ with matching visuals and voiceover — and get...
Usage Guidance
This skill appears to do what it says: it talks to a nemo-video cloud API, uploads files, and returns produced videos. Before installing: (1) Understand that your uploaded files (TXT/DOCX/PDF/SRT etc.) will be sent to https://mega-api-prod.nemovideo.ai — do not upload sensitive/private data you wouldn't want sent to a third party. (2) The skill will obtain or require a NEMO_TOKEN; if you don't set one it will create an anonymous token and persist it for future calls — consider whether you prefer to provide your own token. (3) The frontmatter references a local config path (~/.config/nemovideo/) — expect local token/session storage; check and remove stored tokens if you later uninstall. (4) Verify the backend domain and service terms if you need a higher assurance level (no homepage or owner details are provided). If any of these are unacceptable, do not enable the skill or supply content you consider sensitive.
Capability Analysis
Type: OpenClaw Skill
Name: text-to-video-hindi
Version: 1.0.0
The skill bundle provides a functional integration for a Hindi text-to-video service via the nemovideo.ai API. It includes detailed instructions for the AI agent to handle authentication (using NEMO_TOKEN or anonymous UUIDs), session management, file uploads, and video rendering workflows. All identified behaviors, including network requests to mega-api-prod.nemovideo.ai and the handling of user-provided media, are consistent with the stated purpose of creating AI-generated videos and do not exhibit signs of malicious intent or unauthorized data exfiltration.
Capability Assessment
Purpose & Capability
The name/description (text→video Hindi) matches the runtime instructions: calls to a nemo video API, upload endpoints, SSE-based generation, credits and export endpoints. The declared primaryEnv (NEMO_TOKEN) is appropriate for authenticating to that backend. Minor mismatch: registry metadata earlier listed no configPaths, but the skill frontmatter references a config path (~/.config/nemovideo/) — this is plausible for a client but should be expected/noted.
Instruction Scope
Instructions are focused on creating sessions, sending messages, uploading files, and exporting results. They explicitly instruct generating an anonymous token if NEMO_TOKEN is not set, storing session_id and token for subsequent calls, and including attribution headers on every request. This stays within the service's scope, but it does involve: (a) obtaining and persisting a token on the user's behalf, and (b) sending user files to an external API. The SKILL.md also instructs not to display raw API responses or token values to users, which is reasonable but worth noting because it can hide debug data.
Install Mechanism
Instruction-only skill with no install step and no code files — lowest install risk. No downloads or package installs are specified.
Credentials
The skill only requires a single environment variable (NEMO_TOKEN), which maps to the backend API; that's proportionate. The frontmatter also references a config path (~/.config/nemovideo/), which could indicate the skill may read or write local config — the SKILL.md does not explicitly instruct scanning other system credentials. The runtime flow will generate and store an anonymous token if none is provided; users should be aware that tokens are created and persisted (and that anonymous tokens grant limited credits and expire in 7 days per the docs).
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent platform-wide privileges or modification of other skills. The skill does instruct storing session_id and the NEMO_TOKEN locally for subsequent requests, which is normal for a service client but worth noting for data retention and security posture.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install text-to-video-hindi - After installation, invoke the skill by name or use
/text-to-video-hindi - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of Text to Video Hindi skill: convert Hindi text/scripts into videos with visuals and voiceover.
- Supports uploading TXT, DOCX, PDF, SRT files up to 200MB and generates AI-powered videos automatically.
- Quick setup with free credits—automatically creates/authenticates sessions on first use.
- Handles exports, credits, uploads, and timeline previews with simple user commands.
- Rendered videos available in MP4 and other popular formats, processed in about 1–2 minutes per clip.
- Includes robust error handling and tips for fastest, most accurate results.
Metadata
Frequently Asked Questions
What is Text To Video Hindi?
Skip the learning curve of professional editing software. Describe what you want — हिंदी टेक्स्ट से वीडियो बनाओ with matching visuals and voiceover — and get... It is an AI Agent Skill for Claude Code / OpenClaw, with 87 downloads so far.
How do I install Text To Video Hindi?
Run "/install text-to-video-hindi" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Text To Video Hindi free?
Yes, Text To Video Hindi is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Text To Video Hindi support?
Text To Video Hindi is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Text To Video Hindi?
It is built and maintained by francemichaell-15 (@francemichaell-15); the current version is v1.0.0.
More Skills