ericcames
UserSales demo automation as code — each demo runnable as a Claude Code skill or an AAP job template
Categories
Indexed Skills (23)
ocpvirt-demo
Re-run the demo content on Linux or Windows VMs that ALREADY EXIST: register or patch them, install and configure the web server, rescan for CIS compliance, and turn the demo URL from a 503 into a real page. Launches the Linux Day 1 - Repair or Windows Day 1 - Repair job template in AAP, whichever the VM is. TRIGGER when: the user asks to re-run, repair or reconfigure the demo content, says the demo URL returns 503 or does not load, wants a page tweak applied, or is recovering from a failed step on a VM that is still up. SKIP: if no VMs exist yet — a build from nothing is the Linux Day 1 - 0 Workflow or Windows Day 1 - 0 Workflow, reached through ocpvirt-provision — or if the environment itself has never been set up, which is ocpvirt-setup.
ocpvirt-new-env
Verify a fresh RHDP environment is genuinely demo-ready before anyone watches — boot sources actually imported, storage on the fast clone path, ingress admitting Routes — then build one real VM, time it, and destroy it. Runs playbooks/prepare_env.yml. TRIGGER when: the user has a new or rebuilt RHDP environment, asks whether an environment is ready or warm, says VM creation is slow, or is about to demo on a cluster nobody has built a VM on yet. SKIP: if OpenShift Virtualization is not installed at all — that is Phase 0, ocpvirt-setup — or if the user wants to provision demo VMs to keep, which is ocpvirt-provision.
ocpvirt-provision
Phase 3 — build demo VMs on OpenShift Virtualization with Terraform and register them as managed hosts in AAP, ready for the daily-demo content to run against. Runs playbooks/provision_vm.yml. TRIGGER when: the user asks to provision, create, build or spin up demo VMs, wants a Linux or Windows VM for a demo, or asks for a specific size tier. SKIP: if the environment has never been set up — that is ocpvirt-setup — or if the user wants to destroy VMs, which is ocpvirt-teardown.
ocpvirt-rhel9-image
Point this environment's OpenShift Virtualization at the published CIS L1 hardened RHEL 9 golden containerdisk. Creates a DataImportCron that populates the rhel9-cis-l1 DataSource alongside the stock rhel9, so Terraform clones the hardened image by default. No pull secret needed — the quay repo is public. Fully reversible. Runs playbooks/link_rhel9_image.yml. TRIGGER when: the user asks to enable or update the hardened RHEL 9 image, wants to repoint to a new RHEL 9 golden image tag, says VMs are booting the stock RHEL 9 cloud image instead of the hardened one, asks about the rhel9-cis-l1 DataSource, or asks about issue #202. SKIP: if the user wants the WINDOWS golden image — that is ocpvirt-windows-image — or wants to BUILD the golden image, which is ericcames/image.builder.pipeline.
ocpvirt-setup
Phase 0 of the sales.demos OpenShift Virtualization demo — take a bare RHDP environment to demo-ready in one command: install OpenShift Virtualization, apply the AAP configuration, then prove it by building and timing a real VM. Checks prerequisites, confirms the cluster is reachable, then runs playbooks/setup.yml. TRIGGER when: the user has a new or rebuilt RHDP environment, asks to set one up or prepare it for the ocpvirt demo, says OpenShift Virtualization or KubeVirt is missing, hits a missing kubevirt.io API, or asks to install CNV. SKIP: if the environment is already set up and the user wants to create demo VMs — that is ocpvirt-provision — or only wants to re-check readiness, which is ocpvirt-new-env.
ocpvirt-teardown
Destroy the demo VMs on OpenShift Virtualization and deregister them from AAP, leaving the expensive one-time setup intact — CNV, the boot-source DataSources including the Windows golden image, and the Terraform state namespace. Runs playbooks/teardown.yml. TRIGGER when: the user asks to tear down, destroy, clean up, or remove demo VMs, wants to free cluster memory before provisioning a different tier, or says a demo is finished. SKIP: if the user wants to remove OpenShift Virtualization itself or rebuild the golden image — this deliberately preserves both — or only wants to stop a VM rather than destroy it.
ocpvirt-windows-image
Point this environment's OpenShift Virtualization at the published CIS L1 hardened Windows golden containerdisk. Required on a new environment before os_type=windows will boot — CNV ships win2k22 as an empty placeholder. Adds a DataImportCron to the HyperConverged CR and a pull secret for the private quay repository, then asks the cluster whether the DataSource really came up. Fully reversible. Runs playbooks/link_windows_image.yml. TRIGGER when: the user asks to enable or fix Windows VMs, says a Windows VM will not boot or sits forever in Provisioning, asks why win2k22 is not Ready, wants the Windows boot source populated, asks about issue #3, or wants to undo that link. SKIP: if the user wants to BUILD or publish the golden image itself — that is ericcames/image.builder.pipeline, a separate producer — or wants to provision demo VMs generally, which is ocpvirt-provision.
pah-link-aap
Point this environment's AAP project syncs at its own Private Automation Hub, so collections resolve from the curated `approved` repository instead of the internet. Mints a read-scoped gateway token from credentials the environment already holds, creates the Galaxy credential, assigns it to the organization, and proves it with a real project sync. Fully reversible. TRIGGER when: the user asks to point AAP at PAH, wants project syncs to resolve from the hub, asks why a populated hub is not being used, wants organization Galaxy credentials, asks about issue #69, or wants to undo that link. SKIP: if the hub is empty or has not been populated and curated yet — that is pah-sync — or if the user wants to mirror the execution environment image, which is sales-demos-ee-build.
pah-sync
Populate this environment's Private Automation Hub as code — all Red Hat certified and validated collections windowed to their 3 newest versions, plus the ericcames and mlowcher61 community namespaces at their current version only. Regenerates the pinned lists from upstream, runs playbooks/sync_hub.yml, then asks the hub what actually landed. TRIGGER when: the user asks to populate, sync, fill or refresh Private Automation Hub or PAH, wants certified or validated collections in their hub, asks why a hub is empty or a collection is missing from it, wants to refresh hub/*-requirements.yml, or hits a hub sync that reports success with no content. SKIP: if the user wants to point AAP projects AT the hub via organization Galaxy credentials — that is pah-link-aap — or wants to mirror the execution environment image, which is sales-demos-ee-build.
sales-demos-alloy
Deploy Grafana Alloy on an OpenShift cluster to push metrics and logs to Grafana Cloud. Runs playbooks/deploy_alloy.yml. TRIGGER when: the user wants to deploy Alloy, set up Grafana Cloud observability, push metrics/logs to Grafana, or instrument a cluster. SKIP: if the user only wants to query Grafana Cloud (that is the MCP server from /sales-demos-mcp) or configure dashboards (Phase 2/3).
sales-demos-collections-sync
Pin, install, and verify the Ansible collections this repo depends on. Writes exact versions into collections/requirements.yml, installs them to the recommended path (~/.ansible/collections), then checks that what is installed matches what is pinned and fails loudly on drift. TRIGGER when: the user asks to install or update collections, add a collection to the repo, pin or bump a collection version, or when a playbook fails with 'couldn't resolve module/action' or a collection-version error. SKIP: if the user is adding a Python package rather than an Ansible collection, or only wants to run the CI lint gate.
sales-demos-config
Apply AAP config-as-code to an environment — credential types, credentials, job templates, schedules, execution environments, gateway settings, and hub remotes. Syncs the SCM project first so newly added playbooks are visible to template creation. Runs playbooks/config.yml. TRIGGER when: the user asks to push, apply, or refresh AAP configuration, says a job template is missing or wrong, wants to update gateway settings or branding, asks about config-as-code, asks why a newly added playbook is 'not found for project', or has merged a change and needs AAP to pick it up (Step 2 of /sales-demos-dev-workflow). SKIP: if the user wants to validate without changing anything — run validate.yml --check first (this skill covers that) — or wants to set up OpenShift Virtualization, which is ocpvirt-setup.
sales-demos-dashboard
Push Grafana Cloud dashboards (dashboard-as-code). Runs playbooks/deploy_dashboard.yml. TRIGGER when: the user wants to push, deploy, or update the Grafana dashboard, apply dashboard-as-code, or set up the cluster health dashboard. SKIP: if the user only wants to query Grafana Cloud (that is the MCP server from /sales-demos-mcp) or deploy Alloy (that is /sales-demos-alloy).
sales-demos-dev-workflow
The end-to-end development and testing cycle for this repo — branch, PR, merge, then config.yml to push AAP config, then launch the Linux Day 1 - 0 Workflow to prove the change works from AAP. TRIGGER when: the user asks how to test a change, wants to push code to AAP, asks about the dev process, says 'how do we work in this repo', or is about to launch individual job templates after a merge instead of the workflow. SKIP: if the user wants first-time machine setup — that is sales-demos-first-time — or EE verification specifically, which is sales-demos-verify-ee.
sales-demos-ee-build
Build, verify, and publish the custom execution environment this repo's AAP job templates run on — the image that carries the terraform CLI plus the pinned collections. Wraps utilities/build-ee.sh, then registers the new tag in AAP config-as-code. TRIGGER when: the user asks to build, rebuild, bump, or publish the EE, add a collection to the EE, change the terraform version, re-pin the base image, or hits EE errors (ImagePullBackOff on a job template, 'terraform: command not found' in a job, 'couldn't resolve module/action' at runtime but not locally, or an ansible-builder assemble failure). SKIP: if the user only wants collections installed on their laptop — that is sales-demos-collections-sync — or is registering an EE that already exists in quay.
sales-demos-first-time
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, and the run-log directory — 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 run a phase — that is ocpvirt-setup.
sales-demos-mcp
Connect Claude Code to this repo's OpenShift clusters, AAP instances, Automation Orchestrator, and Grafana Cloud over MCP — up to eight servers, one skill. Generates per-environment kubeconfigs for OpenShift, auto-creates bearer tokens for AAP, registers the AO and Grafana Cloud MCP servers, then verifies every server answers. TRIGGER when: the user asks to set up, connect, refresh or fix the MCP servers, says an openshift-sandbox, openshift-demo, openshift-edge, aap-sandbox, aap-demo, ao-sandbox, ao-demo, or grafana MCP server is failing or shows no tools, or has just repointed an environment or rotated a token. SKIP: if the user wants to install OpenShift Virtualization or apply AAP configuration — that is ocpvirt-setup — or wants to deploy the AAP MCP server into a cluster, which is playbooks/mcp_server.yml run by ocpvirt-setup.
sales-demos-orchestrator-config
Configure Automation Orchestrator post-install — connect it to AAP via OIDC (SSO login) and an AAP integration (so AO can see job templates, workflows, inventories). Runs playbooks/configure_ao.yml. TRIGGER when: the user asks to configure AO, connect AO to AAP, set up SSO for AO, set up OIDC on AO, asks why AO has no integrations, says AO login only shows local accounts, or asks why AO cannot see AAP job templates. SKIP: if AO is not installed (that is sales-demos-orchestrator), or if the user wants to create or edit workflows in AO (that is the AO UI/API directly).
sales-demos-orchestrator
Install Automation Orchestrator and the PostgreSQL it cannot run without, so an environment ends up with a working orchestrator UI rather than a catalog entry. Deploys CloudNativePG, builds the three databases Temporal actually needs, installs the AO operator, creates the instance, and proves the Route serves a page. Runs playbooks/install_ao.yml. TRIGGER when: the user asks to install, deploy or fix Automation Orchestrator or AO, asks why the orchestrator UI is missing or 503s, says ao-temporal-migration is crash-looping, or built an environment with install_ao=false and now wants it. SKIP: if the user wants the AAP self-service portal — that is sales-demos-portal — or wants to install OpenShift Virtualization, which is ocpvirt-setup.
sales-demos-portal
Deploy the AAP self-service portal (Red Hat Developer Hub with the AAP plugin) via Helm chart into an RHDP environment. Runs playbooks/portal.yml, which creates the OAuth application, deploys the chart, and syncs the org list. TRIGGER when: the user wants to deploy the self-service portal, asks about RHDH or Developer Hub, or wants non-admin users to launch templates from a browser. SKIP: if the portal is already deployed and the user wants to use it, or if the user wants to install OpenShift Virtualization — that is ocpvirt-setup.
sales-demos-probe-env
Measure what a cluster actually has — allocatable, what is already requested, what is genuinely free — and emit a recommended available_memory_gb instead of trusting a hardcoded one. Strictly read-only, so it is safe mid-demo. Runs playbooks/probe_env.yml. TRIGGER when: the user asks how much room a cluster has, whether an add-on or another VM will fit, why Terraform refuses a tier, or has moved to a new or resized RHDP environment and the memory budget may be stale. SKIP: if the user is asking whether a VM build would be fast — that is ocpvirt-new-env — or if OpenShift Virtualization is not installed at all, which is ocpvirt-setup.
sales-demos-talk-track
Scaffold a new use-case directory under the sales.demos-docs repo's docs/demos/ from _template/, or verify an existing one: check the five required files are present, discover renderable offline artifacts, run the renderer when applicable, visually inspect the output for broken images, and verify the 'Where the words come from' table has no empty rows and every source file exists. Laptop-only, no playbook. TRIGGER when: the user asks to create, scaffold, or start a new demo talk track or use case, verify or audit an existing talk track's structure or source table, re-render demo assets for the docs, check why a talk-track image looks wrong, or asks about the docs/demos/ conventions. Operates on a sibling checkout of ericcames/sales.demos-docs, not on this repo. SKIP: if the user is writing or editing the talk track prose itself — this skill checks structure and artifacts, not content — or if they only want to run render-demo-assets.py without the surrounding checks.
sales-demos-verify-ee
Run a playbook inside the execution environment AAP actually uses, instead of beside it on the laptop, so a local run verifies the dependency set production runs on. Wraps utilities/run-in-ee.sh (ansible-navigator + podman) and diffs the result against a laptop run. TRIGGER when: the user is about to merge a playbook change, asks to verify or test a playbook properly, asks whether something will work from AAP, hits a job template failure a laptop run will not reproduce, or sees 'couldn't resolve module/action' at runtime but not locally. SKIP: if the user wants to build or publish the EE image itself — that is sales-demos-ee-build — or just wants to run a phase against a cluster, which is that phase's own skill.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.