jira
Skill38 starsChanged 8 months agoMITView on GitHub
Manage Jira issues, projects, sprints and boards via REST API
62 other projects use a version of this.
Adopted by
Most recently taken up by
- HAOYI99/skillstheir own version, first seen Nov 8, 2026
- domengabrovsek/agent-configtheir own version, first seen Nov 8, 2026
- domengabrovsek/claudetheir own version, first seen Nov 8, 2026
- sergeiwallace/skillstheir own version, first seen Nov 8, 2026
- icarloscornejo/doertheir own version, first seen Nov 7, 2026
- Integralist/agent-skillstheir own version, first seen Nov 6, 2026
Used with
Projects with it also use confluence, meet and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SpillwaveSolutionsSkillconfluence
Manage Confluence documentation with downloads, uploads, conversions, and diagrams. Use when asked to "download Confluence pages", "upload to Confluence", "convert Wiki Markup", "sync markdown to Confluence", "create Confluence page", or "handle Confluence images".
Also in 9 projects that use this
kv0906Skillmeet
Process meeting notes into structured notes with extracted decisions, blockers, and action items. Use for "/meet project type title" then paste notes.
Also in 3 projects that use this
er1chuSkillmonday
Full Monday morning setup. Creates week folder, pulls carry-forward, and generates briefing in one pass. Use on Monday mornings or when the user says "monday", "start my week", or "monday morning".
Also in 3 projects that use this
koderoverSkilljenkins
Jenkins CI/CD 操作。用于:(1) 触发 Jenkins 任务构建 (2) 查询任务状态和构建历史 (3) 获取构建日志 (4) 操作 Jenkins 节点和配置
Also in 3 projects that use this
refly-aiSkillasana
Integrate with Asana for task management. Use when you need to: (1) create and manage Asana tasks, (2) organize project work, or (3) automate team task tracking workflows.
Also in 3 projects that use this
montymiSkilltech-spec
Parse and review Technical Specification documents for completeness, consistency, and implementation readiness
Also in 3 projects that use this
Other versions62 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 62
- oracle/graalpython★ 1.7ksame name
- microsoft/hve-core★ 1.6ksame name
- SonarSource/SonarJS★ 1.3ksame name
- mongodb/docs★ 779same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- magnus919/agent-skills★ 172same name
- kv0906/pm-kit★ 138same name
- oprogramadorreal/optimus-claude★ 75same name
- grandcamel/JIRA-Assistant-Skills★ 47same name
52 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository36 other files it gives its agents.
- abacatepaySkill
- appsignalSkill
- clickupSkill
- cloudflareSkill
- cloudinarySkill
- datadogSkill
- digitaloceanSkill
- discordSkill
- firebaseSkill
- flyioSkill
- google-sheetsSkill
- herokuSkill
- honeybadgerSkill
- hostingerSkill
- hubspotSkill
- intercomSkill
- linearSkill
- mercadopagoSkill
- n8nSkill
- notionSkill
- openaiSkill
- planetscaleSkill
- posthogSkill
- railwaySkill
- resendSkill
- rewriteSkill
- sentrySkill
- shopifySkill
- slackSkill
- stripeSkill
- supabaseSkill
- trelloSkill
- twilioSkill
- vercelSkill
- xSkill
- zendeskSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 56 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 40
If the output is OK, proceed to the Flow section.
- Very specific: line 42
If the output is SETUP_NEEDED, guide the user step by step.
- Distinctive: line 65
If the script outputs an error, the config is invalid.
- Distinctive: line 104
Ask the user to confirm the details before creating.
“Common” is measured: kept by at least 6 in 10 of the 56 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/jira
Connect to Jira Cloud to manage projects, issues, sprints, boards and more. Pure Ruby, zero gems — stdlib only.
Structure
scripts/
├── auth.rb # Basic Auth + jira_request helper (required by all scripts)
├── check_setup.rb # Check if config exists (outputs OK or SETUP_NEEDED)
├── save_config.rb # Save and validate domain, email and API token
├── projects.rb # List projects
├── project.rb # Get project details
├── issues.rb # Search issues using JQL
├── issue.rb # Get issue details
├── create_issue.rb # Create an issue
├── update_issue.rb # Update an issue
├── transitions.rb # List available transitions for an issue
├── transition.rb # Transition an issue (change status)
├── comments.rb # List comments on an issue
├── add_comment.rb # Add a comment to an issue
├── assign.rb # Assign an issue to a user
├── boards.rb # List boards (Agile)
└── sprints.rb # List sprints for a boardSetup (check before using)
ruby ~/.claude/skills/jira/scripts/check_setup.rbIf the output is OK, proceed to the Flow section.
If the output is SETUP_NEEDED, guide the user step by step. Present ONE step at a time, wait for the user to confirm before moving to the next.
Step 1 — Ask the user for their Jira domain:
What is your Jira Cloud domain? For example, if you access Jira at
https://mycompany.atlassian.net, the domain ismycompany.
Step 2 — Ask the user to create an API token:
Create an API token at: https://id.atlassian.com/manage-profile/security/api-tokens
Click Create API token, give it a name (e.g. "hitank"), and copy the token. Also confirm your Atlassian account email.
Paste the email and token here.
Step 3 — When the user provides all three values, save them:
ruby ~/.claude/skills/jira/scripts/save_config.rb 'DOMAIN' 'EMAIL' 'TOKEN'If the script outputs an error, the config is invalid. Ask the user to double-check and try again.
If setup is not complete, DO NOT proceed to the Flow. Complete all steps first.
Flow
The argument $ARGUMENTS may contain a project key or issue key.
Step 1: List projects
ruby ~/.claude/skills/jira/scripts/projects.rbPresent the projects. If $ARGUMENTS matches a project key, use that project. Otherwise ask which project to work with.
Step 2: Search issues
ruby ~/.claude/skills/jira/scripts/issues.rb 'project = PROJECT_KEY ORDER BY updated DESC'Present the issues and ask what the user wants to do.
Step 3: Actions
Get issue details:
ruby ~/.claude/skills/jira/scripts/issue.rb ISSUE_KEYSearch with JQL:
ruby ~/.claude/skills/jira/scripts/issues.rb 'project = MYPROJ AND status = "In Progress"'
ruby ~/.claude/skills/jira/scripts/issues.rb 'assignee = currentUser() ORDER BY priority DESC' --max 50Create an issue (requires user confirmation):
Ask the user to confirm the details before creating.
ruby ~/.claude/skills/jira/scripts/create_issue.rb PROJECT_KEY "Issue summary"
ruby ~/.claude/skills/jira/scripts/create_issue.rb PROJECT_KEY "Fix login bug" --type Bug --priority High --description "Detailed description"Update an issue (requires user confirmation):
Show current issue details first, then ask what to change.
ruby ~/.claude/skills/jira/scripts/update_issue.rb ISSUE_KEY '{"summary":"New title","priority":{"name":"High"}}'Transition an issue (requires user confirmation):
First list available transitions, then ask which one to apply.
ruby ~/.claude/skills/jira/scripts/transitions.rb ISSUE_KEY
ruby ~/.claude/skills/jira/scripts/transition.rb ISSUE_KEY TRANSITION_IDAssign an issue (requires user confirmation):
ruby ~/.claude/skills/jira/scripts/assign.rb ISSUE_KEY ACCOUNT_ID
ruby ~/.claude/skills/jira/scripts/assign.rb ISSUE_KEY unassignList comments:
ruby ~/.claude/skills/jira/scripts/comments.rb ISSUE_KEYAdd a comment (requires user confirmation):
ruby ~/.claude/skills/jira/scripts/add_comment.rb ISSUE_KEY "Comment text here"List boards (Agile):
ruby ~/.claude/skills/jira/scripts/boards.rbList sprints:
ruby ~/.claude/skills/jira/scripts/sprints.rb BOARD_ID
ruby ~/.claude/skills/jira/scripts/sprints.rb BOARD_ID --state activeNotes
- Pure Ruby, zero gems — stdlib only (json, net/http, uri, base64, fileutils)
- Auth via Basic Auth (email + API token)
- Config file:
~/.config/jira/config.json(outside the repo, never commit) - Creating, updating, transitioning, and assigning issues require explicit user confirmation
- Adding comments requires user confirmation
- Jira Cloud API v3 uses Atlassian Document Format (ADF) for descriptions and comments
- JQL (Jira Query Language) is used for searching issues
- Base URL:
https://DOMAIN.atlassian.net/rest/api/3 - Agile URL:
https://DOMAIN.atlassian.net/rest/agile/1.0
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

