New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Jira Natural Language Interface

by jjmartres in jjmartres/opencode

Lets an agent view, create, update and transition Jira issues in natural language, automatically choosing between the jira CLI and Atlassian MCP tools.

MITAuto-check passedProduct & Project Management

Install Jira Natural Language Interface

skills CLI
$ npx skills add jjmartres/opencode --skill jira -a claude-code

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

GitHub CLI
$ gh skill install jjmartres/opencode jira --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/jjmartres/opencode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/opencode/skills/jira .claude/skills/jira && 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
jira
GitHub stars
133
Used in
3 other repos
Token cost
~1.7k tokens
SKILL.md length
628 words
Files
3 (incl. references)
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Lets an agent view, create, update and transition Jira issues in natural language, automatically choosing between the jira CLI and Atlassian MCP tools.

  • Works in 4 steps: Research context if user references… → Draft ticket content → Review with user → …
  • Viewing or searching Jira issues by key or JQL
  • SKILL.md covers Backend Detection, Quick Reference (CLI), Quick Reference (MCP) and Triggers, plus 7 more sections
  • Reaches github.com

What it does

Before doing anything, the skill checks which backend is available, preferring the jira command-line tool when it is on the path and falling back to Atlassian MCP tools when those are exposed instead, with a third path that guides the user to install the CLI if neither is available. A quick-reference table for the CLI backend covers viewing an issue, listing the current user's issues or in-progress issues, creating an issue with a type, summary and description, moving an issue between states, assigning or unassigning it, adding a comment, opening it in a browser, listing the active sprint, and checking who the current user is.

A matching quick-reference table for the MCP backend maps the same intents, searching issues with JQL, viewing, creating and editing an issue, listing and applying transitions, adding a comment, and looking up a user's account id, to specific MCP tool names under an Atlassian namespace. Separate reference files hold the full CLI command syntax and the full MCP tool documentation, read only once the backend is known.

When your agent uses it

  • Viewing or searching Jira issues by key or JQL
  • Creating or updating a Jira issue from a natural-language request
  • Checking sprint status or a backlog
  • Moving an issue through its workflow states or adding a comment

Example prompts

  • “Show me PROJ-123 and its current status.”
  • “Create a bug ticket for the login crash and assign it to me.”
  • “What's in the active sprint right now?”

Requirements

  • The jira CLI, or Atlassian MCP tools, at least one of the two

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Research context if user references code/tickets/PRs
  2. Draft ticket content
  3. Review with user
  4. Create using appropriate backend

What it can do on your machine

Read from SKILL.md and the folder at commit 28dc323. 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

    No scripts in the folder and no shell commands in SKILL.md.

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    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

Jira Natural Language Interface loads about 1.7k tokens when it runs, and up to ~5.9k if it reads all its reference files. Until then it costs about 67 tokens; SKILL.md has 628 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.9k

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 jjmartres/opencode at commit 28dc323, republished under its MIT licence (© jjmartres). 628 words, ~1,730 tokens.

Download SKILL.mdSave it as .claude/skills/jira/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
jira
description
Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.

Jira

Natural language interaction with Jira. Supports multiple backends.

Backend Detection

Run this check first to determine which backend to use:

1. Check if jira CLI is available:
   → Run: which jira
   → If found: USE CLI BACKEND

2. If no CLI, check for Atlassian MCP:
   → Look for mcp__atlassian__* tools
   → If available: USE MCP BACKEND

3. If neither available:
   → GUIDE USER TO SETUP
BackendWhen to UseReference
CLIjira command availablereferences/commands.md
MCPAtlassian MCP tools availablereferences/mcp.md
NoneNeither availableGuide to install CLI

Quick Reference (CLI)

Skip this section if using MCP backend.

IntentCommand
View issuejira issue view ISSUE-KEY
List my issuesjira issue list -a$(jira me)
My in-progressjira issue list -a$(jira me) -s"In Progress"
Create issuejira issue create -tType -s"Summary" -b"Description"
Move/transitionjira issue move ISSUE-KEY "State"
Assign to mejira issue assign ISSUE-KEY $(jira me)
Unassignjira issue assign ISSUE-KEY x
Add commentjira issue comment add ISSUE-KEY -b"Comment text"
Open in browserjira open ISSUE-KEY
Current sprintjira sprint list --state active
Who am Ijira me

Quick Reference (MCP)

Skip this section if using CLI backend.

IntentMCP Tool
Search issuesmcp__atlassian__searchJiraIssuesUsingJql
View issuemcp__atlassian__getJiraIssue
Create issuemcp__atlassian__createJiraIssue
Update issuemcp__atlassian__editJiraIssue
Get transitionsmcp__atlassian__getTransitionsForJiraIssue
Transitionmcp__atlassian__transitionJiraIssue
Add commentmcp__atlassian__addCommentToJiraIssue
User lookupmcp__atlassian__lookupJiraAccountId
List projectsmcp__atlassian__getVisibleJiraProjects

See references/mcp.md for full MCP patterns.

Triggers

  • "create a jira ticket"
  • "show me PROJ-123"
  • "list my tickets"
  • "move ticket to done"
  • "what's in the current sprint"

