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…
A skill your agent uses when the user provides a single Jira issue key and asks whether it is still relevant, still applicable, still pending, still a bug, has been fixed, or can be closed.
OfficialCustom licenceAuto-check passed
Install Assessing Jira Issue Relevance
$ npx skills add bitwarden/ai-plugins --skill assessing-jira-issue-relevance -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bitwarden/ai-plugins assessing-jira-issue-relevance --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/bitwarden/ai-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevance .claude/skills/assessing-jira-issue-relevance && 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 "assessing-jira-issue-relevance" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevance into .claude/skills/assessing-jira-issue-relevance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assessing-jira-issue-relevance", 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/bitwarden/ai-plugins/tree/main/plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevanceType 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 bitwarden/ai-plugins --skill assessing-jira-issue-relevance -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bitwarden/ai-plugins assessing-jira-issue-relevance --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevance .agents/skills/assessing-jira-issue-relevance && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "assessing-jira-issue-relevance" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevance into .agents/skills/assessing-jira-issue-relevance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assessing-jira-issue-relevance", 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 bitwarden/ai-plugins --skill assessing-jira-issue-relevance -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bitwarden/ai-plugins assessing-jira-issue-relevance --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevance .cursor/skills/assessing-jira-issue-relevance && 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 "assessing-jira-issue-relevance" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevance into .cursor/skills/assessing-jira-issue-relevance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assessing-jira-issue-relevance", 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/bitwarden/ai-plugins.git --path plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevance--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 bitwarden/ai-plugins --skill assessing-jira-issue-relevance -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bitwarden/ai-plugins assessing-jira-issue-relevance --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevance .gemini/skills/assessing-jira-issue-relevance && 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 "assessing-jira-issue-relevance" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevance into .gemini/skills/assessing-jira-issue-relevance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assessing-jira-issue-relevance", 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 bitwarden/ai-plugins assessing-jira-issue-relevanceInstalls 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 bitwarden/ai-plugins --skill assessing-jira-issue-relevance -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevance .github/skills/assessing-jira-issue-relevance && 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 "assessing-jira-issue-relevance" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevance into .github/skills/assessing-jira-issue-relevance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assessing-jira-issue-relevance", 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 bitwarden/ai-plugins --skill assessing-jira-issue-relevance -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bitwarden/ai-plugins assessing-jira-issue-relevance --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwarden/ai-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevance .opencode/skills/assessing-jira-issue-relevance && 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 "assessing-jira-issue-relevance" agent skill from https://github.com/bitwarden/ai-plugins/tree/main/plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevance into .opencode/skills/assessing-jira-issue-relevance/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assessing-jira-issue-relevance", 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.
Facts
- Skill name
assessing-jira-issue-relevance- GitHub stars
- 155
- Token cost
- ~2.7k tokens
- SKILL.md length
- 1,467 words
- Files
- 2
- Skills in repo
- 35
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when the user provides a single Jira issue key and asks whether it is still relevant, still applicable, still pending, still a bug, has been fixed, or can be closed.
- Works in 5 steps: Fetch the Ticket and Its Context → Establish Repo Scope → Build Search Targets → …
- The user provides a single Jira issue key and asks whether it is still relevant
- SKILL.md covers Workflow, What NOT to Do and Examples
- Calls git
What it does
Assessing Jira Issue Relevance is an agent skill from bitwarden/ai-plugins, published by the product's own GitHub organization. Use when the user provides a single Jira issue key and asks whether it is still relevant, still applicable, still pending, still a bug, has been fixed, or can be closed. Trigger phrases include "Is [TICKET] still relevant?", "Is this still an issue?", "Is PM-123 still pending?", "Has this been fixed?", "Can we close this?", "Is this ticket still valid?", "Is this still applicable?", "Does this bug still exist?". Fetches the ticket and verifies the described problem against the current codebase to return a verdict…
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `examples/relevance_assessment_workflow.md`).
It works with Jira. The repository describes itself as: AI plugin marketplace.
When your agent uses it
- The user provides a single Jira issue key and asks whether it is still relevant
- Still applicable
- Phrases include Is [TICKET] still relevant?
- Is this still an issue?
Example prompts
- “Is [TICKET] still relevant?”
- “Is this still an issue?”
- “Is PM-123 still pending?”
- “/assessing-jira-issue-relevance”
Requirements
- Pre-approved tools (allowed-tools): Read, Grep, Glob, AskUserQuestion, Bash(git log:*), Bash(git -C * log:*), Bash(git -C * rev-parse:*), Bash(git clone:*), mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue_comments, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue_remote_links, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_confluence_page
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Fetch the Ticket and Its Context
- Establish Repo Scope
- Build Search Targets
- Search the Code
- Deliver Verdict
What it can do on your machine
Read from SKILL.md and the folder at commit 0e684b9. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepGlobAskUserQuestionBash(git log:*)Bash(git -C * log:*)Bash(git -C * rev-parse:*)Bash(git clone:*)mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issuemcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue_comments
…and 2 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Assessing Jira Issue Relevance loads about 2.7k tokens when it runs. Until then it costs about 164 tokens; SKILL.md has 1,467 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.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,467 words (~2,723 tokens).
“Determine whether a Jira issue still applies to the current codebase. Fetch the ticket, locate the specific code path it describes, compare current behavior against the ticket's description, and return a verdict with evidence.”
- name
- assessing-jira-issue-relevance
- allowed-tools
- Read, Grep, Glob, AskUserQuestion, Bash(git log:*), Bash(git -C * log:*), Bash(git -C * rev-parse:*), Bash(git clone:*), mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue_comments, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue_remote_links, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_confluence_page
Files
SKILL.md and 1 other file in plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevance of bitwarden/ai-plugins.
- SKILL.md
- examples/relevance_assessment_workflow.md
Open the folder on GitHubat commit 0e684b9
Compare with similar skills
Assessing Jira Issue Relevance 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 |
|---|---|---|---|---|---|---|
| Assessing Jira Issue Relevance this skillbitwarden/ai-plugins | 155 | — | ~2.7k | Automated safety check: Pass | Custom licence | |
| 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 | 920 | — | ~2k | Automated safety check: Pass | AGPL-3.0 | |
| Connect Apps with ComposioComposioHQ/awesome-claude-skills | 77k | 3 repos | ~557 | Automated safety check: Pass | None |
Similar skills
YugabyteDB Issue Creator
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.
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Code Review
croffasia/itsaplan
A skill your agent uses when reviewing code — a diff, a merge request, a file, a directory, or a feature.
Connect Apps with Composio
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.
- Official
PR Body
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.
More from bitwarden/ai-plugins
All 35 skills in this repo- Official
Reading Mailcatcher API
bitwarden/ai-plugins
Retrieves a link from Mailcatcher. An agent skill from bitwarden/ai-plugins.
- Official
Using Stripe CLI
bitwarden/ai-plugins
Query read-only Stripe test-mode data and advance an already-attached test clock.
- Official
Reviewing Claude Config
bitwarden/ai-plugins
Reviews Claude configuration files for security, structure, and prompt engineering quality.
- Official
Managing Workflow Secrets
bitwarden/ai-plugins
Bitwarden's canonical pattern for using a secret inside a GitHub Actions job: authenticate to Azure with the OIDC triad, pull the secret from an Azure Key Vault via the bitwarden/gh-actions…
- Official
Reviewing Security Architecture
bitwarden/ai-plugins
This skill should be used when the user asks to "review the security architecture", "check authentication patterns", "evaluate trust boundaries", "review encryption implementation", "assess…
- Official
Auditing External Claude Plugins
bitwarden/ai-plugins
Audits an external (third-party) Claude Code plugin pinned in this marketplace for security risk before it is vendored, and writes the report to a file for downstream posting.
Related
Works with
Questions about Assessing Jira Issue Relevance
What does Assessing Jira Issue Relevance do?
A skill your agent uses when the user provides a single Jira issue key and asks whether it is still relevant, still applicable, still pending, still a bug, has been fixed, or can be closed. Assessing Jira Issue Relevance is an agent skill from bitwarden/ai-plugins, published by the product's own GitHub organization. Use when the user provides a single Jira issue key and asks whether it is still relevant, still applicable, still pending, still a bug, has been fixed, or can be closed.
When should I use Assessing Jira Issue Relevance?
Assessing Jira Issue Relevance fits situations like: the user provides a single Jira issue key and asks whether it is still relevant; still applicable; phrases include Is [TICKET] still relevant?; is this still an issue?.
How do I install Assessing Jira Issue Relevance in Claude Code?
Run `npx skills add bitwarden/ai-plugins --skill assessing-jira-issue-relevance -a claude-code`. Or copy the skill folder (plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevance in bitwarden/ai-plugins) into .claude/skills/assessing-jira-issue-relevance in your project. Claude Code loads it when a task matches its description.
How do I install Assessing Jira Issue Relevance in Codex?
Run `npx skills add bitwarden/ai-plugins --skill assessing-jira-issue-relevance -a codex`. Or copy the skill folder (plugins/bitwarden-atlassian-tools/skills/assessing-jira-issue-relevance in bitwarden/ai-plugins) into .agents/skills/assessing-jira-issue-relevance in your project. Codex loads it when a task matches its description.
Can I use Assessing Jira Issue Relevance 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 bitwarden/ai-plugins --skill assessing-jira-issue-relevance -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/assessing-jira-issue-relevance, .gemini/skills/assessing-jira-issue-relevance, .github/skills/assessing-jira-issue-relevance and .opencode/skills/assessing-jira-issue-relevance in your project.
What does Assessing Jira Issue Relevance need to run?
Going by SKILL.md and its folder, Assessing Jira Issue Relevance needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Read, Grep, Glob, AskUserQuestion, Bash(git log:*), Bash(git -C * log:*), Bash(git -C * rev-parse:*), Bash(git clone:*), mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue_comments, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue_remote_links, mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_confluence_page.
Does Assessing Jira Issue Relevance access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Assessing Jira Issue Relevance 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 Assessing Jira Issue Relevance use?
Assessing Jira Issue Relevance has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Assessing Jira Issue Relevance use?
About 2.7k tokens (SKILL.md is roughly 11k 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 Assessing Jira Issue Relevance?
Skills that share tags, products or a category with Assessing Jira Issue Relevance: 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, 920 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Assessing Jira Issue Relevance?
bitwarden (a GitHub organization, an official publisher) maintains it in bitwarden/ai-plugins, which has 155 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 9, 2026.
Source: bitwarden/ai-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.