Agent skill

Get Release Dates

by openshift-eng in openshift-eng/ai-helpers

Fetch OpenShift release dates and metadata from Sippy API. An agent skill from openshift-eng/ai-helpers.

Apache-2.0Auto-check passed

Install Get Release Dates

skills CLI
$ npx skills add openshift-eng/ai-helpers --skill get-release-dates -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install openshift-eng/ai-helpers get-release-dates --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/teams/skills/get-release-dates .claude/skills/get-release-dates && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
get-release-dates
GitHub stars
120
Token cost
~1.6k tokens
SKILL.md length
634 words
Files
3
Skills in repo
118
Repo updated
First seen
Licence
Apache-2.0

At a glance

Fetch OpenShift release dates and metadata from Sippy API. An agent skill from openshift-eng/ai-helpers.

  • Works in 5 steps: Verify Prerequisites → Locate the Script → Run the Script → …
  • SKILL.md covers When to Use This Skill, Prerequisites, Implementation Steps and Error Handling, plus 6 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Get Release Dates is an agent skill from openshift-eng/ai-helpers. Fetch OpenShift release dates and metadata from Sippy API

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `README.md` and `get_release_dates.py`).

It works with Python. The repository describes itself as: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.

Example prompts

  • “/get-release-dates”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Verify Prerequisites
  2. Locate the Script
  3. Run the Script
  4. Process the Output
  5. Use the Information

What it can do on your machine

Read from SKILL.md and the folder at commit a627176. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • sippy.dptools.openshift.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Get Release Dates loads about 1.6k tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 634 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~19
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from openshift-eng/ai-helpers at commit a627176, republished under its Apache-2.0 licence (© openshift-eng). 634 words, ~1,621 tokens.

Download SKILL.mdSave it as .claude/skills/get-release-dates/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
get-release-dates
description
Fetch OpenShift release dates and metadata from Sippy API

Get Release Dates

This skill provides functionality to fetch OpenShift release information including GA dates and development start dates from the Sippy API.

When to Use This Skill

Use this skill when you need to:

  • Get GA (General Availability) date for a specific OpenShift release
  • Find when development started for a release
  • Identify the previous release in the sequence
  • Validate if a release exists in Sippy
  • Determine if a release is in development or has GA'd

Prerequisites

  1. Python 3 Installation

    • Check if installed: which python3
    • Python 3.6 or later is required
    • Comes pre-installed on most systems
  2. Network Access

    • The script requires network access to reach the Sippy API
    • Ensure you can make HTTPS requests to sippy.dptools.openshift.org

Implementation Steps

Step 1: Verify Prerequisites

First, ensure Python 3 is available:

bash
python3 --version

If Python 3 is not installed, guide the user through installation for their platform.

Step 2: Locate the Script

The script is located at:

plugins/teams/skills/get-release-dates/get_release_dates.py
Step 3: Run the Script

Execute the script with the release parameter:

bash
# Get dates for release 4.21
python3 plugins/teams/skills/get-release-dates/get_release_dates.py \
  --release 4.21

# Get dates for release 4.20
python3 plugins/teams/skills/get-release-dates/get_release_dates.py \
  --release 4.20
Step 4: Process the Output

The script outputs JSON data with the following structure:

json
{
  "release": "4.21",
  "found": true,
  "ga": "2026-02-17T00:00:00Z",
  "development_start": "2025-09-02T00:00:00Z",
  "previous_release": "4.20"
}

Field Descriptions:

  • release: The release identifier that was queried
  • found: Boolean indicating if the release exists in Sippy
  • ga: GA (General Availability) date. If null, the release is still in development.
  • development_start: When development started for this release
  • previous_release: The previous release in the sequence (empty string if none)

If Release Not Found:

json
{
  "release": "99.99",
  "found": false
}

Release Status - Development vs GA'd:

  • In Development: If ga is null, the release is still under active development
    json
    {
      "release": "4.21",
      "found": true,
      "development_start": "2025-09-02T00:00:00Z",
      "previous_release": "4.20"
    }
  • GA'd (Released): If ga has a timestamp, the release has reached General Availability
    json
    {
      "release": "4.17",
      "found": true,
      "ga": "2024-10-01T00:00:00Z",
      "development_start": "2024-05-17T00:00:00Z",
      "previous_release": "4.16"
    }