Issue Key Detection

Issue keys follow the pattern: [A-Z]+-[0-9]+ (e.g., PROJ-123, ABC-1).

When a user mentions an issue key in conversation:

  • CLI: jira issue view KEY or jira open KEY
  • MCP: mcp__atlassian__jira_get_issue with the key

Workflow

Creating tickets:

  1. Research context if user references code/tickets/PRs
  2. Draft ticket content
  3. Review with user
  4. Create using appropriate backend

Updating tickets:

  1. Fetch issue details first
  2. Check status (careful with in-progress tickets)
  3. Show current vs proposed changes
  4. Get approval before updating
  5. Add comment explaining changes

Before Any Operation

Ask yourself:

  1. What's the current state? — Always fetch the issue first. Don't assume status, assignee, or fields are what user thinks they are.

  2. Who else is affected? — Check watchers, linked issues, parent epics. A "simple edit" might notify 10 people.

  3. Is this reversible? — Transitions may have one-way gates. Some workflows require intermediate states. Description edits have no undo.

  4. Do I have the right identifiers? — Issue keys, transition IDs, account IDs. Display names don't work for assignment (MCP).

Show full SKILL.md (256 more words)Show less

NEVER

  • NEVER transition without fetching current status — Workflows may require intermediate states. "To Do" → "Done" might fail silently if "In Progress" is required first.

  • NEVER assign using display name (MCP) — Only account IDs work. Always call lookupJiraAccountId first, or assignment silently fails.

  • NEVER edit description without showing original — Jira has no undo. User must see what they're replacing.

  • NEVER use --no-input without all required fields (CLI) — Fails silently with cryptic errors. Check project's required fields first.

  • NEVER assume transition names are universal — "Done", "Closed", "Complete" vary by project. Always get available transitions first.

  • NEVER bulk-modify without explicit approval — Each ticket change notifies watchers. 10 edits = 10 notification storms.

Safety

  • Always show the command/tool call before running it
  • Always get approval before modifying tickets
  • Preserve original information when editing
  • Verify updates after applying
  • Always surface authentication issues clearly so the user can resolve them

No Backend Available

If neither CLI nor MCP is available, guide the user:

To use Jira, you need one of:

1. **jira CLI** (recommended):
   https://github.com/ankitpokhrel/jira-cli

   Install: brew install ankitpokhrel/jira-cli/jira-cli
   Setup:   jira init

2. **Atlassian MCP**:
   Configure in your MCP settings with Atlassian credentials.

Deep Dive

LOAD reference when:

  • Creating issues with complex fields or multi-line content
  • Building JQL queries beyond simple filters
  • Troubleshooting errors or authentication issues
  • Working with transitions, linking, or sprints

Do NOT load reference for:

  • Simple view/list operations (Quick Reference above is sufficient)
  • Basic status checks (jira issue view KEY)
  • Opening issues in browser
TaskLoad Reference?
View single issueNo
List my ticketsNo
Create with descriptionYes — CLI needs /tmp pattern
Transition issueYes — need transition ID workflow
JQL searchYes — for complex queries
Link issuesYes — MCP limitation, need script

References:

  • CLI patterns: references/commands.md
  • MCP patterns: references/mcp.md

© jjmartres, MIT. 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 (references) in opencode/skills/jira of jjmartres/opencode.

  • SKILL.md
  • references/commands.md
  • references/mcp.md

Open the folder on GitHubat commit 28dc323

Used in 3 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in jjmartres/opencode, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Jira Natural Language Interface 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.

Jira Natural Language Interface compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Jira Natural Language Interface this skilljjmartres/opencode1333 repos~1.7kAutomated safety check: PassMIT
Pm Skillsalirezarezvani/claude-skills28k—~2.6kAutomated safety check: PassMIT
Mps Project ManagementJetBrains/MPS1.7k—~2.2kAutomated safety check: PassApache-2.0
JiraVixenLights/Vixen114—~3.4kAutomated safety check: PassCustom licence
Integration Orchestratorrampstackco/claude-skills945—~5.3kAutomated safety check: PassMIT
Notionkv0906/pm-kit138—~3.5kAutomated safety check: NotesMIT

Similar skills

  • Pm Skills

    alirezarezvani/claude-skills

    A skill your agent uses when coordinating project-delivery work across the 8 project-management sub-skills — sprint/velocity analytics, portfolio health, Jira/JQL, Confluence, Atlassian admin…

    28k GitHub stars~2.6k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed

  • Mps Project Management

    JetBrains/MPS

    Official

    Open an MPS project in a running or freshly started MPS instance when MCP tools fail because no project is open (welcome screen), close an open project with mpsmcpcloseproject, or create a new empty…

    1.7k GitHub stars~2.2k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Jira

    VixenLights/Vixen

    Manages JIRA issues, projects, and workflows using Atlassian MCP.

    114 GitHub stars~3.4k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Integration Orchestrator

    rampstackco/claude-skills

    Generate a phased delivery orchestration plan for creative-direction-driven work: which skills run when, what locks at which gate, how handoffs occur, and how the cadence implements in the team's…

    945 GitHub stars~5.3k tokensUpdated 4 days ago
    Agent WorkflowsAuto-check passed

  • Notion

    kv0906/pm-kit

    Bridge PM-Kit vault with Notion workspace — search, sync, publish, and link vault notes to Notion pages.

    138 GitHub stars~3.5k tokensUpdated 3 mo ago
    Product & Project ManagementAuto-check: notes

  • Ot Cost Analysis

    aiskillstore/marketplace

    Trigger for: Other Transaction or OT should-cost, cost estimate, cost-share analysis, milestone pricing, funding profile, proposed-price comparison, prototype price analysis, research OT budget…

    433 GitHub stars~4.4k tokensUpdated yesterday
    Documents & OfficeAuto-check passed

