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?"
77%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
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.mdIdentify product and version from user message. If unclear, ask. Look up lifecycle data using the script below and respond using the output format.
Step 0 — Resolve scripts directory. Before anything else, locate the helper scripts. They are inside the skill's scripts/ subfolder. Run:
SCRIPTS_DIR="scripts"
test -f "$SCRIPTS_DIR/rh_lifecycle.py" || { echo "Error: Scripts directory not found at $SCRIPTS_DIR"; exit 1; }Use $SCRIPTS_DIR in all subsequent script calls.
Python 3 — the script uses only the stdlib.
When the user asks about lifecycle status, support phases, or EOL dates for any Red Hat product or version.
python $SCRIPTS_DIR/rh_lifecycle.py "Product Name Version"https://access.redhat.com/product-life-cycles/api/v1/products and returns JSON to stdout.
Errors are on stderr (JSON with "error" key); exit code 1 on failure.{
"product": "Red Hat Enterprise Linux",
"version": "9",
"current_phase": "Full Support",
"phases": {
"General availability": { "start": "2022-05-18", "end": "2022-05-18" },
"Full support": { "start": "2022-05-18", "end": "2027-05-31" },
"Maintenance support": { "start": "2027-06-01", "end": "2032-05-31" }
}
}Dates are YYYY-MM-DD; "N/A" means no date; "Ongoing" means open-ended.
Script: $SCRIPTS_DIR/rh_lifecycle.py
RHEL 8/9/10 -- 10-year lifecycle
Add-ons (purchased separately): EUS = 24-month minor release freeze; Enhanced EUS = 48 months; E4S = 48 months for SAP; ELS = post-EOL Critical/Important fixes for RHEL 6/7
OCP 4.x -- 18-month lifecycle per minor
Applies to all Red Hat products (RHEL, OpenShift, Ansible, JBoss, Satellite, etc.).
dnf update within a minor never moves a system to a new major version.name-version-release.elX. The version field tracks the upstream base (e.g., 1.1.1k); the release counter (e.g., -7.el8 -> -8.el8) increments for each backported fix. Same version + higher release = fix applied.Phase: [current phase] Dates: GA [date] | End Full Support [date] | End Maintenance [date] | EOL [date] (include EUS/ELS end if applicable)
What this means: 1-2 sentences on what updates this version currently receives.
Action:
Use today's date from context to determine if support has already ended. State dates concretely ("ends May 31, 2025"), never relatively. If a version has no data, say so and list what versions do. For inventory queries, report per-system phase when possible.
RHEcosystemAppEng/agentic-plugins
df1d156
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.