CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

validate-environment

Check and report the status of required tools and environment for rh-developer skills. Validates tool installation (oc, helm, podman, git, skopeo, etc.), cluster connectivity, and permissions. Use this skill before running other deployment skills to ensure prerequisites are met. Triggers on /validate-environment command or when user asks to check their environment setup.

Quality

83%

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

78%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, highly actionable skill body: concrete bash checks, a defined report format, and proper use of two real, one-level-deep reference files. The main flaw is the undefined TARGET variable used to gate Steps 3 and 4, which introduces minor ambiguity in both actionability and workflow execution.

Suggestions

Define TARGET (or replace it) by explicitly mapping the four scope options from Step 1 to the checks in Steps 2-4 (e.g., 'All → Steps 2, 3, 4; OpenShift → Steps 2, 3; RHEL/Containers → Steps 2, 4; Minimal → core tools only').

Show the invocation of the check_tool function (e.g., a loop over the tool list) so the Step 2 snippet is fully copy-paste executable.

Consolidate the three separate links to references/prerequisites.md into one well-placed reference to trim redundancy.

DimensionReasoningScore

Conciseness

The body is dominated by executable commands and output templates rather than explanation of known concepts, fitting the 'efficient; minor instances that could be trimmed' anchor. Small redundancies — prerequisites.md is linked three times and the Step 5 sample report is fully populated with placeholder data — keep it below the lean-every-token-earns-its-place anchor.

4 / 5

Actionability

Guidance is mostly executable: the check_tool bash function, oc connectivity/permission commands, podman/docker info commands, and a pull test are copy-paste ready, and error sections give concrete remediation commands. Minor gaps — check_tool is defined but never invoked, and TARGET is referenced in Step 3/4 headers without being defined — keep it from a 5.

4 / 5

Workflow Clarity

The six-step sequence is clear with scoping up front, a structured report, and error-recovery sections (login, KUBECONFIG, permission options) that act as feedback loops. It misses a 5 because the conditional steps depend on an undefined TARGET variable, leaving the scope-to-check mapping implicit.

4 / 5

Progressive Disclosure

The body keeps the workflow inline while pushing comprehensive tool requirements and installation instructions to references/prerequisites.md and checkpoint behavior to references/human-in-the-loop.md — both real files, clearly signaled with descriptive links, one level deep. This matches the clear-overview with well-signaled one-level-deep references anchor.

5 / 5

Total

17

/

20

Passed

Description

83%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 explicitly covers what the skill does, when to use it, and how it is triggered, with a specific named toolchain. The only weaknesses are minor: an open-ended "etc." in tool coverage and a slightly generic "check their environment setup" trigger phrase.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Validates tool installation (oc, helm, podman, git, skopeo, etc.), cluster connectivity, and permissions" — with named tools, matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because the trailing "etc." leaves tool coverage open-ended rather than comprehensive.

4 / 5

Completeness

It clearly answers both what ("Check and report the status of required tools... Validates tool installation..., cluster connectivity, and permissions") and when ("Use this skill before running other deployment skills", the /validate-environment command, "when user asks to check their environment setup") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

"Triggers on /validate-environment command or when user asks to check their environment setup" plus the explicit tool names gives good keyword coverage. A few natural terms users might say are missing (e.g., "prerequisites", "verify tools are installed"), keeping it below the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

The specific toolchain (oc, helm, podman, skopeo) and named command give it a mostly distinct niche with only minor overlap risk. The generic phrase "check their environment setup" could still collide with other setup/diagnostic skills, so it does not reach the minimal-conflict anchor.

4 / 5

Total

17

/

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/validate-environment/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.