Rapidly create disposable provider-neutral HyperShift hosted OpenShift development environments, deploy and test code in verified guests, and clean them up safely. Use when: - "Create a HyperShift hosted cluster / guest" - "Deploy my app into a hosted OpenShift guest" - "Check status of or access a hosted control plane" - "Tear down a HyperShift guest and verify cleanup" - "Install the HyperShift operator" (only when explicitly requested) Provider-neutral lifecycle over aws, kubevirt, agent, azure, gcp, none, openstack, and powervs using the installed hypershift or hcp CLI. NOT for: - ROSA service provisioning (`rosa create cluster`) → separate workflow - Assisted Installer cluster creation → use the cluster-creator skill - Creating the initial management cluster → out of scope
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Use an existing HyperShift installation for the rapid prototype loop: configure,
preflight, create, deploy, test or benchmark, iterate, and destroy. The upstream
hypershift/hcp binary performs provider mechanics; this skill owns environment
discovery, safety checks, orchestration, verification, cost/ownership awareness,
and the evidence-backed report.
Use a private JSON or YAML profile. hcp.py expands ${ENVIRONMENT_VARIABLE}
references without shell evaluation, so shareable profiles do not contain personal
paths, account IDs, domains, or credentials. See profile.example.yaml
(provider-neutral/KubeVirt) and profile.example.aws.yaml
(AWS secret_creds mode), plus rapid-prototyping.md.
Read providers.md for the selected provider and
operations.md for command usage, readiness, deployment,
recovery, and teardown. Research provenance and limits are in research.md.
If the user explicitly requests installing HyperShift, first read
bootstrap.md. Do not bootstrap it implicitly during
ordinary guest creation.
For an explicitly requested operator installation inside a guest, read
guest-operators.md. This is distinct from
installing HyperShift on management.
For building and iterating on local project code in the guest, read
code-workflow.md. The agent and source workspace
remain local; the guest runs the deployed workload.
For mixed worker pools or accelerator workloads, read
accelerators.md. For requested inference measurements,
also read inference-benchmarks.md.
Use when:
Do NOT use when:
rosa create cluster) or the Assisted Installer → use the /cluster-creator skill instead/cluster-inventory or /cluster-report skill insteadHostedCluster, NodePool, and associated
lifecycle resources. Guest credentials deploy and test code. Some providers
also have an infrastructure cluster/account. Keep all three explicit.<hostedcluster-namespace>-<name>. The management cluster cannot remain literally
unchanged. Preserve its existing control plane, shared operators, configuration,
unrelated namespaces, and other guests. Do not install/upgrade HyperShift or patch
ingress, storage defaults, SCCs, or shared RBAC as a hidden workaround for missing
prerequisites. Report the precise prerequisite for the administrator to prepare
separately unless the user has explicitly requested that setup.rosa create cluster, Assisted Installer cluster creation, or a
fake generic HostedCluster template for the chosen HyperShift provider workflow.
HyperShift's Agent provider is infrastructure, distinct from the AI agent.hypershift is the upstream development CLI; hcp exposes a product CLI surface.
Inspect the installed CLI's create cluster <provider> --help and matching version
documentation. Supported providers and flags differ. Do not assume latest upstream
documentation establishes support in the user's release.create cluster ... --render is not a safe planning operation. Provider
completion can create cloud infrastructure/IAM before YAML is emitted. The helper's
plan constructs a command locally without running the CLI. Rendering sensitive
resources produces credentials and is not necessary for this workflow.Discover information from the user's files and read-only tools before asking for it.
Resolve helper paths relative to this skill directory ($SKILL_DIR in examples).
Requires a POSIX host (macOS/Linux), Python 3.10+, PyYAML 6, an oc client compatible
with the target cluster versions, and a compatible hypershift or hcp CLI.
Configured AWS cleanup verification also requires the AWS CLI.
The skill is portable without MCP tools. A connected Kubernetes tool is usable only
if it pins the same target context and keeps credential values out of output.
Collect:
kube-system namespace
UID obtained from that explicit context. Record version/distribution, installed
HyperShift image/version, served CRD versions, compatible guest releases, and
capacity/storage/network/policy constraints. Do not use ambient current-context.node_pools expectations for every pool, including the base
pool. replicas still controls the CLI's initial pool size; it is not the total
expected topology. Additional pools need a separately reviewed creation step.Copy either profile.example.json or the equivalent
profile.example.yaml to a private run directory
(mode 0700), make the profile readable only by you (mode 0600), replace every
example value, and adapt create_args / destroy_args
using provider help and providers.md. For AWS, start from
profile.example.aws.yaml instead, which adds
cloud_identity and the account-specific role ARN. YAML is convenient
for hand editing; JSON remains useful for automation. Use absolute file paths or
${ENVIRONMENT_VARIABLE} references and --long-flag=value tokens; do not put
literal credentials into the profile. For AWS, secret_creds names a Secret in the
management namespace using the native credential keys (aws_access_key_id,
aws_secret_access_key, aws_session_token, baseDomain, pullSecret); the
legacy sts-creds, pull-secret, and base-domain aliases are also accepted.
Add the --role-arn for the account's installing role to both create_args and
destroy_args, as required by current AWS --secret-creds mode. Prefer this
Secret over a workstation AWS credential file.
The helper explicitly selects SingleReplica for both control plane and guest infra,
appropriate for a disposable development environment, without HA guarantees. If HA
is required, adapt that helper policy deliberately before creating anything.
MCP Tool: none — this skill is CLI/script-based (hypershift/hcp, oc, aws) and invokes no MCP tools. Parameters: every hcp.py subcommand takes --profile <profile.json> and a private --state-dir; subcommand flags are documented in operations.md. Error handling: see operations.md for timeout and partial-failure recovery, and never label an unperformed check as passed.
Run plan, inspect preflight, and complete the selected provider's checks.
Preflight proves the target/CRDs/basic RBAC/CLI flags, not release compatibility,
capacity, cloud permissions, DNS reachability, or provider readiness. Record those
separately with evidence. Never label unperformed checks as passed.
Present a concise concrete plan: management identity, guest name/namespace,
provider/region, release, worker resources, SingleReplica tradeoff, expected
management/provider changes, reused resources, cleanup ownership, and cost scope.
Execute create --execute within the user's authorized scope.
Observe the actual command/session and cluster state. Use bounded wait or
status; do not treat CLI success, kubeconfig publication, or Available=True
alone as an application-ready cluster. Check current-generation availability,
guest /readyz, Ready workers in each requested pool, advertised accelerator
resources, guest ClusterVersion, and ClusterOperator conditions.
Do not restart a launch merely because observation timed out.
Run access to retrieve the Secret referenced by status.kubeconfig.name into a
private guest-only file. It checks TLS, the published guest API host/port, and a
guest kube-system UID different from management; the saved HC/guest UIDs detect
replacement. Never print kubeconfigs, passwords, Secret bodies, or credential logs.
When code deployment is requested, build/test the code, publish an image somewhere
guest workers can pull if that action is authorized, then render manifests or
the Helm/Kustomize output locally. Review namespaces, resources/probes, arbitrary
UID compatibility, image references, and the guest's admission policy. Run deploy
for discovery and server validation, then deploy --execute for the requested
apply. It allows namespaced resources in a dedicated guest namespace. Cluster-wide
CRDs/operators/RBAC need a separate reviewed guest plan with the same identity
checks; follow guest-operators.md for an OLM installation. Do not widen the
helper to silently admit platform changes.
Verify rollout and an application-specific smoke test through the guest's explicit kubeconfig and pinned context. A successful apply is not proof the application works.
If teardown was requested, record and review inventory before deletion; see
teardown.md for ownership, storage, AWS configuration,
verification and timeout recovery. Execute destroy --execute only for the
authorized guest. verify-cleanup must confirm API and supported cloud cleanup;
a successful destroy CLI exit is not sufficient. Never delete the shared lifecycle
namespace, management cluster, operator, shared IAM/VPC/DNS, or finalizers by default.
Use operations.md for timeout and partial-failure recovery. After a create attempt,
reconcile existing provider resources before any retry. The local attempt receipt
intentionally blocks automatic reruns. Do not clear it to make a failing check pass.
State the actual outcome: planned, submitted, reconciling, guest ready, application verified, or cleanup verified. Include the provider and cluster identities, private kubeconfig path, tested code/image, rollout/smoke-test results, unresolved conditions, cleanup ownership, and next action. Distinguish offline/fake-CLI checks from actual cluster tests. Never claim all providers work based on one provider's test.
None — this skill is CLI/script-based and uses no MCP server.
None — the skill drives the hypershift/hcp, oc, and aws CLIs via Bash and local helper scripts.
oc — management and guest cluster API access.hypershift or hcp — hosted cluster lifecycle (create/destroy). Inspect the installed create cluster <provider> --help; supported providers and flags vary by version.aws — read-only AWS inventory and cleanup verification (AWS provider teardown only).hcp.py — profile-driven lifecycle: plan, preflight, create, status, wait, access, verify-guest, deploy, inventory, verify-cleanup. Previews are local; mutations require --execute.cleanup.py — read-only AWS ownership/preservation inventory used by teardown verification.make_profile.py — build a validated profile.json, resolving the management kubeconfig from HYPERSHIFT_CONFIG (or, with confirmation, KUBECONFIG) and deriving context + kube_system_uid from the cluster.KUBECONFIG / HYPERSHIFT_CONFIG — management kubeconfig resolution for make_profile.py (the skill itself uses the explicit path pinned in the profile, never an ambient context)./cluster-creator — Assisted Installer cluster creation (distinct provisioning model)./cluster-inventory — list and inspect existing clusters.RHEcosystemAppEng/agentic-plugins
89ba231
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.