CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hypershift-cluster

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

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered operational skill: safety-critical boundaries, a validated multi-step workflow with verification at every destructive stage, and an exemplary progressive-disclosure structure verified against a real one-level-deep bundle. The main gaps are the absence of any literal copy-paste invocation in the body and minor repetition across sections.

Suggestions

Include one complete example invocation in the body (e.g., `python $SKILL_DIR/scripts/hcp.py create --execute --profile <run>/profile.json --state-dir <run>/state`) so the most common command is copy-paste ready without opening operations.md.

De-duplicate repeated admonitions such as "Never label unperformed checks as passed" (Workflow preamble and Step 1) and consolidate the AWS secret_creds key/alias enumeration into providers.md or operations.md, keeping only the pointer in the body.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious domain constraints (management/guest/infrastructure credential separation, "--render is not a safe planning operation", SingleReplica policy, attempt-receipt blocking) and never explains concepts Claude already knows. Minor trimmable material remains: "Never label unperformed checks as passed" appears in both the Workflow preamble and Step 1, and a few long prose passages (e.g., the AWS secret_creds key/alias enumeration) could be tightened. Not 5 because of this repetition and padding; not 3 because nearly all content is skill-specific knowledge Claude cannot infer.

4 / 5

Actionability

Concrete guidance throughout: named helper subcommands (plan, preflight, create --execute, access, deploy --execute, inventory, verify-cleanup, destroy --execute), script paths, profile file modes (0700/0600), and specific flags (--role-arn, SingleReplica). Not 5 because no literal copy-paste invocation line (e.g., `python $SKILL_DIR/scripts/hcp.py create --execute --profile ...`) appears in the body — exact syntax is deferred to operations.md — leaving a minor gap for the most common case. Not 3: the guidance is executable in substance, not pseudocode or vague direction.

4 / 5

Workflow Clarity

The 7-step workflow (plan/preflight → present plan & create → observe readiness → access → deploy → verify → teardown) is clearly sequenced with explicit validation checkpoints at every risky stage: preflight scope limits, readiness evidence beyond Available=True, guest UID checks, smoke tests, and inventory review plus verify-cleanup before/after destroy. Feedback loops are present ("reconcile existing provider resources before any retry", timeout/partial-failure recovery in operations.md, "do not clear the receipt to make a failing check pass"). This matches the anchor-5 pattern including for the destructive teardown path.

5 / 5

Progressive Disclosure

Verified against the actual bundle: all 10 references/, 4 assets/, and 3 scripts/ files cited in the body exist, and reference-file cross-links (operations.md → teardown.md/bootstrap.md, accelerators.md → guest-operators.md) are sibling-level, one level deep with no nested chains. Each reference is signaled twice with purpose and a conditional read trigger (bootstrap.md only when installation is explicitly requested, accelerators.md for mixed pools, inference-benchmarks.md for measurements). Not 4: content split is appropriate for a complex lifecycle skill and navigation is unambiguous despite the long overview.

5 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete lifecycle actions, verbatim natural-language triggers, explicit when/not-for boundaries, and correct third-person imperative voice. It both maximizes discoverability and minimizes mis-triggering against closely related cluster-provisioning skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete lifecycle actions — "Rapidly create disposable provider-neutral HyperShift hosted OpenShift development environments", "deploy and test code in verified guests", and "clean them up safely" — giving comprehensive create/deploy/test/teardown coverage of the skill's scope.

5 / 5

Completeness

It explicitly answers both what (create/deploy/test/cleanup of hosted OpenShift dev environments) and when (a dedicated "Use when:" list of concrete trigger phrases), and goes further with a "NOT for" boundary list. This clearly matches the anchor-5 example structure.

5 / 5

Trigger Term Quality

Natural trigger phrases users would actually say are quoted verbatim ("Create a HyperShift hosted cluster / guest", "Deploy my app into a hosted OpenShift guest", "Tear down a HyperShift guest and verify cleanup") plus synonyms (hosted cluster, guest, hosted control plane) and tool names (hypershift, hcp). Not below 5: no common variation of the request is missing.

5 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (HyperShift hosted clusters on an existing management cluster) and actively routes adjacent requests away — ROSA provisioning, Assisted Installer ("use the cluster-creator skill"), and management-cluster creation are all excluded — so conflict risk with sibling cluster skills is minimal.

5 / 5

Total

20

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

RHEcosystemAppEng/agentic-plugins

Path

ocp-admin/skills/hypershift-cluster/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.