VSD Craft Plugin Development for Openclaw

Build and port VSD Craft and StreamDock plugins with verified compatibility guidance, scaffolding, testing, and packaging workflows.

nextaltair
v1.0.0
Oct 10, 2026
0
134
0

Install & Download

1. ClawHub CLI

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

npx clawhub@latest install vsd-craft-plugin-development

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-plugin-development 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 Plugin Development?

VSD Craft Plugin Development is an Openclaw Skills guide for creating new VSD Craft, VSDinside, and StreamDock plugins, as well as porting Elgato Stream Deck plugins. It helps developers distinguish reusable Elgato APIs from VSD Craft-specific behavior and implement SDK communication, inspectors, key and knob input, rendering, reconnection, and packaging.

The workflow emphasizes evidence-based compatibility, separate state for each placement context, safe cleanup on disconnect, and validation before hardware testing. Use it for plugin development and porting; built-in device configuration is outside its scope and should use the separate VSD Craft operations skill.

VSD Craft Plugin Development Use Cases

  • Create a new VSD Craft or StreamDock plugin from a minimal scaffold.
  • Port an existing Elgato Stream Deck plugin by separating domain logic from host-specific registration, rendering, and settings UI.
  • Implement key or knob input, inspector settings, display behavior, and SDK communication.
  • Diagnose reconnection, disconnect, or disappearing-device behavior while preserving user-owned settings.
  • Run mock-host tests and package a reviewed plugin archive before an optional installation or hardware check.

How VSD Craft Plugin Development Works

  1. Review the bundled Elgato compatibility matrix and identify which APIs and wire formats can be reused, adapted, or must be reimplemented.
  2. Establish the device model, application version, operating system, requested behavior, and existing built-in capabilities; use field observations to clarify scenes, coordinates, and reconnection assumptions.
  3. Generate a scaffold for a new plugin, or separate portable domain logic from host-dependent code when porting an existing plugin.
  4. Implement registration, input dispatch, rendering, inspector settings, and reconnection. Keep state separate for each placement context, and clear held input and pending operations when a device disconnects or disappears.
  5. Install dependencies and run the mock-host test suite to check the manifest, registration, input, inspector settings, multiple contexts, reconnection, and host shutdown.
  6. Package only the intended allowlisted files, then inspect the archive to ensure it includes runtime dependencies and excludes personal settings, logs, test records, and secrets.
  7. If installation is explicitly requested, preserve the existing version, install to the actual VSD Craft plugins directory, and perform the documented application and physical hardware checks. Report static, mock-host, application, and hardware results separately.

VSD Craft Plugin Development Setup

The skill provides scripts and a template rather than a single package-install command. Resolve resource paths from the skill directory. For a new plugin, replace the example ID and name, and choose a new output directory:

python3 scripts/scaffold.py --id com.example.counter --name "Counter" --output <new-directory>/com.example.counter.sdPlugin
cd <new-directory>/com.example.counter.sdPlugin
npm install --ignore-scripts --omit=optional --no-audit --no-fund
npm test

For subsequent dependency installs, use npm ci with the project lockfile. Review the compatibility matrix and development guide before implementation. To create an archive after validation, run the packaging helper from the skill directory:

python3 scripts/package_plugin.py <generated-directory> --output <new-zip>

The packaging helper targets the bundled counter scaffold. Update its explicit allowlist when a production plugin adds dependencies or assets. Install into VSD Craft only when installation is in scope, after confirming the real plugins directory and preserving the old version.

VSD Craft Plugin Development Data Schema & Taxonomy

The scaffold creates a plugin directory with the files needed for a minimal plugin. Exact manifest fields and implementation details should follow the bundled template and development guide.

Area Purpose
Manifest Declares the plugin and its actions; references must resolve to files included in the plugin.
Entry point Implements host registration and plugin behavior, including input event handling and rendering.
Images and UI Supplies plugin imagery and the inspector interface, including its HTML and JavaScript.
Tests Includes mock-host smoke tests for registration, input, inspector settings, multiple contexts, reconnection, and shutdown.
Runtime dependencies Installed from the package definition; include required production dependencies in the archive.
State Keep state distinct for each placement context, even when action UUIDs match. Discard held-input state and pending operations on disconnect or disappearance, while preserving user-owned settings such as manual titles.
Archive Contains only reviewed, allowlisted plugin files; exclude personal settings, logs, test records, and secrets. Expand the packaging helper's explicit file list when needed.

Supporting reference files document Elgato compatibility, field observations, official sources and verification dates, development procedures, and hardware checks.

VSD Craft Plugin Development Advanced Features

  • Compatibility-led porting: use the bundled matrix to focus additional research on unverified APIs and target-version differences.
  • Host and rendering distinctions: treat the Creator SDK background-rendering path separately from the VSD Craft plugin socket.
  • Placement-aware behavior: dispatch by event name and maintain independent state for each action placement context.
  • Resilient lifecycle handling: clear held inputs and pending operations on disconnect or disappearance, and implement reconnection without overwriting user-owned settings.
  • Mock-host verification: test through temporary localhost ports without connecting to VSD Craft or physical hardware.
  • Controlled release packaging: review the archive and update the scaffold-targeted allowlist when adding production assets or dependencies.
  • Staged verification: distinguish static checks, mock-host tests, real-application validation, and physical hardware results in the final report.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*