Management Talk
thananon/9arm-skills
Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA…
Add a Component Readiness triage record link to a JIRA issue description
$ npx skills add openshift-eng/ai-helpers --skill add-jira-triage-link -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openshift-eng/ai-helpers add-jira-triage-link --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ci/skills/add-jira-triage-link .claude/skills/add-jira-triage-link && rm -rf skills-srcUse ~/.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/
Install the "add-jira-triage-link" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/add-jira-triage-link into .claude/skills/add-jira-triage-link/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-jira-triage-link", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/add-jira-triage-linkType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add openshift-eng/ai-helpers --skill add-jira-triage-link -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openshift-eng/ai-helpers add-jira-triage-link --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ci/skills/add-jira-triage-link .agents/skills/add-jira-triage-link && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "add-jira-triage-link" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/add-jira-triage-link into .agents/skills/add-jira-triage-link/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-jira-triage-link", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift-eng/ai-helpers --skill add-jira-triage-link -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openshift-eng/ai-helpers add-jira-triage-link --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ci/skills/add-jira-triage-link .cursor/skills/add-jira-triage-link && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "add-jira-triage-link" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/add-jira-triage-link into .cursor/skills/add-jira-triage-link/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-jira-triage-link", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/openshift-eng/ai-helpers.git --path plugins/ci/skills/add-jira-triage-link--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add openshift-eng/ai-helpers --skill add-jira-triage-link -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openshift-eng/ai-helpers add-jira-triage-link --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ci/skills/add-jira-triage-link .gemini/skills/add-jira-triage-link && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "add-jira-triage-link" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/add-jira-triage-link into .gemini/skills/add-jira-triage-link/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-jira-triage-link", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install openshift-eng/ai-helpers add-jira-triage-linkInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add openshift-eng/ai-helpers --skill add-jira-triage-link -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ci/skills/add-jira-triage-link .github/skills/add-jira-triage-link && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "add-jira-triage-link" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/add-jira-triage-link into .github/skills/add-jira-triage-link/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-jira-triage-link", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add openshift-eng/ai-helpers --skill add-jira-triage-link -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openshift-eng/ai-helpers add-jira-triage-link --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ci/skills/add-jira-triage-link .opencode/skills/add-jira-triage-link && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "add-jira-triage-link" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/add-jira-triage-link into .opencode/skills/add-jira-triage-link/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-jira-triage-link", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
add-jira-triage-linkAdd a Component Readiness triage record link to a JIRA issue description
Add Jira Triage Link is an agent skill from openshift-eng/ai-helpers. Add a Component Readiness triage record link to a JIRA issue description
Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `add_jira_triage_link.py`).
It works with Jira. The repository describes itself as: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.
2 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit a627176. It shows what the files ask for, not the result of running them.
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.
Ships script files (Python), which the agent can run.
Shell commands in SKILL.md call:
python3jqFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
sippy-auth.dptools.openshift.orgFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
JIRA_API_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Add Jira Triage Link loads about 684 tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 218 words of instructions outside code blocks.
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.
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.
The full file from openshift-eng/ai-helpers at commit a627176, republished under its Apache-2.0 licence (© openshift-eng). 218 words, ~684 tokens.
.claude/skills/add-jira-triage-link/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.This skill adds a Component Readiness triage record link to a JIRA issue description so that anyone viewing the bug can monitor the on-going status of all regressions triaged to it.
Use this skill after creating or updating a triage record via the triage-regression skill. The link gives bug viewers a way to see all regressions associated with the bug in Component Readiness.
script_path="plugins/ci/skills/add-jira-triage-link/add_jira_triage_link.py"
python3 "$script_path" OCPBUGS-12345 \
--triage-id 456 \
--format jsonArguments:
issue_key: JIRA issue key (e.g., OCPBUGS-12345)Required Options:
--triage-id <id>: Triage record ID from Component ReadinessOptions:
--format json|text: Output format (default: text)output=$(python3 "$script_path" OCPBUGS-12345 --triage-id 456 --format json)
success=$(echo "$output" | jq -r '.success')
if [ "$success" = "true" ]; then
already=$(echo "$output" | jq -r '.already_present')
if [ "$already" = "true" ]; then
echo "Triage link already in description"
else
echo "Triage link added"
fi
fiSuccess (link added):
{
"success": true,
"issue_key": "OCPBUGS-12345",
"triage_url": "https://sippy-auth.dptools.openshift.org/sippy-ng/component_readiness/triages/456",
"already_present": false
}Success (link already present):
{
"success": true,
"issue_key": "OCPBUGS-12345",
"triage_url": "https://sippy-auth.dptools.openshift.org/sippy-ng/component_readiness/triages/456",
"already_present": true
}Error:
{
"success": false,
"error": "Failed to update description: HTTP 403: ...",
"issue_key": "OCPBUGS-12345"
}triage-regression (creates triage records that produce the triage ID)set-release-blocker (similar pattern for updating JIRA issue fields)/ci:analyze-regression (calls this skill after triaging)© 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
SKILL.md and 1 other file in plugins/ci/skills/add-jira-triage-link of openshift-eng/ai-helpers.
Open the folder on GitHubat commit a627176
Add Jira Triage Link 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Add Jira Triage Link this skillopenshift-eng/ai-helpers | 120 | — | ~684 | Automated safety check: Pass | Apache-2.0 | |
| Management Talkthananon/9arm-skills | 3.2k | — | ~3.2k | Automated safety check: Pass | None | |
| YugabyteDB Issue Creatoryugabyte/yugabyte-db | 11k | — | ~2k | Automated safety check: Pass | Custom licence | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Code Reviewcroffasia/itsaplan | 926 | — | ~2k | Automated safety check: Pass | AGPL-3.0 | |
| Connect Apps with ComposioComposioHQ/awesome-claude-skills | 77k | 3 repos | ~557 | Automated safety check: Pass | None |
thananon/9arm-skills
Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA…
yugabyte/yugabyte-db
Creates a GitHub issue or JIRA ticket for a YugabyteDB change or bug, after scrubbing customer data, secrets and unreleased details from anything public.
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
croffasia/itsaplan
A skill your agent uses when reviewing code — a diff, a merge request, a file, a directory, or a feature.
ComposioHQ/awesome-claude-skills
Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.
SAP/spartacus
A skill your agent uses when the user asks to generate, write, or draft a pull request (PR) body or description for the current branch.
openshift-eng/ai-helpers
Find and independently validate actionable reliability defects across OpenShift release jobs and presubmits, then export portable issue handoffs.
openshift-eng/ai-helpers
Fetch and address all PR review comments — categorize by priority, make code changes, post replies, and push.
openshift-eng/ai-helpers
Categorize Jira issues into Red Hat Sankey Activity Type categories using MCP Jira tools.
openshift-eng/ai-helpers
Decide whether a GitHub PR has unanswered authorized review comments or new required CI failures worth a follow-up agent.
openshift-eng/ai-helpers
Analyze OpenShift must-gather diagnostic data including cluster operators, pods, nodes, and network components.
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
Works with
Add a Component Readiness triage record link to a JIRA issue description. Add Jira Triage Link is an agent skill from openshift-eng/ai-helpers.
Run `npx skills add openshift-eng/ai-helpers --skill add-jira-triage-link -a claude-code`. Or copy the skill folder (plugins/ci/skills/add-jira-triage-link in openshift-eng/ai-helpers) into .claude/skills/add-jira-triage-link in your project. Claude Code loads it when a task matches its description.
Run `npx skills add openshift-eng/ai-helpers --skill add-jira-triage-link -a codex`. Or copy the skill folder (plugins/ci/skills/add-jira-triage-link in openshift-eng/ai-helpers) into .agents/skills/add-jira-triage-link in your project. Codex loads it when a task matches its description.
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 add-jira-triage-link -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-jira-triage-link, .gemini/skills/add-jira-triage-link, .github/skills/add-jira-triage-link and .opencode/skills/add-jira-triage-link in your project.
Going by SKILL.md and its folder, Add Jira Triage Link needs Python for the scripts in its folder, the command-line tools its instructions call (python3 and jq) and credentials named JIRA_API_TOKEN. Our summary lists: Python 3; A credential in JIRA_API_TOKEN.
SKILL.md names 1 domain. In commands or code: sippy-auth.dptools.openshift.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
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.
Add Jira Triage Link 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.
About 684 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Add Jira Triage Link: Management Talk (thananon/9arm-skills, 3.2k stars), YugabyteDB Issue Creator (yugabyte/yugabyte-db, 11k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars) and Code Review (croffasia/itsaplan, 926 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.