sales-demos-first-timelisted

First-time setup for the sales.demos repo on a new machine. Checks and guides every local prerequisite — Automation Hub token, the vault password and the secrets file you build from the example, pinned collections, the python kubernetes client, the CLI tools (oc, terraform, virtctl, helm), the run-log directory, and the environment's passwords — then validates each one. TRIGGER when: the user is new to this repo, asks how to get started, says prerequisites are missing, or hits errors about vault decryption, a missing vault password, `couldn't resolve module/action`, or an undefined connection variable. SKIP: if setup is already done and the user wants to point at a new environment — that is sales-demos-bootstrap — or run a phase, which is that phase's own skill.
ericcames/sales.demos · ★ 1 · DevOps & Infrastructure · score 67

Install: claude install-skill ericcames/sales.demos

# sales-demos-first-time Walks a new machine through every local prerequisite for this repo, then validates them. Run once per machine; after that point it at an RHDP cluster with [`/sales-demos-bootstrap`](https://github.com/ericcames/sales.demos/blob/main/.claude/skills/sales-demos-bootstrap/SKILL.md). **This repo is self-contained.** Every skill it needs lives in `.claude/skills/` and is discovered natively — no marketplace, no plugin. Do not send the user to a skill from another repo or plugin; if something is missing here, add it here. The `sales-demos-` prefix keeps these unambiguous when other skills happen to be loaded on the same machine. ## Orientation Print this once at the start. Do not repeat it on later steps. ``` Setting up sales.demos on this machine. About 10 minutes, once. 1. Automation Hub token ~/.ansible.cfg 2. Vault password ~/secrets/.vault_pass_sales_demos 3. Pinned collections via /sales-demos-collections-sync 4. Python kubernetes client 4.5 CLI tools oc, terraform, virtctl, helm (+ optional) 5. Run-log directory ~/ansible-logs/ 6. Your environment's values local.yml + set-env-passwords.sh + derived API token Nothing here has to be asked of anyone. Since #130 you create the vault password and the secrets file yourself — step 2, case A. ``` Confirm the working directory first. Everything below assumes the repo root: ```bash test -f playbooks/setup.yml && test -