Validates built iPlug2 audio plugins against industry-standard format requirements.
Install
mkdir -p .claude/skills/validate && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4195" && unzip -o skill.zip -d .claude/skills/validate && rm skill.zipInstalls to .claude/skills/validate
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Validate iPlug2 plugin builds using format-specific validators (auval, pluginval, vstvalidator, clap-validator) (project)Key capabilities
- →Extract plugin identifiers from config.h
- →Validate AUv2 and AUv3 plugins using auval
- →Validate VST3 plugins using vstvalidator
- →Validate CLAP plugins using clap-validator
- →Run multi-format validation with pluginval
How it works
It reads plugin identifiers from the project configuration, determines the AU type, and executes the appropriate format-specific validator tool.
Inputs & outputs
When to use validate
- →Validate AUv2 plugin
- →Run plugin build tests
- →Verify plugin identifiers
- →Debug plugin compatibility
About this skill
Validate iPlug2 Plugin
Validate a built plugin using format-specific validation tools. Plugin must have been built prior to using this skill.
Arguments
PROJECT_NAME(required): Name of the project (e.g.,IPlugEffect)FORMAT(optional): Specific format to validate (AU,AUv3,VST3,CLAP,all). Default:all
Validation Workflow
Step 1: Read config.h to extract plugin identifiers
Read Examples/[PROJECT_NAME]/config.h or Tests/[PROJECT_NAME]/config.h and extract:
PLUG_NAME- Plugin display namePLUG_UNIQUE_ID- 4-char subtype (e.g.,'Ipef'→Ipef)PLUG_MFR_ID- 4-char manufacturer code (e.g.,'Acme'→Acme)PLUG_MFR- Manufacturer display namePLUG_TYPE- 0=effect (aufx), 1=instrument (aumu), 2=MIDI effect (aumf)
Step 2: Determine AU type from PLUG_TYPE
PLUG_TYPE 0 → aufx
PLUG_TYPE 1 → aumu
PLUG_TYPE 2 → aumf
Step 3: Validate each format
AUv2 (macOS) - auval
# Restart audio server first to pick up changes
sudo killall -9 AudioComponentRegistrar 2>/dev/null; sleep 1
# Run validation
auval -v [AU_TYPE] [PLUG_UNIQUE_ID] [PLUG_MFR_ID]
Example: auval -v aufx Ipef Acme
Look for AU VALIDATION SUCCEEDED at the end.
Useful auval options:
-strict- Enforce strict checks (recommended for release)-r N- Repeat validation N times-o- Quick open/init test only (faster debugging)-q- Quiet mode (errors/warnings only)
AUv3 (macOS) - auval
Note: The host app must be built codesigned and launched at least once to register the AUv3 extension. AUv2 plugin should be removed to avoid conflict. Auval usage the same as AUv2, but should see "This AudioUnit is a version 3 implementation."
VST3 - vstvalidator
Build vstvalidator if not present:
# macOS/Linux
cd Dependencies/IPlug && ./download-vst3-sdk.sh master build-validator
# Windows (use Git Bash or WSL)
cd Dependencies/IPlug && ./download-vst3-sdk.sh master build-validator
The validator binary will be at Dependencies/IPlug/VST3_SDK/validator (or validator.exe on Windows).
Run validation:
# macOS
Dependencies/IPlug/VST3_SDK/validator ~/Library/Audio/Plug-Ins/VST3/[PLUG_NAME].vst3
# Windows
Dependencies\IPlug\VST3_SDK\validator.exe "C:\Program Files\Common Files\VST3\[PLUG_NAME].vst3"
CLAP - clap-validator
Install clap-validator: Download from https://github.com/free-audio/clap-validator/releases
Run validation:
# macOS
clap-validator validate ~/Library/Audio/Plug-Ins/CLAP/[PLUG_NAME].clap
# Windows
clap-validator.exe validate "C:\Program Files\Common Files\CLAP\[PLUG_NAME].clap"
Look for X tests run, Y passed, 0 failed at the end.
Useful options:
--in-process- Run in-process (faster)--only-failed- Show only failed tests
Multi-format: pluginval
# macOS
brew install --cask pluginval
/Applications/pluginval.app/Contents/MacOS/pluginval --strictness-level 5 --validate ~/Library/Audio/Plug-Ins/VST3/[PLUG_NAME].vst3
# Windows (download from https://github.com/Tracktion/pluginval/releases)
pluginval.exe --strictness-level 5 --validate "C:\Program Files\Common Files\VST3\[PLUG_NAME].vst3"
Plugin Locations
| Format | macOS | Windows |
|---|---|---|
| AUv2 | ~/Library/Audio/Plug-Ins/Components/[NAME].component | N/A |
| AUv3 | ~/Applications/[NAME].app/Contents/PlugIns/[NAME].appex | N/A |
| VST3 | ~/Library/Audio/Plug-Ins/VST3/[NAME].vst3 | C:\Program Files\Common Files\VST3\[NAME].vst3 |
| CLAP | ~/Library/Audio/Plug-Ins/CLAP/[NAME].clap | C:\Program Files\Common Files\CLAP\[NAME].clap |
Expected Output
Report validation results in a table:
| Format | Status | Details |
|---|---|---|
| AUv2 | PASS/FAIL | Brief summary |
| AUv3 | PASS/FAIL/SKIP | Reason if skipped |
| VST3 | PASS/FAIL/SKIP | Reason if skipped |
| CLAP | PASS/FAIL/SKIP | Reason if skipped |
When not to use it
- →Plugins that have not been built yet
Prerequisites
Limitations
- →Requires pre-built plugins
- →AUv3 requires host app codesigning and registration
How it compares
It automates the extraction of identifiers and standardizes the reporting across multiple plugin formats compared to manual command-line execution.
Compared to similar skills
validate side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| validate (this skill) | 1 | 7mo | Review | Intermediate |
| code-coverage-with-gcov | 15 | 4mo | Review | Intermediate |
| unity-mcp-orchestrator | 17 | 4mo | No flags | Intermediate |
| 3d-games | 16 | 6mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by iPlug2
View all by iPlug2 →You might also like
code-coverage-with-gcov
gadievron
Add gcov code coverage instrumentation to C/C++ projects
unity-mcp-orchestrator
CoplayDev
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
3d-games
davila7
3D game development principles. Rendering, shaders, physics, cameras.
dev
atopile
LLM-focused workflow for working in this repo: compile Zig, run the orchestrated test runner, consume test-report.json/html artifacts, and discover/debug ConfigFlags.
rsyslog-test
rsyslog
Standardizes testing and validation for rsyslog using the diag.sh framework.
libfuzzer
trailofbits
Coverage-guided fuzzer built into LLVM for C/C++ projects. Use for fuzzing C/C++ code that can be compiled with Clang.