About rhdh-release-teams
rhdh-release-teams is a read-only skill for answering which teams and leads are associated with an RHDH release and which Jira Cloud IDs identify them. It directs the agent to a specific workflow and distinguishes its scope from release status, announcements, and Jira changes.
Key features
- 01Look up teams and leads
- 02Resolve Jira Cloud IDs
- 03Include lead Slack handles
- 04Read-only team information
- 05Route requests to related skills
Use cases
- 01Find the leads for a release team
- 02Identify a team's Jira Cloud ID
- 03Distinguish team lookup from Jira assignment
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ redhat-developer/ rhdh-skills --skill rhdh-release-teamsAfter installing, type/rhdh-release-teamsin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
agents/openai.yamlscripts/_jira.py_support.pyjql-release.mdjql.pyrelease.pyrich_filter.pyslack_templates.pyslack-templates.mdworkflows/teams-and-leads.mdDetails
From the project READMERHDH teams and leads
Answer who a team is, who leads it, and what identifier Jira knows it by. Read-only.
Route
Load workflows/teams-and-leads.md.
Boundary with the neighbouring skills
- How many issues each team still has open against a release is
/rhdh-release-status, whose per-team breakdown consumes the Cloud IDs this skill resolves. - The freeze message that lists teams and pings their leads is
/rhdh-release-announce. - Assigning work to a person or team, or any Jira write, is
/rhdh-jira-api.
Completion
Complete when each team named in the answer carries its category, leads, Slack handles, and Cloud ID as the source holds them, and the answer says whether the Cloud IDs came from the Rich Filter export or from the spreadsheet column. Say that inactive teams are excluded whenever the full roster was requested. A team the user named that does not appear in the sheet is reported as absent, not matched to the nearest similar name.