← Back to Skills Marketplace
Pixverse Ai
by
vcarolxhberger
· GitHub ↗
· v1.0.0
· MIT-0
110
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install pixverse-ai
Description
Tired of spending hours trying to produce cinematic video content without a film crew or budget? PixVerse AI changes that entirely. This skill connects you d...
Usage Guidance
This skill appears to do what it says: it sends prompts and any uploaded images to mega-api-prod.nemovideo.ai to generate videos and needs one token (NEMO_TOKEN). Before installing, consider: 1) The skill will use any NEMO_TOKEN in your environment — that token may be charged or tied to your account, so remove or rotate it if you do not want your account used. 2) Uploaded files and prompts are sent to an external service (privacy implications); do not upload sensitive files. 3) The registry metadata and SKILL.md disagree about a config path (~/.config/nemovideo/) — ask the maintainer to clarify what, if anything, will be written or read from disk. 4) There is no homepage or publisher info in the registry entry; if you need accountability or a privacy policy, request the service's documentation before use. If you trust nemovideo.ai and are comfortable with the above, the skill's requirements look proportionate to its purpose.
Capability Analysis
Type: OpenClaw Skill
Name: pixverse-ai
Version: 1.0.0
The skill is a functional integration for the PixVerse AI video generation service, facilitating text-to-video and image-to-video workflows. It provides detailed instructions for the agent to interact with the 'nemovideo.ai' backend, including session management, SSE stream handling, and asset export. The requested permissions (NEMO_TOKEN and ~/.config/nemovideo/) are consistent with the tool's purpose, and there is no evidence of data exfiltration, unauthorized execution, or malicious prompt injection.
Capability Assessment
Purpose & Capability
Name/description (AI video generation) lines up with the runtime instructions and the single required credential (NEMO_TOKEN). The API endpoints and operations described (session creation, SSE, upload, export, credits) are consistent with a cloud video-generation service. One minor inconsistency: the registry metadata provided earlier listed no required config paths, but the SKILL.md frontmatter includes a configPaths entry (~/.config/nemovideo/). This is likely a metadata mismatch but does not change the skill's stated purpose.
Instruction Scope
Instructions are explicit about network calls to mega-api-prod.nemovideo.ai, using Authorization: Bearer <NEMO_TOKEN>, creating sessions, uploading files/URLs, and using SSE streams. The skill tells the agent to read its YAML frontmatter and to detect install path (~/.clawhub/, ~/.cursor/skills/) to set an attribution header — reading the install path is reasonable for the requested X-Skill-Platform header but does require filesystem metadata access. The skill will upload user-supplied files and prompts to the remote service (expected for this capability). The guidance to 'keep technical details out of the chat' is a UX instruction and does not imply extra data collection, but it does reduce transparency of those network actions in chat.
Install Mechanism
No install/spec files and no code shipped — instruction-only. This is low-risk because nothing is written to disk by an installer. There are no remote downloads or package installs described.
Credentials
Only one environment variable is required (NEMO_TOKEN), which matches the need to authenticate to the external video service. That is proportionate for the stated purpose. Caveat: if a user already has NEMO_TOKEN in their environment the skill will use it (acting under that account); if no token exists it will request an anonymous starter token from the service. Also note the SKILL.md frontmatter lists a config path (~/.config/nemovideo/) while the registry metadata earlier indicated none — this is a metadata mismatch worth clarifying.
Persistence & Privilege
always is false and the skill does not request elevated or permanent platform privileges. It does not ask to modify other skills or system-wide configs. Autonomous invocation (model can call the skill) is the platform default and is not in itself a concern here.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install pixverse-ai - After installation, invoke the skill by name or use
/pixverse-ai - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
PixVerse AI Skill v1.0.0 — Turn text and images into cinematic videos in seconds.
- Instant AI video generation from text prompts or image uploads — no video editing required.
- Seamless connection to the PixVerse backend: handles authentication, session management, and API routing automatically.
- Supports credits checking, export/download workflow, and session state tracking.
- Detailed error handling for tokens, credits, file support, and rate limits, with clear user guidance.
- Includes prompt suggestions and best practices to help users get high-quality results faster.
Metadata
Frequently Asked Questions
What is Pixverse Ai?
Tired of spending hours trying to produce cinematic video content without a film crew or budget? PixVerse AI changes that entirely. This skill connects you d... It is an AI Agent Skill for Claude Code / OpenClaw, with 110 downloads so far.
How do I install Pixverse Ai?
Run "/install pixverse-ai" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Pixverse Ai free?
Yes, Pixverse Ai is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Pixverse Ai support?
Pixverse Ai is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Pixverse Ai?
It is built and maintained by vcarolxhberger (@vcarolxhberger); the current version is v1.0.0.
More Skills