CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deploy

Create Kubernetes Deployment, Service, and Route resources on OpenShift to deploy and expose an application. Use this skill after /s2i-build to make the built image accessible. Handles port detection, replica configuration, HTTPS route creation, rollout monitoring, and rollback on failure. Triggers on /deploy command when user wants to deploy a container image to OpenShift.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

70%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.

The workflow design is excellent — explicit wait checkpoints, rollout validation, and a well-structured failure-recovery path — and the body is reasonably lean. However, executability is undermined by missing template files, and progressive disclosure is broken by stub reference files that point to other skills, dead template paths, and an unreferenced orphan file.

Suggestions

Add the missing `templates/deployment.yaml.template`, `templates/service.yaml.template`, and `templates/route.yaml.template` files (or inline the manifests), since Steps 3–5 cannot execute without them.

Replace the stub `references/*.md` files, which contain only cross-skill path pointers, with real content so the "mandatory checkpoint behavior" and prerequisites they promise are actually loadable.

Specify the rollout polling mechanism in Step 6 (e.g. which MCP tool or command to check pod readiness) instead of the placeholder "[Poll until ready or timeout after 5 minutes]", and either reference or remove the orphaned `references/selinux-troubleshooting.md`.

DimensionReasoningScore

Conciseness

The body is template-driven with no padding explaining concepts Claude already knows, and every dialog block serves the human-in-the-loop flow. Minor trims exist: the framework-port table appears twice (Step 2 detection list and the "Port Required" fallback), and the identical "If user says yes/no" bullet block is repeated verbatim across Steps 3–5 when one statement would suffice — fitting "efficient; minor instances that could be trimmed" rather than the lean anchor.

4 / 5

Actionability

Process guidance is concrete (named MCP tools `resources_create_or_update` and `pods_log`, substitution variables, specific framework ports), but key executable details are missing: Steps 3–5 rely on `templates/deployment.yaml.template`, `templates/service.yaml.template`, and `templates/route.yaml.template`, none of which exist in the bundle, and no manifest YAML is shown inline. Step 6's "[Poll until ready or timeout after 5 minutes]" gives no concrete polling command or tool. This matches "some concrete guidance but incomplete; missing key details" — the core artifacts the skill applies are simply absent, which is more than the minor gaps of score 4.

3 / 5

Workflow Clarity

The sequence is a clearly ordered 7-step workflow with explicit validation checkpoints ("**WAIT for user confirmation before proceeding**" after every mutating step), rollout monitoring as verification, and a full failure-recovery loop in Step 6a (debug pod, debug network, view logs, rollback, continue waiting). This matches the top anchor: clear sequence with explicit validation, feedback loops for error recovery, and rollback handling.

5 / 5

Progressive Disclosure

In-body structure and reference signaling are good (three clearly labeled one-level references under "Reference Documentation"), but scoring against the actual bundle reveals broken navigation: the referenced `templates/*.yaml.template` files do not exist anywhere; the three referenced `references/*.md` files are 50-byte stubs containing only paths to other skills' files (e.g. `../../validate-environment/references/prerequisites.md`), creating 2+ levels of indirection; and `references/selinux-troubleshooting.md` is an orphan never mentioned in the body. This fits "some structure but could be better organized" — the organization gaps are in the bundle, not the signaling.

3 / 5

Total

15

/

20

Passed

Description

88%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.

A strong description: it states concrete capabilities in third person, gives explicit use-when guidance with two trigger conditions, and scopes itself clearly to OpenShift deployment. The only weaknesses are a few missing natural synonyms and residual overlap risk inherent in the generic verb "deploy".

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Create Kubernetes Deployment, Service, and Route resources on OpenShift", "port detection, replica configuration, HTTPS route creation, rollout monitoring, and rollback on failure" — giving comprehensive coverage of the skill's capabilities. It matches the anchor for multiple specific concrete actions; score 4 would require minor gaps in coverage, but the action list spans creation, exposure, monitoring, and failure handling.

5 / 5

Completeness

Both questions are explicitly answered: the "what" ("Create Kubernetes Deployment, Service, and Route resources on OpenShift to deploy and expose an application") and the "when" with concrete triggers ("Use this skill after /s2i-build" and "Triggers on /deploy command when user wants to deploy a container image to OpenShift"). This matches the anchor for clear, explicit what-and-when with concrete trigger phrases; score 4 would require the "when" to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "deploy", "OpenShift", "Kubernetes", "container image", "Deployment, Service, Route", "/deploy command". It falls short of the comprehensive anchor because common synonyms like "k8s", "roll out", or "expose" are missing, though the core terms users would say are present.

4 / 5

Distinctiveness Conflict Risk

The niche is well-scoped to OpenShift/Kubernetes container deployment with an explicit "/deploy command" trigger, keeping it distinct from the related debug skills it names in the body. However, "deploy" is a broadly common verb, so minor overlap risk with other deployment-oriented skills remains — fitting the "mostly distinct; minor overlap risk" anchor rather than the minimal-conflict anchor.

4 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

RHEcosystemAppEng/agentic-plugins

Path

rh-developer/skills/deploy/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.