Step 5: Use the Information

Based on the release dates:

  1. Determine release status: Check if release is in development or GA'd
    • If ga is null: Release is still in development
    • If ga has a timestamp: Release has reached General Availability
  2. Determine release timeline: Use development_start and ga dates
    • Calculate time in development: ga - development_start
    • For in-development releases: Calculate time since development_start
  3. Find related releases: Use previous_release to navigate the release sequence
  4. Validate release: Check found field before using the release in other operations
Show full SKILL.md (300 more words)Show less

Error Handling

The script handles several error scenarios:

  1. Network Errors: If unable to reach Sippy API

    Error: URL Error: [reason]
  2. HTTP Errors: If API returns an error status

    Error: HTTP Error 404: Not Found
  3. Invalid Release: Script returns exit code 1 with found: false in output

  4. Parsing Errors: If API response is malformed

    Error: Failed to fetch release dates: [details]

Output Format

The script outputs JSON to stdout with:

  • Success: Exit code 0, JSON with found: true
  • Release Not Found: Exit code 1, JSON with found: false
  • Error: Exit code 1, error message to stderr

API Details

The script queries the Sippy releases API:

The full API response includes:

  • releases: Array of all available release identifiers
  • ga_dates: Simple mapping of release to GA date
  • dates: Detailed mapping with GA and development_start dates
  • release_attrs: Extended attributes including previous release

Examples

Example 1: Get Current Development Release
bash
python3 plugins/teams/skills/get-release-dates/get_release_dates.py \
  --release 4.21

Output:

json
{
  "release": "4.21",
  "found": true,
  "development_start": "2025-09-02T00:00:00Z",
  "previous_release": "4.20"
}
Example 2: Get GA'd Release
bash
python3 plugins/teams/skills/get-release-dates/get_release_dates.py \
  --release 4.17

Output:

json
{
  "release": "4.17",
  "found": true,
  "ga": "2024-10-01T00:00:00Z",
  "development_start": "2024-05-17T00:00:00Z",
  "previous_release": "4.16"
}
Example 3: Query Non-Existent Release
bash
python3 plugins/teams/skills/get-release-dates/get_release_dates.py \
  --release 99.99

Output:

json
{
  "release": "99.99",
  "found": false
}

Exit code: 1

Integration with Other Commands

This skill can be used in conjunction with other teams skills:

  1. Before analyzing regressions: Verify the release exists
  2. Timeline context: Understand how long a release has been in development
  3. Release status: Determine if a release is in development or has GA'd
  4. Release navigation: Find previous/next releases in the sequence

Notes

  • The script uses Python's standard library only (no external dependencies)
  • API responses are cached by Sippy, so repeated calls are fast
  • Release identifiers are case-sensitive (use "4.21" not "4.21.0")
  • OKD releases are suffixed with "-okd" (e.g., "4.21-okd")
  • ARO releases have special identifiers (e.g., "aro-production")
  • "Presubmits" is a special release for pull request data

See Also

© openshift-eng, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files in plugins/teams/skills/get-release-dates of openshift-eng/ai-helpers.

  • SKILL.md
  • README.md
  • get_release_dates.py

Open the folder on GitHubat commit a627176

Compare with similar skills

