VSD Craft Operations for Openclaw

Safely configure VSD Craft controls and plugins, preserve existing settings, and verify or recover device behavior.

nextaltair
v1.0.0
Oct 10, 2026
0
63
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install vsd-craft-operations

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

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).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is VSD Craft Operations?

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.

VSD Craft Operations Use Cases

  • Configure a key or knob using the actions available in the installed application version.
  • Identify whether a requested behavior requires a built-in action or a custom plugin implementation.
  • Install or update a plugin while preserving user settings, scenes, manual titles, and other plugins.
  • Back up a scene, plugin, and selection-state configuration before file-based changes or recovery.
  • Diagnose USB reconnection, device display, or KVM round-trip problems using a layered troubleshooting sequence.
  • Inspect an application data directory without exposing configuration bodies or logs.
  • Prepare a handoff that records verified behavior, unknowns, backup locations, and restoration steps.

How VSD Craft Operations Works

  1. Classify the request as built-in action configuration, plugin installation or update, or recovery; consult the confirmed workflows and model differences first.
  2. Record the application version, operating system, device model, connection path, target scene or page, and application data location. Confirm the location through Settings > General > Open Application Folder.
  3. Inspect the selected control's available actions. For the observed basic hotkey action, check the separate left-rotation, right-rotation, and press fields. Keep native scenes and pages distinct from plugin-internal virtual pages.
  4. Export the target scene. Before file-based changes or recovery, quit the application normally and make timestamped copies of the target plugin, related scenes, and selection-state configuration.
  5. Apply the requested change, preferring the UI for settings. For plugin installation, use the confirmed plugins/.sdPlugin location and identify the active installation target using the running executable and path shown in the UI.
  6. Restart the application only when needed, then verify rendering, physical input, device display, USB reconnection, and KVM round trips as separate checks. Trace recovery failures through application and device connectivity, the plugin process, WebSocket registration, and display contexts.
  7. Hand off the change summary, verification results, unknowns, backup paths, and restoration steps. Do not report unperformed checks as passes or include personal profiles, logs, device IDs, or credentials in shared artifacts.

VSD Craft Operations Setup

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.

VSD Craft Operations Data Schema & Taxonomy

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/.sdPlugin 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.

VSD Craft Operations Advanced Features

  • Version- and model-aware procedures: reuse recorded findings and investigate only unverified behavior or relevant target differences.
  • Safe rollback planning: export scenes, create timestamped copies, and document restoration mappings before file-based changes.
  • Read-only inventory: summarize directory structure and plugin manifests without printing configuration bodies or logs.
  • Controlled plugin updates: identify the active installation target and preserve existing settings and unrelated plugins.
  • Layered USB/KVM diagnosis: check application and device connectivity, plugin process, WebSocket registration, and display contexts in sequence.
  • Evidence-based verification: test application rendering, physical input, device display, USB reconnection, and KVM round trips independently.
  • Reusable handoffs: record changes, verified behavior, unknowns, backups, and rollback steps while excluding sensitive artifacts.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*