TypingMindTypingMindThe best frontend for AI
Validate Vst3 Editorhost logo

Validate Vst3 Editorhost

Organization
iPlug3
validate-vst3-editorhost

Test VST3 plugin UIs (.vst3 bundles) using Steinberg's EditorHost without a full DAW. Use when user says "test the plugin UI", "open in editorhost", "show the .vst3 editor", or wants to visually inspect the VST3 editor. For functional validation use validate-vst3 instead.

Overview

PublisheriPlug3
Repositoryaudio-plugin-dev-skills
Skill namevalidate-vst3-editorhost
Stars
100
Forks
4
Bundled files
Instructions only
LicenseMIT
Links
Skill sourceRepository
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by iPlug3 on GitHub. Read the source before you install it.

Installation

Install the Validate Vst3 Editorhost AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/iPlug3/audio-plugin-dev-skills/tree/main/plugins/audio-plugin-validators/skills/validate-vst3-editorhost
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/iPlug3/audio-plugin-dev-skills.git /tmp/audio-plugin-dev-skills
mkdir -p .claude/skills
cp -r /tmp/audio-plugin-dev-skills/plugins/audio-plugin-validators/skills/validate-vst3-editorhost .claude/skills/validate-vst3-editorhost
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Validate Vst3 Editorhost in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Validate Vst3 Editorhost on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Validate Vst3 Editorhost is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

VST3 EditorHost

Minimal VST3 host for testing plugin UIs without a full DAW.

Plugin Install Locations

editorhost accepts a direct path to a .vst3 bundle.

PlatformUser LocationSystem Location
macOS~/Library/Audio/Plug-Ins/VST3//Library/Audio/Plug-Ins/VST3/
Windows%LOCALAPPDATA%\Programs\Common\VST3\C:\Program Files\Common Files\VST3\
Linux~/.vst3//usr/lib/vst3/ or /usr/local/lib/vst3/

Instructions

  1. Build EditorHost from the VST3 SDK if not already built (see Building EditorHost below)
  2. Run: editorhost /path/to/plugin.vst3
  3. The plugin UI window should appear — verify layout, controls, and resizing
  4. Test multiple editor instances with --secondWindow
  5. If the UI doesn't appear, verify the plugin passes validator tests first

Usage

bash
# Basic usage - load plugin and show UI
editorhost /path/to/plugin.vst3

# With component handler (tests host callbacks)
editorhost --componentHandler /path/to/plugin.vst3

# Open second window (tests multiple editor instances)
editorhost --secondWindow /path/to/plugin.vst3

# Specify a particular effect class by UID
editorhost --uid "ABCD1234..." /path/to/plugin.vst3

Binary Locations

PlatformTypical Path
macOS<vst3sdk>/build/bin/Release/editorhost.app/Contents/MacOS/editorhost
Windows<vst3sdk>\build\bin\Release\editorhost.exe
Linux<vst3sdk>/build/bin/Release/editorhost

Building EditorHost

Clone the VST3 SDK if you don't have it, then build:

bash
cd <vst3sdk>
cmake -B build -G Ninja -DCMAKE_BUILD_TYPE=Release
cmake --build build --target editorhost

Linux: Requires X11 and GTK3 development libraries:

bash
# Debian/Ubuntu
sudo apt install libx11-dev libgtkmm-3.0-dev libxcb-util-dev libxcb-cursor-dev libxcb-keysyms1-dev libxcb-xkb-dev

# Fedora
sudo dnf install libX11-devel gtkmm3.0-devel xcb-util-devel xcb-util-cursor-devel xcb-util-keysyms-devel libxkbcommon-x11-devel

Troubleshooting

Plugin doesn't load

  • Check the plugin path is correct
  • Verify the plugin passes validator tests first
  • Check logs: Console.app (macOS), Event Viewer (Windows), or stderr (Linux)

UI doesn't appear

  • The plugin might not have an editor (hasEditor() returns false)
  • Check if createEditor() is returning a valid view
  • Linux: Ensure X11 display is available (echo $DISPLAY)

UI appears but is blank/wrong size

  • Check defaultEditorSize() returns valid dimensions
  • For WebView UIs, check the HTML content is being set correctly
  • Try with --secondWindow to see if the issue is with first-time setup

Frequently asked questions

What does the Validate Vst3 Editorhost AI skill do?

Test VST3 plugin UIs (.vst3 bundles) using Steinberg's EditorHost without a full DAW. Use when user says "test the plugin UI", "open in editorhost", "show the .vst3 editor", or wants to visually inspect the VST3 editor. For functional validation use validate-vst3 instead.

Why use Validate Vst3 Editorhost on TypingMind?

Because you install it once and use it with any model. Validate Vst3 Editorhost is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Validate Vst3 Editorhost in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/iPlug3/audio-plugin-dev-skills/tree/main/plugins/audio-plugin-validators/skills/validate-vst3-editorhost. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Validate Vst3 Editorhost?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Validate Vst3 Editorhost?

As many as you like. As long as a model supports skills, you can use Validate Vst3 Editorhost with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Validate Vst3 Editorhost AI skill free?

Yes. It is published on GitHub by iPlug3 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
openclaw logo

Gitcrawl

openclaw
OrganizationPopular

GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.

82.2K
391K
1 files
View
openclaw logo

Graincrawl

openclaw
OrganizationPopular

Granola archive: search, sync freshness, notes, transcripts, panels, SQL counts, and Graincrawl repo work.

82.2K
391K
1 files
View
openclaw logo

Openclaw Changelog Update

openclaw
OrganizationPopular

Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.

82.2K
391K
1 files
View
openclaw logo

Openclaw Ci Limits

openclaw
OrganizationPopular

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

82.2K
391K
1 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