ClawHub

VibeVideoIO AI Script to Video

v1.0.5

Log into bollo.video or vibevideo.io, list Studio projects, create Studio episodes from prompts or scripts, and log out. Use when users ask to make or genera...

⭐ 0· 121·0 current·0 all-time
byVibeVideo IO@vibevideo

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for vibevideo/vibevideo-core.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "VibeVideoIO AI Script to Video" (vibevideo/vibevideo-core) from ClawHub.
Skill page: https://clawhub.ai/vibevideo/vibevideo-core
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
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 vibevideo-core

ClawHub CLI

Package manager switcher

npx clawhub@latest install vibevideo-core
Security Scan
Capability signals
CryptoRequires OAuth tokenRequires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The skill name and description match the included CLI code and SKILL.md: the package provides a node-based CLI to login, list Studio projects, create episodes, handle CAPTCHA/email flows, and logout against bollo.video or vibevideo.io. Minor inconsistency: registry-level 'Requirements' reported no required binaries, while the skill metadata and package.json clearly expect Node.js (node >=20) and the SKILL.md lists node in metadata; this is a small metadata mismatch, not a functional red flag.
✓
Instruction Scope
The SKILL.md is explicit: it instructs the agent to run the local CLI (node .../scripts/vibevideo-studio.mjs) to perform login, projects, create-episode, and logout. The CLI reads/writes local OpenClaw session and media files (under ~/.openclaw by default), handles CAPTCHA and email verification only as part of login, and does not attempt OCR or automatic external delivery except via the documented OpenClaw messaging hooks. There are no instructions to read unrelated system files or to send arbitrary data to unknown endpoints; API endpoints used are bollo.video and vibevideo.io as described.
ℹ
Install Mechanism
There is no remote download/install step; the package includes a local registration script (scripts/register-openclaw-skill.mjs) that, when run, copies the skill into the user's OpenClaw home (~/.openclaw/skills/<skillId>) and writes a managed marker. The script does file copies locally and filters common build artifacts; it is not run automatically during postinstall. Because it operates only on local filesystem paths and does not fetch remote code, install risk is low — but running the registration script will write files into the user's OpenClaw skills directory.
✓
Credentials
The skill does not require external API keys or secrets via environment variables. It optionally respects OPENCLAW_HOME to locate its storage and reads OPENCLAW_MCP_SESSION_KEY to detect OpenClaw session context; the register script respects OPENCLAW_VIBEVIDEO_STUDIO_SKIP_POSTINSTALL and OPENCLAW_VIBEVIDEO_STUDIO_AUTO_SETUP to control registration. These environment variables are proportional to the described functionality (local storage location and registration control).
ℹ
Persistence & Privilege
The CLI persistently stores session state and CAPTCHA media under the OpenClaw home (DEFAULT_SESSION_FILE and DEFAULT_CAPTCHA_DIR, e.g. ~/.openclaw/secrets and ~/.openclaw/media) and the optional registration step copies the skill into the user's OpenClaw skills folder. always:true is not set. Autonomous invocation by the agent is allowed (platform default) — combined with the local storage behavior this means a skill run can create or update local session files, which is expected for a provider-bridge skill but users should be aware of token persistence and where files are stored.
Assessment
This package appears coherent: it is a node-based CLI for VibeVideo Studio and its files implement the login/CAPTCHA/episode-creation flows described in SKILL.md. Before installing or registering the skill, consider: 1) the package will store session tokens and CAPTCHA images under your OpenClaw home (~/.openclaw by default); inspect those files if you need to revoke or remove credentials. 2) Registration (npm run openclaw:register) copies the skill into ~/.openclaw/skills — do not run it unless you trust the skill source. 3) The package requires Node >=20; ensure you run it in a trusted environment. 4) The small metadata mismatch (registry shows no required binaries while SKILL.md/package.json expect node) is benign but worth noting. If you want extra assurance, review the included scripts (skills/.../scripts/vibevideo-studio.mjs and register-openclaw-skill.mjs) yourself or run them in an isolated environment before adding them to your primary OpenClaw installation.

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

latestvk9741v4wa3npvjvr0179akc87d856c9c
121downloads
0stars
6versions
Updated 1w ago
v1.0.5
MIT-0
VibeVideo IO@vibevideo
latest
Download

VibeVideoIO AI Script to Video

This package exposes a single canonical skill:

  • skills/vibevideoio-ai-script-to-video/SKILL.md

Install Notes

  • Local OpenClaw skill registration is manual via npm run openclaw:register
  • The package does not auto-register itself during postinstall

When To Use

  • Create / make / generate an AI video
  • Turn a prompt / script / story into a video
  • Paste a screenplay or short video script and ask to make it into an AI video
  • Log into bollo.video or vibevideo.io
  • List or manage Studio projects

Default Site Rule

  • Chinese input → bollo.video
  • English input → vibevideo.io
  • Explicit user choice overrides the default

Site Consistency Rule

  • If the login site is vibevideo.io, keep all subsequent Studio operations on the vibevideo.io web/API endpoints
  • If the login site is bollo.video, keep all subsequent Studio operations on the bollo.video web/API endpoints
  • Do not mix vibevideo.io web pages or APIs with a bollo.video login session, and do not mix bollo.video web pages or APIs with a vibevideo.io login session

Error And Retry Policy

  • For login continuation errors, return the exact CLI/API error to the user first
  • Only retry login when the user explicitly asks, or when the error clearly means the CAPTCHA expired/was incorrect and a fresh CAPTCHA is required
  • For create-episode failures such as fetch failed, timeout, HTTP/API errors, or backend generation errors, return the failure result directly and stop
  • When returning a create-episode failure, also include any known generation context such as video ID, title, aspect ratio, style mode, and project information
  • Do not automatically rerun create-episode, do not silently switch sites, and do not change the script/style/aspect ratio/project to retry on the user's behalf
  • After returning the error, ask the user whether they want to retry manually or adjust inputs

Source Of Truth

For all detailed behavior, follow:

  • skills/vibevideoio-ai-script-to-video/SKILL.md

That file is the single source of truth for:

  • login and CAPTCHA flow
  • Feishu vs local preview behavior
  • episode creation questions
  • CLI command usage and expected results

Key Files

  • skills/vibevideoio-ai-script-to-video/SKILL.md
  • skills/vibevideoio-ai-script-to-video/scripts/vibevideo-studio.mjs
  • agents/openai.yaml
  • references/current-system-map.md

Comments

Loading comments...