CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

red-hat-product-lifecycle

Explain a Red Hat product's lifecycle status, support phases, and recommended action. Answers questions like "Is RHEL 8.6 still supported?" or "When does OpenShift 4.14 reach end of maintenance?"

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./rh-basic/skills/red-hat-product-lifecycle/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 solid, actionable skill body: the script-based lookup workflow is concrete and error-aware, and the embedded Red Hat domain knowledge (backports, support add-ons) is genuinely valuable. The weakest area is token efficiency — boilerplate setup steps and inlined reference data add length without adding guidance value.

Suggestions

Drop the Step 0 "Resolve scripts directory" block and the separate "Dependencies" section; invoke the script directly as `python scripts/rh_lifecycle.py "..."` since the path is fixed relative to the skill.

Move the "Lifecycle Phase Reference" and "Red Hat Versioning & Backports" sections into a references/ file (e.g. references/phases.md) and link to it, keeping SKILL.md as a lean overview.

Add one concrete worked example, such as `python scripts/rh_lifecycle.py "Red Hat Enterprise Linux 9"` with its expected JSON output, and a note to retry with the script's close-match suggestions when a product is not found.

DimensionReasoningScore

Conciseness

The core content (backporting model, EUS/ELS add-ons, phase semantics, output format) is dense, non-obvious domain knowledge, but the Step 0 "Resolve scripts directory" ceremony, the redundant "Dependencies" section, and inlined time-sensitive version lists ("RHEL 8/9/10", "4.12, 4.14, 4.16") are tighten-able padding. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the merely-minor-trims of anchor 4.

3 / 5

Actionability

The workflow gives an executable command (python $SCRIPTS_DIR/rh_lifecycle.py "Product Name Version") backed by a real bundled script whose behavior matches the documented API URL, stdout/stderr split, and exit codes, plus a concrete output schema and per-phase action templates. It stops short of 5 because the invocation uses a placeholder rather than a worked example and no sample end-to-end output is shown.

4 / 5

Workflow Clarity

A clear three-step sequence (identify product/version, run script, format response) with explicit error signaling ("Errors are on stderr (JSON with \"error\" key); exit code 1 on failure") and interpretation rules ("Use today's date from context", "State dates concretely... never relatively"). It is not 5 because there is no recovery loop for product-not-found errors, e.g. retrying with the script's close-match suggestions.

4 / 5

Progressive Disclosure

The body is well-sectioned with one-level-deep navigation, and its single bundle reference (scripts/rh_lifecycle.py) is clearly signaled and verified to exist with matching behavior. It is not 5 because roughly 30 lines of reference-style data (Lifecycle Phase Reference, Versioning & Backports) are inlined in a ~90-line body rather than split into references/ files.

4 / 5

Total

15

/

20

Passed

Description

78%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 and includes genuinely natural example questions that double as triggers. The main improvement would be an explicit "Use when..." clause with broader synonym coverage (EOL, end of life, end of support) to reach top marks on completeness and trigger quality.

DimensionReasoningScore

Specificity

"Explain a Red Hat product's lifecycle status, support phases, and recommended action" names the domain plus three concrete deliverables, matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because "recommended action" is generic and the action list is not comprehensive.

4 / 5

Completeness

The "what" is clear (explain lifecycle status, support phases, recommended action) and a "when" is present via concrete example questions, so the missing-trigger cap of 3 does not apply. It is not 5 because there is no explicit "Use when..." directive and the example questions cover only two of the trigger situations (upgrade-planning and EOL-action queries are uncovered).

4 / 5

Trigger Term Quality

The quoted questions "Is RHEL 8.6 still supported?" and "When does OpenShift 4.14 reach end of maintenance?" are exactly what users would naturally say, alongside "lifecycle" and "support phases". Common synonyms like "EOL", "end of life", and "end of support" are missing, so it fits anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

"Red Hat product's lifecycle status" with named products (RHEL, OpenShift) carves out a clear niche with distinct triggers and minimal conflict risk with any plausible sibling skill. It clearly matches the anchor-5 example's level of niche specificity rather than the 'minor overlap risk' anchor 4.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

RHEcosystemAppEng/agentic-plugins

Path

rh-basic/skills/red-hat-product-lifecycle/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.