seance

Evaluate synthesizer engines against the canonical ghost-panel seance framework.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Formalizes a reproducible protocol to evaluate synthesizer engines against a canonical ghost panel, turning subjective judgments into structured, repeatable assessments.

Core Features & Use Cases

  • Provides a formal seance evaluation framework across the eight ghost-panel perspectives to judge an engine’s sonic identity, expressivity, and maturation.
  • Covers Doctrine Compliance, Sonic Identity, Preset Quality, Coupling Potential, Blessing candidates, and Debate relevance to guide targeted improvements.
  • Integrates existing references and synthesis guides to ensure consistent, auditable evaluations across engines.

Quick Start

Resolve the engine name to its Source directory and initiate the seance evaluation against that engine's presets.

Frequently Asked Questions about seance

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

FAQPage Schema
How do I evaluate a synthesizer engine against a structured framework?

To evaluate a synthesizer engine against a structured framework, you apply a formal seance protocol to assess doctrine compliance, sonic identity, preset quality, coupling potential, and debate relevance, producing a scored report with actionable recommendations.

What is the ghost panel framework for audio synthesis engine evaluation?

The ghost panel framework is a canonical seance protocol that provides eight perspectives to formally judge a synthesizer engine's sonic identity, expressivity, and maturation, turning subjective judgments into repeatable, auditable assessments.

How do I run a preset review for my synthesizer's Source directory?

To run a preset review, you resolve the engine name to its Source directory, inspect its presets, and consult seance references to evaluate preset quality and sonic identity, generating actionable improvement recommendations.

Can I assess doctrine compliance across multiple registered synthesizer engines?

Yes, you can assess doctrine compliance across multiple registered engines by applying the seance evaluation protocol uniformly, ensuring consistent and auditable comparisons of coupling potential and sonic identity.

Does engine evaluation require external dependencies or components?

No external dependencies or components are required for engine evaluation; the protocol operates independently by reading the engine's Source directory and consulting its own seance references to produce structured scores.