CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

helm-deploy

Deploy applications to OpenShift using Helm charts. Use this skill when user wants to deploy with Helm, when a Helm chart is detected in the project, or when /helm-deploy command is invoked. Supports both existing charts and chart creation. Handles chart detection, values customization, install/upgrade operations, and rollback. Requires kubernetes MCP Helm tools.

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

71%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-structured interactive deployment workflow with strong sequencing, explicit human-in-the-loop checkpoints, and concrete tool usage. The main weaknesses are in progressive disclosure — reference files are indirection stubs with no in-bundle content and the chart-creation templates directory is missing — plus a missing error-recovery path for failed deployments.

Suggestions

Resolve the references/*.md stub files (which contain only a relative path to another skill's references) into actual content or working symlinks, so following references/human-in-the-loop.md — marked as mandatory — yields the checkpoint behavior instead of another path.

Include the templates/helm/ directory referenced in Step 3 (Chart.yaml, values.yaml, deployment/service/route templates, _helpers.tpl, NOTES.txt) in the bundle or inline the template contents, since chart creation is a core advertised capability.

Add an error-recovery loop to Step 7: when pods are not ready before timeout, specify what to do next (e.g., inspect pod status and invoke /debug-pod) to close the validate-fix-retry cycle.

DimensionReasoningScore

Conciseness

The body is largely functional — user-facing markdown templates, exact search paths, and quick commands — with almost no explanation of concepts Claude already knows; only minor trimming opportunities remain (e.g., Step 5 duplicates the values in both a YAML block and a table).

4 / 5

Actionability

Guidance is mostly executable — named MCP tools (helm_list, helm_install, pods_list_in_namespace), concrete chart search paths, an explicit list of chart files to generate — but Step 7 invokes helm_upgrade which is not in allowed-tools, and Step 3 points to templates/helm/ files that are not in the bundle.

4 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit 'WAIT for user confirmation' checkpoints and branch handling (chart found/not found, existing release), plus validation via connection check and pod monitoring; however there is no error-recovery loop for when pods fail to become ready before timeout, keeping it below the top anchor.

4 / 5

Progressive Disclosure

The structure and one-level-deep reference linking are good, but measured against the actual bundle all four references/*.md files are ~50-byte path stubs to other skills' directories whose targets are absent, and the templates/helm/ path referenced in Step 3 does not exist — references are signaled but do not resolve to real content.

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 that clearly and explicitly states both capabilities and trigger conditions with concrete, natural trigger phrases. It is specific and comprehensive within its niche; the only weaknesses are a few missing natural keyword variations and slight overlap risk with generic deployment skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'chart detection, values customization, install/upgrade operations, and rollback' plus 'existing charts and chart creation' — giving comprehensive coverage of the Helm deployment domain rather than just a few actions with minor gaps.

5 / 5

Completeness

It explicitly answers both 'what' ('Deploy applications to OpenShift using Helm charts... install/upgrade operations, and rollback') and 'when' with three concrete trigger phrases ('when user wants to deploy with Helm, when a Helm chart is detected in the project, or when /helm-deploy command is invoked'), matching the top anchor.

5 / 5

Trigger Term Quality

Natural phrases like 'deploy with Helm', 'a Helm chart is detected', and '/helm-deploy' give good keyword coverage, but common variations users would say (Kubernetes, helm install/upgrade, Chart.yaml, release) are absent, so it falls just short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The Helm-on-OpenShift niche and Helm-specific triggers make it mostly distinct with only minor overlap risk against a generic deployment skill (the body itself lists /deploy as an alternative), so it fits 'mostly distinct; minor overlap risk' better than 'minimal conflict risk'.

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/helm-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.