How do I install the Pv Tool skill?

Run npx skillmds@latest add stvlynn/pv-tool in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pv Tool safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pv Tool?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pv Tool free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pv Tool?

stvlynn (@stvlynn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pv Tool by stvlynn — Agent Skill

Name: Pv Tool
Author: stvlynn

Pv Tool

Operate the bundled PV Tool kinetic typography web app for lyric videos, promotional videos, and motion-graphics text overlays. Use this whenever the user mentions PV Tool, wants to run or preview the app locally, build it for distribution, experiment with PV templates and effects, or work with lyric text, media backgrounds, audio-reactive overlays, or LRC input inside PV Tool.

stvlynn e86f2a3 141 files · 542.7 KB Updated Sep 17, 2026

File contents

PV Tool Skill

Use this skill to operate the vendored pv-tool application in app/.

What this skill is for

Start the local PV Tool dev server
Build the bundled app
Preview the production build
Use the app for lyric-video and kinetic-typography workflows

Important license note

The bundled upstream app in app/ is not under a generic permissive license.

Non-commercial use only by default
Commercial use requires a separate license from the upstream author
Check app/LICENSE and app/COMMERCIAL.md before using it for paid work

If the user asks to use PV Tool for a commercial workflow, call out this restriction explicitly.

Runtime requirements

Node.js 20+
npm

Commands

Run commands from skills/pv-tool/:

bash scripts/bootstrap.sh
bash scripts/dev.sh
bash scripts/build.sh
bash scripts/preview.sh

Environment overrides:

PV_TOOL_DEV_HOST=0.0.0.0
PV_TOOL_DEV_PORT=4173
PV_TOOL_PREVIEW_HOST=127.0.0.1
PV_TOOL_PREVIEW_PORT=4174
VITE_BASE=/pv-tool/

Standard workflow

Run bash scripts/bootstrap.sh to install dependencies into app/node_modules.
Run bash scripts/dev.sh for local editing and experimentation.
Open the reported local URL and use the UI.
Run bash scripts/build.sh when the user wants a production build.
Run bash scripts/preview.sh to verify the built output in a browser.

In-app usage

Start from a preset template or switch to Custom
Enter text with / as the segment separator
Load an image or video as the background media layer
Load audio for BPM and beat-reactive effects
Import .lrc files for lyric timing
Adjust post-FX such as shake, zoom, tilt, glitch, and hue shift
Use the built-in recording/export controls when the user needs captured output

Agent behavior

Prefer running the provided scripts instead of manually restating npm commands.
When starting dev.sh or preview.sh, report the exact local URL.
Keep long-running server processes attached unless the user asks to daemonize them.
If dependencies are missing, let the wrapper scripts install them first.
If Node.js is too old, stop and tell the user to upgrade before proceeding.

File layout

app/ — vendored upstream PV Tool source
scripts/bootstrap.sh — dependency installation
scripts/dev.sh — local Vite dev server
scripts/build.sh — production build
scripts/preview.sh — local preview server

---name: pv-tooldescription: Operate the bundled PV Tool kinetic typography web app for lyric videos, promotional videos, and motion-graphics text overlays. Use this whenever the user mentions PV Tool, wants to run or preview the app locally, build it for distribution, experiment with PV templates and effects, or work with lyric text, media backgrounds, audio-reactive overlays, or LRC input inside PV Tool.---# PV Tool SkillUse this skill to operate the vendored `pv-tool` application in `app/`.## What this skill is for- Start the local PV Tool dev server- Build the bundled app- Preview the production build- Use the app for lyric-video and kinetic-typography workflows## Important license noteThe bundled upstream app in `app/` is **not** under a generic permissive license.- Non-commercial use only by default- Commercial use requires a separate license from the upstream author- Check `app/LICENSE` and `app/COMMERCIAL.md` before using it for paid workIf the user asks to use PV Tool for a commercial workflow, call out this restriction explicitly.## Runtime requirements- Node.js 20+- npm## CommandsRun commands from `skills/pv-tool/`:```bashbash scripts/bootstrap.shbash scripts/dev.shbash scripts/build.shbash scripts/preview.sh```Environment overrides:```bashPV_TOOL_DEV_HOST=0.0.0.0PV_TOOL_DEV_PORT=4173PV_TOOL_PREVIEW_HOST=127.0.0.1PV_TOOL_PREVIEW_PORT=4174VITE_BASE=/pv-tool/```## Standard workflow1. Run `bash scripts/bootstrap.sh` to install dependencies into `app/node_modules`.2. Run `bash scripts/dev.sh` for local editing and experimentation.3. Open the reported local URL and use the UI.4. Run `bash scripts/build.sh` when the user wants a production build.5. Run `bash scripts/preview.sh` to verify the built output in a browser.## In-app usage- Start from a preset template or switch to `Custom`- Enter text with `/` as the segment separator- Load an image or video as the background media layer- Load audio for BPM and beat-reactive effects- Import `.lrc` files for lyric timing- Adjust post-FX such as shake, zoom, tilt, glitch, and hue shift- Use the built-in recording/export controls when the user needs captured output## Agent behavior- Prefer running the provided scripts instead of manually restating npm commands.- When starting `dev.sh` or `preview.sh`, report the exact local URL.- Keep long-running server processes attached unless the user asks to daemonize them.- If dependencies are missing, let the wrapper scripts install them first.- If Node.js is too old, stop and tell the user to upgrade before proceeding.## File layout- `app/` — vendored upstream PV Tool source- `scripts/bootstrap.sh` — dependency installation- `scripts/dev.sh` — local Vite dev server- `scripts/build.sh` — production build- `scripts/preview.sh` — local preview server

Frequently asked questions