Skills Guide

Mixer Scene Contract

VerifiedSafe

Design the structured contract for approved mixer scene changes, including schema fields, approval and audit model, CLI dry-run examples, and test checklist.

Download and use
Sby Skills Guide Bot
DevelopmentIntermediate
7/30/2026
Claude CodeCursorCodex
#schema-design#approval-workflow#audit-logging#cli-dry-run#mixer-control

Recommended for

Backend developerClaude CodeCode reviewFrontend developerCursorFullstack developer

Automated summary

Designs the structured contract — MixerSceneIntent schema, approval and audit model, dry-run CLI shape, and test checklist — for operator-approved scene arming on a Soundcraft Ui24R mixer.

Strengths

  • Cleanly separates the 'arm scene/cue for approval' MVP operation from autonomous execution and from the generic arm_effect path.
  • Requires explicit identifiers (show_name, snapshot_name, cue_name, scene_id, setlist_ref) rather than fuzzy live lookup.
  • Specifies a full audit entry per accepted request: request, intent, decision, approval ID, operator, and adapter target.
  • Names the context files to read and the unit tests to cover, so a builder can implement without follow-up questions.

Limitations

  • Design/spec work only — it does not deliver the schema implementation or runtime code.
  • Assumes the referenced showDirector and CLI source files already exist in the repository.
  • Deliberately scopes out live scene lookup and any autonomous execution.
When to use it

Use whenever a task mentions mixer scenes, Ui24R snapshots/cues, operator-approved mixer control, or revisions to the show-director contract and dry-run CLI shape.

When not to use it

Avoid it when the goal is writing the implementation code, actually driving the console, or handling non-mixer effect arming.

Security analysis

Safe
Quality score85/100

The skill is purely a design/specification workflow: it instructs reading source files and writing a contract document to a workspace markdown file. It declares no tools, performs no execution, and does not include destructive, exfiltration, or obfuscation patterns. The only filesystem action is writing a local markdown file, which is low risk.

No concerns found

How this analysis is made

Examples

Initial contract draft
Write the mixer scene contract for our AI party show director: define the MixerSceneIntent schema fields, the approval and audit model, dry-run CLI examples, action-plan mapping, and a unit-test checklist. Output to _workspace/ai-party-mixer/01_contract.md.
Revise for explicit IDs
Update the mixer scene contract so every request must carry show_name, snapshot_name, cue_name, scene_id or setlist_ref instead of a fuzzy live lookup, and show the new CLI dry-run shape plus audit entry.
Keep gain and mute blocked
Revise the show-director contract follow-up: confirm mixer_gain, pa_mute and audio_routing stay operator-only, separate mixer scene arming from arm_effect, and list the showDirector and cliAgent tests to add.

name: mixer-scene-contract description: "Design the MixerSceneIntent, approval state, JSON schema, CLI examples, audit entries, and tests for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use whenever a task mentions mixer scenes, Ui24R snapshots/cues, operator-approved mixer control, show-director contract updates, schema updates, dry-run CLI shape, or follow-ups that revise this contract."

mixer-scene-contract

Design the structured contract for approved mixer scene changes. This skill is for design/spec work, not implementation.

Context to read

  • src/automation/showDirectorSchema.ts
  • src/automation/showDirectorRuntime.ts
  • src/cli/agent.ts around show-director
  • tests/unit/showDirector.test.ts
  • tests/unit/cliAgent.test.ts

Design rules

  • Keep mixer scene changes separate from generic arm_effect.
  • The MVP operation is "arm scene/cue for approval", not autonomous execution.
  • Require explicit names or IDs: show_name, snapshot_name, cue_name, scene_id, or setlist_ref. Do not design fuzzy live lookup as execution.
  • Preserve blocked/operator-only semantics for mixer_gain, pa_mute, and audio_routing.
  • Every accepted request needs an audit entry with request, intent, decision, approval ID, operator, and adapter target.

Output

Write _workspace/ai-party-mixer/01_contract.md with:

  1. proposed schema fields and examples;
  2. approval and audit model;
  3. CLI dry-run examples;
  4. mapping to action plans;
  5. compatibility notes;
  6. unit-test checklist.

Quality bar

The result should be specific enough that a builder can implement it without asking what fields exist or how approval flows.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/mixer-scene-contract-ms71b317/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/mixer-scene-contract-ms71b317' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/mixer-scene-contract-ms71b317/download' --output '.skill-downloads/mixer-scene-contract-ms71b317/SKILL.md.part' && mv '.skill-downloads/mixer-scene-contract-ms71b317/SKILL.md.part' '.skill-downloads/mixer-scene-contract-ms71b317/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/mixer-scene-contract-ms71b317/SKILL.md' && test -s '.skill-downloads/mixer-scene-contract-ms71b317/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/mixer-scene-contract' && cp -R '.skill-downloads/mixer-scene-contract-ms71b317' '.claude/skills/mixer-scene-contract'

Cursor
test -f '.skill-downloads/mixer-scene-contract-ms71b317/SKILL.md' && test -s '.skill-downloads/mixer-scene-contract-ms71b317/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/mixer-scene-contract' && cp -R '.skill-downloads/mixer-scene-contract-ms71b317' '.cursor/skills/mixer-scene-contract'

Codex
test -f '.skill-downloads/mixer-scene-contract-ms71b317/SKILL.md' && test -s '.skill-downloads/mixer-scene-contract-ms71b317/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/mixer-scene-contract' && cp -R '.skill-downloads/mixer-scene-contract-ms71b317' '.agents/skills/mixer-scene-contract'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/mixer-scene-contract-ms71b317'

openskills read 'mixer-scene-contract-ms71b317'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/mixer-scene-contract-ms71b317/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot