Agent skill

C Jira

Manage Jira issues using jira (jira-cli). An agent skill from daxaur/openpaw.

MITAuto-check passed

Install C Jira

skills CLI

$ npx skills add daxaur/openpaw --skill c-jira -a claude-code

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

GitHub CLI

$ gh skill install daxaur/openpaw c-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/daxaur/openpaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/c-jira .claude/skills/c-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/

Paste into Claude Code

Install the "c-jira" agent skill from https://github.com/daxaur/openpaw/tree/main/skills/c-jira into .claude/skills/c-jira/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "c-jira", 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

$skill-installer install https://github.com/daxaur/openpaw/tree/main/skills/c-jira

Type 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.

skills CLI

$ npx skills add daxaur/openpaw --skill c-jira -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install daxaur/openpaw c-jira --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/daxaur/openpaw.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/c-jira .agents/skills/c-jira && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "c-jira" agent skill from https://github.com/daxaur/openpaw/tree/main/skills/c-jira into .agents/skills/c-jira/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "c-jira", 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.

skills CLI

$ npx skills add daxaur/openpaw --skill c-jira -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install daxaur/openpaw c-jira --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/daxaur/openpaw.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/c-jira .cursor/skills/c-jira && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "c-jira" agent skill from https://github.com/daxaur/openpaw/tree/main/skills/c-jira into .cursor/skills/c-jira/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "c-jira", 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

$ gemini skills install https://github.com/daxaur/openpaw.git --path skills/c-jira

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add daxaur/openpaw --skill c-jira -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install daxaur/openpaw c-jira --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/daxaur/openpaw.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/c-jira .gemini/skills/c-jira && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "c-jira" agent skill from https://github.com/daxaur/openpaw/tree/main/skills/c-jira into .gemini/skills/c-jira/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "c-jira", 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.

GitHub CLI

$ gh skill install daxaur/openpaw c-jira

Installs 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).

skills CLI

$ npx skills add daxaur/openpaw --skill c-jira -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/daxaur/openpaw.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/c-jira .github/skills/c-jira && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "c-jira" agent skill from https://github.com/daxaur/openpaw/tree/main/skills/c-jira into .github/skills/c-jira/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "c-jira", 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.

skills CLI

$ npx skills add daxaur/openpaw --skill c-jira -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install daxaur/openpaw c-jira --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/daxaur/openpaw.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/c-jira .opencode/skills/c-jira && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "c-jira" agent skill from https://github.com/daxaur/openpaw/tree/main/skills/c-jira into .opencode/skills/c-jira/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "c-jira", 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: c-jira
GitHub stars: 173
Token cost: ~500 tokens
SKILL.md length: 113 words
Files: 1
Skills in repo: 42
Repo updated: May 23, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Manage Jira issues using jira (jira-cli). An agent skill from daxaur/openpaw.

Works in 4 steps: Always use the full issue key (e.g.,… → Run jira issue list before creating… → Use jira issue move to transition issues… → …
SKILL.md covers What This Skill Does, CLI Tool: jira, Usage Guidelines and Notes
Calls brew

What it does

C Jira is an agent skill from daxaur/openpaw. Manage Jira issues using jira (jira-cli). List and filter issues, create new tickets, transition issue status, manage sprints, and add comments — all from the terminal without opening a browser.

Its SKILL.md is about 500 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Jira. The repository describes itself as: Personal Assistant Wizard for Claude Code — npx pawmode. The licence is MIT.

Example prompts

“/c-jira”

Workflow steps

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

Always use the full issue key (e.g., MYPROJ-123) in commands.
Run jira issue list before creating tickets to check for existing duplicates.
Use jira issue move to transition issues — confirm the valid transition names with jira issue view first.
When the user says "close" or "resolve" an issue, use the appropriate transition name for their workflow.

What it can do on your machine

Read from SKILL.md and the folder at commit a2562d1. 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
Shell commands in SKILL.md call:
- brew
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

C Jira loads about 500 tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 113 words of instructions outside code blocks.

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

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 daxaur/openpaw at commit a2562d1, republished under its MIT licence (© daxaur). 113 words, ~500 tokens.

Download SKILL.mdSave it as .claude/skills/c-jira/SKILL.md (or your agent's skills folder).

name: c-jira
description: Manage Jira issues using `jira` (jira-cli). List and filter issues, create new tickets, transition issue status, manage sprints, and add comments — all from the terminal without opening a browser.
tags: jira, issues, project-management, sprints, tickets, atlassian

What This Skill Does

Uses jira (jira-cli) to interact with Jira projects — listing issues, creating tickets, moving issues through workflow transitions, and managing sprints.

CLI Tool: `jira`

List & View Issues

bash

jira issue list                             # List issues assigned to you
jira issue list --project MYPROJ            # Filter by project
jira issue list --status "In Progress"      # Filter by status
jira issue list --type Bug                  # Filter by issue type
jira issue view MYPROJ-123                  # View issue details

Create Issues

bash

jira issue create \
  --project MYPROJ \
  --type Bug \
  --summary "Login page throws 500 error" \
  --body "Steps to reproduce: ..." \
  --priority High \
  --label backend

Transitions

bash

jira issue move MYPROJ-123 "In Progress"
jira issue move MYPROJ-123 "Done"
jira issue move MYPROJ-123 "In Review"

Comments

bash

jira issue comment add MYPROJ-123 --body "Fixed in PR #456"

Sprints

bash

jira sprint list --project MYPROJ           # List sprints
jira sprint add MYPROJ-123 --sprint 42      # Add issue to sprint

Usage Guidelines

Always use the full issue key (e.g., MYPROJ-123) in commands.
Run jira issue list before creating tickets to check for existing duplicates.
Use jira issue move to transition issues — confirm the valid transition names with jira issue view first.
When the user says "close" or "resolve" an issue, use the appropriate transition name for their workflow.

Notes

Requires jira init to configure server URL and credentials before use.
Install: brew install ankitpokhrel/jira-cli/jira-cli

Files

Just SKILL.md in skills/c-jira of daxaur/openpaw.

Open the folder on GitHubat commit a2562d1

Compare with similar skills

C Jira 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.

C Jira compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
C Jira this skilldaxaur/openpaw	173	—	~500	Automated safety check: Pass	MIT	4 mo ago
Management Talkthananon/9arm-skills	3.2k	—	~3.2k	Automated safety check: Pass	None	3 mo ago
YugabyteDB Issue Creatoryugabyte/yugabyte-db	11k	—	~2k	Automated safety check: Pass	Custom licence	today
Dynamo Jira TicketDynamoDS/Dynamo	2k	—	~1.1k	Automated safety check: Pass	Apache-2.0	today
Code Reviewcroffasia/itsaplan	920	—	~2k	Automated safety check: Pass	AGPL-3.0	today
Connect Apps with ComposioComposioHQ/awesome-claude-skills	77k	3 repos	~557	Automated safety check: Pass	None	22 days ago

Similar skills

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…
3.2k GitHub stars~3.2k tokensUpdated 3 mo ago
Productivity & AutomationAuto-check passed
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.
11k GitHub stars~2k tokensUpdated today
DevelopmentAuto-check passed
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
2k GitHub stars~1.1k tokensUpdated today
Testing & QAAuto-check passed
Code Review
croffasia/itsaplan
A skill your agent uses when reviewing code — a diff, a merge request, a file, a directory, or a feature.
920 GitHub stars~2k tokensUpdated today
DevelopmentAuto-check passed
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.
77k GitHub starsUsed in 3 repos~557 tokens
Productivity & AutomationAuto-check passed
PR Body
SAP/spartacus
Official
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.
784 GitHub stars~499 tokensUpdated today
DevelopmentAuto-check passed

Questions about C Jira

What does C Jira do?

Manage Jira issues using jira (jira-cli). An agent skill from daxaur/openpaw. C Jira is an agent skill from daxaur/openpaw. Manage Jira issues using jira (jira-cli).

How do I install C Jira in Claude Code?

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

How do I install C Jira in Codex?

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

Can I use C Jira 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 daxaur/openpaw --skill c-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/c-jira, .gemini/skills/c-jira, .github/skills/c-jira and .opencode/skills/c-jira in your project.

What does C Jira need to run?

Going by SKILL.md and its folder, C Jira needs the command-line tools its instructions call (brew).

Does C Jira access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is C Jira 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 C Jira use?

C Jira 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 C Jira use?

About 500 tokens (SKILL.md is roughly 2k 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 C Jira?

Skills that share tags, products or a category with C Jira: 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 C Jira?

daxaur (a GitHub user) maintains it in daxaur/openpaw, which has 173 GitHub stars. The repository holds 42 skills in this directory. The repository was last updated on May 23, 2026.

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

Install C Jira

Facts

At a glance

What it does

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

What This Skill Does

CLI Tool: jira

List & View Issues

Create Issues

Transitions

Comments

Sprints

Usage Guidelines

Notes

Files

Compare with similar skills

Similar skills

More from daxaur/openpaw

Related

Questions about C Jira

CLI Tool: `jira`