agentleFS
redhat-developerredhat-developer/rhdh-skills/skills/release/rhdh-platform-lifecycle/SKILL.md

rhdh-platform-lifecycle

Skill20 starsChanged 20 days agoApache-2.0View on GitHub

Reports vendor support phases and end-of-life dates for RHDH and the platforms it runs on: OpenShift, ARO, OSD, ROSA, AKS, EKS, GKE, PostgreSQL, Red Hat build of Keycloak, and Quay. Use for "is OCP 4.16 still supported", "when does PostgreSQL 15 go EOL", "which Kubernetes version should AKS be on", "which OCP versions does RHDH 1.10 support", or an RHBK or Quay lifecycle lookup. Product lifecycle only — RHDH milestone dates such as Code Freeze belong to rhdh-release-schedule.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    every endpoint the answer rests on.

    line 40
  2. Distinctive:

    every version the script could not classify, as a warning.

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

RHDH platform support

Produce lifecycle facts without changing repositories or external systems.

Route

QuestionLoadRun
RHDH support and compatible OCP versionsworkflows/check-rhdh.mdscripts/check_rhdh_lifecycle.py
OpenShift support phasesworkflows/check-ocp.mdscripts/check_ocp_lifecycle.py
Azure AKS support and configured versionsworkflows/check-aks.mdscripts/check_aks_lifecycle.py
AWS EKS support and configured versionsworkflows/check-eks.mdscripts/check_eks_lifecycle.py
Google GKE supportworkflows/check-gke.mdscripts/check_gke_lifecycle.py
PostgreSQL supportworkflows/check-pg.mdscripts/check_pg_lifecycle.py
RHBK, Quay, or another Red Hat productworkflows/check-redhat.mdscripts/check_lifecycle.py

Load one workflow. Use the bundled script for deterministic retrieval and classification; add judgment only after its output is available.

What to report

Report, for the product asked about and the date the answer was produced:

  • each version with the support phase and the source date the script returned;
  • versions found only in openshift/release, labelled configured, never supported;
  • the RHDH-to-platform compatibility pairs, where the script emits them;
  • every endpoint the answer rests on;
  • every version the script could not classify, as a warning.

Preserve the script's source dates and uncertainty. Distinguish vendor lifecycle from versions merely configured in openshift/release. Do not infer that a configured version is supported.

Composition

Other skills invoke /rhdh-platform-lifecycle by name and use what it reports. rhdh_lifecycle is a private, local adapter: no other skill imports it or locates this skill on disk, and all repository and YAML access stays behind it.

Completion

Complete when every product and version named in the request carries the support phase and the source date the script returned, the answer names each endpoint it rests on, and every version the script could not classify is reported as a warning rather than dropped or estimated. A version found only in openshift/release is reported as configured and never as supported. If a lifecycle source was unreachable, name the product that remains unassessed instead of returning the partial list as the answer.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.