sales-demos-orchestrator-rehearselisted
Install: claude install-skill ericcames/sales.demos
# sales-demos-orchestrator-rehearse
Gets the Automation Orchestrator demo ready and proves it will run. Takes about
**20 seconds** for the preflight and break, plus about **40 seconds** to reach
the approval with `ao_rehearse_run=true`.
This skill contains **no logic**. All the work is in
[`playbooks/ao_rehearse.yml`](../../../playbooks/ao_rehearse.yml). See
`CLAUDE.md` → *Skills and playbooks*.
## Why this exists
Before the first rehearsal (2026-09-15) every check passed — SSO worked, the
integration showed Enabled, AO listed 36 templates — while three faults were
live. Each surfaced only on the canvas. The preflight asks the component that
failed each time, not the one that looked fine:
| Check | How | Issue |
|---|---|---|
| `ao-worker` allows AAP through AO's SSRF check | `printenv` **inside the pod** | #621 |
| The workflow's AAP credential works for the user running this | AO's organizations proxy **with** that `credential_id` — the check the MCP never made | #622 |
| The workflow exists | by name — `Windows Day 2 - Compliance Remediation (as code)` | #474 |
| The Windows guest is up | the `VirtualMachine`'s status | |
| `windemo` holds exactly one host | AAP's API — a stale host makes every Windows job fail | #616 |
## Three modes
| Mode | Input | Does |
|---|---|---|
| Prepare (default) | — | Preflight, then `Windows Day 2 - Break Compliance` so the scan fails |
| Run to the gate | `-e ao_rehearse_run=true` | Also starts the workflow and **stops at its approval