validate-engine

Validate synthesizer engines against D001-D006 and report PASS/FAIL with file:line evidence.

1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/BertCalm/XO_OX-XOmnibus --skill validate-engine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-engine
Source: https://github.com/BertCalm/XO_OX-XOmnibus/tree/main/.claude/skills/validate-engine
Command: npx skills add https://github.com/BertCalm/XO_OX-XOmnibus --skill validate-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run quality checks on an engine to ensure adherence to the 6 Doctrines and detect defects before deployment.

Core Features & Use Cases

  • D001-D006 rule checks against engine code and parameter layouts.
  • Generates a PASS/FAIL report with evidence and recommended fixes.
  • Use case: when adding a new engine or modifying DSP to ensure compliance.

Quick Start

Provide an engine name (e.g., Onset) to validate and review the resulting PASS/FAIL report.

Frequently Asked Questions about validate-engine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a synthesizer engine against the Doctrines before deployment?

To validate a synthesizer engine, you provide the engine name so the tool can read its source code and CLAUDE.md, checking rules D001-D006 and reporting a PASS/FAIL status with file and line evidence.

What is the 6 Doctrines engine check process for modified DSP code?

The 6 Doctrines engine check process reads modified engine source and CLAUDE.md files, applies D001-D006 rule checks to the code and parameter layouts, and generates a report with evidence and recommended fixes.

When do I need to run an engine quality audit for synthesizer compliance?

You need to run an engine quality audit when adding a new synthesizer engine, modifying DSP code, or conducting a quality review across the engine repository to ensure adherence to the 6 Doctrines and detect defects.

How do I get a PASS/FAIL report with evidence for engine code changes?

You get a PASS/FAIL report by providing the modified engine name for validation; the tool checks D001-D006 rules and outputs the report with specific file:line evidence and recommended fixes.

Does the validate-engine tool check parameter layouts in synthesizer DSP code?

Yes, the validate-engine tool checks parameter layouts in synthesizer DSP code by applying D001-D006 rule checks against the engine code and generating a PASS/FAIL report with evidence.