Get Release Dates next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Get Release Dates compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Get Release Dates this skillopenshift-eng/ai-helpers120—~1.6kAutomated safety check: PassApache-2.0
MCP Server Builderanthropics/skills180k62 repos~2.3kAutomated safety check: PassApache-2.0
PDF Processinganthropics/skills180k48 repos~2kAutomated safety check: PassProprietary
NotebookLM Research AssistantPleasePrompto/notebooklm-skill7.8k13 repos~2.4kAutomated safety check: NotesMIT
Manim Video Productionbrowser-use/video-use28k6 repos~3kAutomated safety check: PassMIT
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 62 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • PDF Processing

    anthropics/skills

    Official

    Handles everyday PDF jobs in Python and on the command line: extract text and tables, merge, split, rotate, watermark, fill forms, encrypt and OCR.

    180k GitHub starsUsed in 48 repos~2k tokens
    Documents & OfficeAuto-check passed
  • NotebookLM Research Assistant

    PleasePrompto/notebooklm-skill

    Lets Claude Code ask questions of your Google NotebookLM notebooks through browser automation and return answers grounded in your uploaded sources.

    7.8k GitHub starsUsed in 13 repos~2.4k tokens
    Knowledge ManagementAuto-check: notes
  • Manim Video Production

    browser-use/video-use

    Produces math and technical explainer videos with Manim Community Edition: concept animations, equation derivations, algorithm walkthroughs and data stories.

    28k GitHub starsUsed in 6 repos~3k tokens
    Media & CreativeAuto-check passed
  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed
  • PPT Master

    hugohe3/ppt-master

    Generates editable PowerPoint decks, rebuilds slides from images, fills .pptx templates and polishes existing presentations through routed workflows.

    58k GitHub starsUsed in 1 repo~2.5k tokens
    Documents & OfficeAuto-check passed

More from openshift-eng/ai-helpers

All 118 skills in this repo
  • Investigate CI Reliability

    openshift-eng/ai-helpers

    Find and independently validate actionable reliability defects across OpenShift release jobs and presubmits, then export portable issue handoffs.

    120 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Address Review PR

    openshift-eng/ai-helpers

    Fetch and address all PR review comments — categorize by priority, make code changes, post replies, and push.

    120 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed
  • Categorize Activity Types

    openshift-eng/ai-helpers

    Categorize Jira issues into Red Hat Sankey Activity Type categories using MCP Jira tools.

    120 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Has Review Work

    openshift-eng/ai-helpers

    Decide whether a GitHub PR has unanswered authorized review comments or new required CI failures worth a follow-up agent.

    120 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed
  • Must Gather Analyzer

    openshift-eng/ai-helpers

    Analyze OpenShift must-gather diagnostic data including cluster operators, pods, nodes, and network components.

    120 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed
  • Payload Autodl JSON

    openshift-eng/ai-helpers

    Schema for the autodl JSON data file produced by payload-analysis for database ingestion — you must use this skill whenever generating the autodl JSON file

    120 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Get Release Dates

What does Get Release Dates do?

Fetch OpenShift release dates and metadata from Sippy API. An agent skill from openshift-eng/ai-helpers. Get Release Dates is an agent skill from openshift-eng/ai-helpers.

How do I install Get Release Dates in Claude Code?

Run `npx skills add openshift-eng/ai-helpers --skill get-release-dates -a claude-code`. Or copy the skill folder (plugins/teams/skills/get-release-dates in openshift-eng/ai-helpers) into .claude/skills/get-release-dates in your project. Claude Code loads it when a task matches its description.

How do I install Get Release Dates in Codex?

Run `npx skills add openshift-eng/ai-helpers --skill get-release-dates -a codex`. Or copy the skill folder (plugins/teams/skills/get-release-dates in openshift-eng/ai-helpers) into .agents/skills/get-release-dates in your project. Codex loads it when a task matches its description.

Can I use Get Release Dates in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openshift-eng/ai-helpers --skill get-release-dates -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/get-release-dates, .gemini/skills/get-release-dates, .github/skills/get-release-dates and .opencode/skills/get-release-dates in your project.

What does Get Release Dates need to run?

Going by SKILL.md and its folder, Get Release Dates needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Get Release Dates access the network?

SKILL.md names 1 domain. As links in the text: sippy.dptools.openshift.org. This is read from the text; nothing was executed.

Is Get Release Dates safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Get Release Dates use?

Get Release Dates is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Get Release Dates use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Get Release Dates?

Skills that share tags, products or a category with Get Release Dates: MCP Server Builder (anthropics/skills, 180k stars), PDF Processing (anthropics/skills, 180k stars), NotebookLM Research Assistant (PleasePrompto/notebooklm-skill, 7.8k stars) and Manim Video Production (browser-use/video-use, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Get Release Dates?

openshift-eng (a GitHub organization) maintains it in openshift-eng/ai-helpers, which has 120 GitHub stars. The repository holds 118 skills in this directory. The repository was last updated on October 6, 2026.

Source: openshift-eng/ai-helpers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.