Is mixer-scene-contract safe to install?

SaferSkills independently audited mixer-scene-contract (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.claude/skills/mixer-scene-contract/SKILL.md · 1 file

.claude/skills/mixer-scene-contract/SKILL.md1.6 KB · Markdown

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:

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.

mixer-scene-contract— agent skill

Is mixer-scene-contract safe to install?

mixer-scene-contract

Context to read

Design rules

Output

Quality bar

Audit the pieces. Scan the whole. Decide.