Safely configure VSD Craft controls and plugins, preserve existing settings, and verify or recover device behavior.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install vsd-craft-operations
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install vsd-craft-operations using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
VSD Craft Operations guides an AI agent through configuring keys, knobs, scenes, and pages in VSD Craft, VSDinside, and StreamDock. It helps distinguish built-in actions from plugin features, install or update plugins in the correct location, and troubleshoot USB or KVM recovery issues.
The workflow emphasizes confirmed procedures, target-version and device differences, backups, and evidence-based verification. As part of Openclaw Skills, it also includes a read-only data inventory script and a verification sheet to make changes safer, traceable, and easier to roll back.
Use the skill within an environment that can access its bundled references and scripts. The SKILL.md does not specify a universal skill-install command; follow the host agent's instructions for adding skills. In VSD Craft, confirm the application data folder through Settings > General > Open Application Folder before inspecting or changing files.
Run the bundled inventory script with the confirmed data root when a read-only structural summary is useful:
python3 scripts/inspect_data.py --root <data-root>
Before making changes, read references/operations.md and copy references/verification.md into the working directory if you need to record verification evidence. No command-line installation procedure for VSD Craft or its plugins is specified; use the application's UI and the confirmed plugin location.
The skill does not define a new application data format. It works with existing VSD Craft data and uses the following locations and artifacts:
| Data or artifact | Purpose and handling |
|---|---|
| Application data root | Confirm through the application's Open Application Folder command; distinguish it from Elgato's separate folders. |
| plugins/ |
Confirmed plugin installation location. Preserve the old plugin version and user settings during updates. |
| Scenes and pages | Export the target scene before changes. Keep native scenes and pages distinct from plugin-internal virtual pages. |
| Selection-state configuration | Back up with the related plugin and scenes before file-based updates or recovery. |
| Timestamped backup directory | Store readable copies separately and record original-to-restoration path mappings. |
| Verification sheet | Copy references/verification.md into the working directory and record checks and evidence. |
| Inventory output | scripts/inspect_data.py summarizes directory structure and plugin manifests; it excludes configuration bodies and logs. |
The bundled test, scripts/test_inspect_data.py, uses temporary fixtures to check read-only behavior, omission of content, and exclusion of links. Do not share personal profiles, logs, device IDs, or credentials.
Loading
Build and port VSD Craft and StreamDock plugins with verified compatibility guidance, scaffolding, testing, and packaging workflows.

Turn audio and video recordings into timestamped transcripts, subtitles, and action-item notes with local Whisper processing.

Design AI-agent workflows that route requests intelligently while keeping competence, availability, novelty, and authorization distinct.

Harness AI Director connects eight specialized AI video agents to help turn video links, images, scripts, and clips into edited, review-ready content.

Dynamic Workflow turns large, independent work into repeatable agent workflows with file-based results, verification, and clear integration steps.

Screen Binance USD-M perpetuals for extreme funding rates, crowded positioning, and BTC, ETH, and SOL market regimes in one pay-per-request call.








































