Validate built iPlug2 plugins with format-specific validators for conformance.
npx skills add https://github.com/iPlug2/iPlug2 --skill validate-iplug2
Please help me install this Agent Skill. Skill: validate Source: https://github.com/iPlug2/iPlug2/tree/main/.claude/skills/validate Command: npx skills add https://github.com/iPlug2/iPlug2 --skill validate-iplug2
This Skill helps developers verify iPlug2 plugin builds against standard format validators to detect conformance issues before release.
Run the validate skill against your built plugin binaries to perform format-specific checks and report results.
High-intent search queries and answers about installing and using this skill.
You validate iPlug2 plugins by running format-specific validators such as auval, vstvalidator, clap-validator, and pluginval against your built binaries to verify IDs, formats, and metadata.
iPlug2 validation supports AUv2, AUv3, VST3, and CLAP formats, using their respective official validators to check conformance and compliance before release.
Yes, you can run pluginval, auval, vstvalidator, and clap-validator during CI pipelines or local development to enforce quality gates and catch compatibility issues early.
Yes, plugins must be built prior to validation, and the corresponding validator tools like auval and pluginval must be installed and accessible in your environment.
VST3 plugin validation fails when the built plugin has incorrect IDs, formats, or metadata, or if the required vstvalidator tool is not installed or accessible in your environment.
iPlug2Configure and build iPlug2 plugin projects with CMake generators.
carterbsCorrelate Git worktree context with OTEL JSONL logs to debug Gardener runtime failures.
mdrashedmamunOrchestrate PDF extraction through validation, approvals, and build verification.
BertCalmExecute XOmnibus builds and diagnose REGISTER_ENGINE, CMake, and auval failures.