More from jjmartres/opencode

All 11 skills in this repo

  • Mermaid Diagrams

    jjmartres/opencode

    Helps an agent pick the right Mermaid diagram type and write the syntax for class, sequence, flow, ER, C4, state and other software diagrams.

    133 GitHub starsUsed in 6 repos~1.9k tokens
    Auto-check passed

  • Marp Slide Creator

    jjmartres/opencode

    Builds Marp slide decks in one of seven ready-made themes, using bundled templates plus syntax, image and style references to keep slides short and readable.

    133 GitHub starsUsed in 3 repos~2.2k tokens
    Auto-check passed

  • Google Style Code Docs

    jjmartres/opencode

    Applies Google Style documentation to Python docstrings, Go comments and Terraform descriptions, for writing new docs or reviewing existing ones.

    133 GitHub stars~1.9k tokensUpdated 5 mo ago
    Auto-check passed

  • Worktrunk Git Worktree Manager

    jjmartres/opencode

    Guides use of Worktrunk (wt), a CLI that makes git worktrees as easy as branches so several AI agents can work in parallel on isolated branches.

    133 GitHub stars~1.9k tokensUpdated 5 mo ago
    Auto-check: notes

  • Writing Clearly And Concisely

    jjmartres/opencode

    A skill your agent uses when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text.

    133 GitHub starsUsed in 6 repos~1k tokens
    Auto-check passed

  • Asdf

    jjmartres/opencode

    A skill your agent uses whenever the user wants to install, configure, or use asdf (asdf-vm), the universal version manager.

    133 GitHub stars~2.1k tokensUpdated 5 mo ago
    Auto-check: notes

Works with

Categories

Questions about Jira Natural Language Interface

What does Jira Natural Language Interface do?

Lets an agent view, create, update and transition Jira issues in natural language, automatically choosing between the jira CLI and Atlassian MCP tools. Before doing anything, the skill checks which backend is available, preferring the jira command-line tool when it is on the path and falling back to Atlassian MCP tools when those are exposed instead, with a third path that guides the user to install the CLI if neither is available. A quick-reference table for the CLI backend covers viewing an issue, listing the current user's issues or in-progress issues, creating an issue with a type, summary and description, moving an issue between states, assigning or unassigning it, adding a comment, opening it in a browser, listing the active sprint, and checking who the current user is.

When should I use Jira Natural Language Interface?

Jira Natural Language Interface fits situations like: viewing or searching Jira issues by key or JQL; creating or updating a Jira issue from a natural-language request; checking sprint status or a backlog; moving an issue through its workflow states or adding a comment.

How do I install Jira Natural Language Interface in Claude Code?

Run `npx skills add jjmartres/opencode --skill jira -a claude-code`. Or copy the skill folder (opencode/skills/jira in jjmartres/opencode) into .claude/skills/jira in your project. Claude Code loads it when a task matches its description.

How do I install Jira Natural Language Interface in Codex?

Run `npx skills add jjmartres/opencode --skill jira -a codex`. Or copy the skill folder (opencode/skills/jira in jjmartres/opencode) into .agents/skills/jira in your project. Codex loads it when a task matches its description.

Can I use Jira Natural Language Interface 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 jjmartres/opencode --skill jira -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jira, .gemini/skills/jira, .github/skills/jira and .opencode/skills/jira in your project.

What does Jira Natural Language Interface need to run?

SKILL.md names no scripts, command-line tools or credentials: Jira Natural Language Interface is instructions for the agent only. Our summary lists: The jira CLI, or Atlassian MCP tools, at least one of the two.

Does Jira Natural Language Interface access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Jira Natural Language Interface 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 Jira Natural Language Interface use?

Jira Natural Language Interface is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Jira Natural Language Interface use?

About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.1k tokens, read only when the agent opens those files.

What are the alternatives to Jira Natural Language Interface?

Skills that share tags, products or a category with Jira Natural Language Interface: Pm Skills (alirezarezvani/claude-skills, 28k stars), Mps Project Management (JetBrains/MPS, 1.7k stars), Jira (VixenLights/Vixen, 114 stars) and Integration Orchestrator (rampstackco/claude-skills, 945 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jira Natural Language Interface?

jjmartres (a GitHub user) maintains it in jjmartres/opencode, which has 133 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on April 20, 2026.

Source: jjmartres/opencode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.