mixer-scene-contract
Creates structured specs for arming and approving audio mixer scenes.
Install
mkdir -p .claude/skills/mixer-scene-contract && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14434" && unzip -o skill.zip -d .claude/skills/mixer-scene-contract && rm skill.zipInstalls to .claude/skills/mixer-scene-contract
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.
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.Key capabilities
- →Design schema fields and examples for mixer scene intents
- →Define an approval and audit model for scene changes
- →Generate CLI dry-run examples for scene arming
- →Map mixer scene intents to action plans
- →Provide a unit-test checklist for mixer scene functionality
How it works
This skill designs a structured contract for approved mixer scene changes by defining schema, approval workflows, and testing requirements. It focuses on specification rather than implementation.
Inputs & outputs
When to use mixer-scene-contract
- →Defining mixer scene schema
- →Designing dry-run audit flows
- →Specifying audio routing controls
About this skill
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.tssrc/automation/showDirectorRuntime.tssrc/cli/agent.tsaroundshow-directortests/unit/showDirector.test.tstests/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, orsetlist_ref. Do not design fuzzy live lookup as execution. - Preserve blocked/operator-only semantics for
mixer_gain,pa_mute, andaudio_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:
- proposed schema fields and examples;
- approval and audit model;
- CLI dry-run examples;
- mapping to action plans;
- compatibility notes;
- 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.
When not to use it
- →When implementing the mixer scene functionality, as this skill is for design/spec work
- →When fuzzy live lookup for execution is required, as explicit names or IDs are required
- →When generic `arm_effect` is sufficient and mixer scene changes do not need separation
Limitations
- →This skill is for design/spec work, not implementation
- →It requires explicit names or IDs for scenes, snapshots, or cues
- →It preserves blocked/operator-only semantics for `mixer_gain`, `pa_mute`, and `audio_routing`
How it compares
This skill provides a structured design and specification for mixer scene control with explicit approval and audit requirements, which is more formal than ad-hoc implementation without a predefined contract.
Compared to similar skills
mixer-scene-contract side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| mixer-scene-contract (this skill) | 0 | 2mo | No flags | Intermediate |
| fastapi-templates | 520 | 2mo | No flags | Intermediate |
| android-kotlin-development | 268 | 5mo | Review | Advanced |
| mcp-builder | 136 | 3mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Pantani
View all by Pantani →You might also like
fastapi-templates
wshobson
Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.
android-kotlin-development
aj-geddes
Develop native Android apps with Kotlin. Covers MVVM with Jetpack, Compose for modern UI, Retrofit for API calls, Room for local storage, and navigation architecture.
mcp-builder
anthropics
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
fastapi-pro
sickn33
Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and Pydantic V2. Master microservices, WebSockets, and modern Python async patterns. Use PROACTIVELY for FastAPI development, async optimization, or API architecture.
api-design-principles
wshobson
Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
telegram-bot-builder
davila7
Expert in building Telegram bots that solve real problems - from simple automation to complex AI-powered bots. Covers bot architecture, the Telegram Bot API, user experience, monetization strategies, and scaling bots to thousands of users. Use when: telegram bot, bot api, telegram automation, chat bot telegram, tg bot.