sales-demos-bootstraplisted

Full environment bootstrap from a single AAP URL — repoint local.yml, verify vault, run setup.yml (all 12 stages with timing including probe), set up MCP servers, and verify everything. TRIGGER when: user provides a new RHDP environment URL and wants it fully set up, or says "bootstrap", "new environment", "fresh cluster". SKIP: if only one component needs updating — use the specific skill instead.
ericcames/sales.demos · ★ 1 · DevOps & Infrastructure · score 67

Install: claude install-skill ericcames/sales.demos

# sales-demos-bootstrap Takes a single AAP URL and drives every step needed to bring a new RHDP environment from bare to demo-ready, including the post-setup tasks that `setup.yml` cannot do (MCP server registration, cluster probing, settings updates). **This skill orchestrates other skills and playbooks.** It contains no playbook logic of its own — it calls `setup.yml`, invokes [`/sales-demos-mcp`](https://github.com/ericcames/sales.demos/blob/main/.claude/skills/sales-demos-mcp/SKILL.md), runs `probe_env.yml`, and updates gitignored local files. The playbooks do the work; this skill sequences them. ## Quick start A new RHDP environment needs three inputs from its RHDP page: the **AAP URL**, the **AAP admin password**, and the **kubeadmin password**. The passwords go into the vault with `utilities/set-env-passwords.sh`; the URL goes in the prompt. The copy-paste commands live in one place, the [New environment quick start](https://ericcames.github.io/sales.demos-docs/reference/new-environment/#quick-start) — do not duplicate them here. ## When to use this vs the pieces | Situation | Use | |---|---| | Brand new RHDP environment, want everything | **This skill** | | Only AAP config changed (edited group_vars) | [`/sales-demos-config`](https://github.com/ericcames/sales.demos/blob/main/.claude/skills/sales-demos-config/SKILL.md) | | Only the portal needs redeploying | [`/sales-demos-portal`](https://github.com/ericcames/sales.demos/blob/main/.claude/skills/sales-demos-por