jira
Skill94 starsChanged 5 months agoMITView on GitHub
General-purpose Jira skill for any Jira project. Use for any Jira-related request: creating issues (Epic, Story, Bug, Task, Sub-task), querying issues (in progress, completed, by type/status, bugs by due date), or updating issues. Triggers include: "create an epic", "create a bug", "show me bugs", "epics in progress", "issues completed last N days", "bugs due in N days", or any request involving Jira. Also triggers when any other skill (e.g. write-us, write-epic-build) reaches a "create in Jira" confirmation step or similar.
65 other projects use a version of this.
Adopted by
Most recently taken up by
- thalals/MY-CLAUDE-SKILLtheir own version, first seen Nov 16, 2026
- Ivan-propio/claude-skillstheir own version, first seen Nov 16, 2026
- fworks-tech/agenthoodtheir own version, first seen Nov 15, 2026
- Integralist/agent-skillstheir own version, first seen Nov 14, 2026
- arfar-x/agent-skillstheir own version, first seen Nov 14, 2026
- icarloscornejo/doertheir own version, first seen Nov 11, 2026
Used with
Projects with it also use confluence, monday and 10 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
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
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
refly-aiSkillhubspot
Integrate with HubSpot for CRM management. Use when you need to: (1) manage contacts and deals, (2) track sales pipelines, or (3) automate marketing and CRM workflows.
Also in 4 projects that use this
koderoverSkilljenkins
Jenkins CI/CD 操作。用于:(1) 触发 Jenkins 任务构建 (2) 查询任务状态和构建历史 (3) 获取构建日志 (4) 操作 Jenkins 节点和配置
Also in 3 projects that use this
SentrySkilldatadog
Query live Datadog telemetry (logs, metrics, traces, spans, monitors, incidents, dashboards, services, hosts) through Datadog's Pup CLI. Use when users ask to investigate production behavior in Datadog, including searching logs, checking monitor status, inspecting traces or spans, looking up incidents, finding services, or correlating metrics. Do not use it for Sentry issues, repository/source-code work, or ticketing.
Also in 3 projects that use this
Other versions65 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 65
- oracle/graalpython★ 1.7ksame name
- microsoft/hve-core★ 1.6ksame name
- SonarSource/SonarJS★ 1.3ksame name
- mongodb/docs★ 780same name
- sd0xdev/sd0x-dev-flow★ 192same name
- sd0xdev/sd0x-harness★ 192same name
- magnus919/agent-skills★ 177same name
- kv0906/pm-kit★ 138same name
- oprogramadorreal/optimus-claude★ 75same name
- grandcamel/JIRA-Assistant-Skills★ 47same name
55 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 repository15 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- check-boardSkill
- check-epicSkill
- check-ic-activitySkill
- check-issueSkill
- mentor-meSkill
- one-on-oneSkill
- plan-initiativeSkill
- us-mappingSkill
- write-epic-buildSkill
- write-epic-technical-discoverySkill
- write-strategySkill
- write-updateSkill
- write-usSkill
- write-visionSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 5 are distinctive, and 10 are very specific to this project.
0
Common
Most of the 58 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Before using this skill, replace the following placeholders throughout this file — including the name: and description: in the frontmatter …
- Distinctive: line 26
Delete this section and the "Auto-detection" section below once you've replaced the placeholders.
- Very specific: line 34
If {{PROJECT_KEY}} appears literally in this file → ask: *"What is your Jira project key?
- Very specific: line 35
If {{CLOUD_ID}} appears literally in this file → ask: *"What is your Atlassian Cloud ID?
- Very specific: line 36
If {{BASE_URL}} appears literally in this file → ask: *"What is your Jira domain?
- Very specific: line 41
If yes → edit this SKILL.md file, replacing each {{PLACEHOLDER}} with the value the user provided, and confirm when done.
- Distinctive: line 42
If no → keep them only for this conversation.
- Very specific: line 65
Always prefer the
jiraCLI: Only fall back to MCP (searchJiraIssuesUsingJql, createJiraIssue, etc.) if the CLI is not available or a … - Distinctive: line 120
If not stated, ask. Options: Epic, Story, Bug, Task, Sub-task.
- Very specific: line 171
Always try the CLI first: Do not skip to MCP because the description is long or structured — use --body or pass the description via stdin.
- Very specific: line 183
If CLI flags don't support a field, fall back to createJiraIssue MCP with:
- Very specific: line 210
Always scope queries to project = {{PROJECT_KEY}} — never query without the team filter
- Distinctive: line 211
Never invent issue keys, user IDs, or field values
- Distinctive: line 212
If a field value is unknown, ask — don't guess
- Very specific: line 213
If the user says "N days", substitute the number directly into the JQL (e.g.
“Common” is measured: kept by at least 6 in 10 of the 58 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
Skill: Jira — Project
Manual Setup
Before using this skill, replace the following placeholders throughout this file — including the name: and description: in the frontmatter above:
name:→ use a short identifier for your project (e.g.jira-platform,jira-core)description:→ update "any Jira project" to mention your actual project name, so Claude picks the right skill when you have multiple
Then replace the configuration placeholders:
| Placeholder | Description | How to find it |
{{PROJECT_KEY}} | Your Jira project key | Visible in any issue key (e.g. PLAT-123 → key is PLAT) |
{{CLOUD_ID}} | Your Atlassian Cloud ID | Run jira config list or extract from your Atlassian URL |
{{BASE_URL}} | Your Jira domain | e.g. yourcompany.atlassian.net |
Delete this section and the "Auto-detection" section below once you've replaced the placeholders.
Auto-detection (always run this first)
Before doing anything else, check if any placeholder is still unconfigured:
- If
{{PROJECT_KEY}}appears literally in this file → ask: "What is your Jira project key? (e.g. PLAT, ENG, CORE)" - If
{{CLOUD_ID}}appears literally in this file → ask: "What is your Atlassian Cloud ID? You can find it by runningjira config listor from your Atlassian admin URL." - If
{{BASE_URL}}appears literally in this file → ask: "What is your Jira domain? (e.g. yourcompany.atlassian.net)"
Once the user provides the values, use them for the rest of the conversation without asking again.
Then ask: "Should I save these values in the skill so you don't have to enter them again in future conversations?"
- If yes → edit this SKILL.md file, replacing each
{{PLACEHOLDER}}with the value the user provided, and confirm when done. - If no → keep them only for this conversation.
Configuration
| Field | Value |
| Project | {{PROJECT_KEY}} |
| cloudId | {{CLOUD_ID}} |
| Base URL | {{BASE_URL}} |
| Assignee | None (unless user specifies) |
| Reporter | Current user |
| Priority | Medium (unless user specifies) |
| Components | None by default |
| Labels | None by default |
Supported issue types: Epic, Story, Bug, Task, Sub-task
Tool usage
Always prefer the jira CLI. Only fall back to MCP (searchJiraIssuesUsingJql, createJiraIssue, etc.) if the CLI is not available or a specific operation isn't supported by it.
Jira CLI quick reference
# Search / query — using native flags (preferred for simple filters)
jira issue list -p {{PROJECT_KEY}} -a "<email>" -s "<status>" -t <IssueType> \
--created-after "YYYY-MM-DD" --created-before "YYYY-MM-DD" \
--plain --columns KEY,SUMMARY,STATUS,ASSIGNEE,PRIORITY \
--paginate 0:100
# Search / query — using raw JQL (for complex filters)
# ⚠️ Do NOT include ORDER BY in the JQL string — the CLI adds it automatically and will return a 400 error if you include it
jira issue list -p {{PROJECT_KEY}} --jql "<JQL without ORDER BY>"
# Create issue
jira issue create -p {{PROJECT_KEY}} -t <IssueType> -s "<summary>" [flags]
# View issue
jira issue view <ISSUE-KEY>Prefer native flags over --jql when the filter maps cleanly (assignee, status, type, date range). Use --jql only for filters that have no native flag equivalent (e.g. resolutiondate, custom fields).
A. Querying issues
Identify the query intent and build the appropriate query. Always scope to project = {{PROJECT_KEY}}.
Common queries
| User request | Preferred command |
| Epics in progress | jira issue list -p {{PROJECT_KEY}} -t Epic -s "In Progress" --plain --columns KEY,SUMMARY,STATUS,ASSIGNEE --paginate 0:100 |
| Bugs open / in progress | jira issue list -p {{PROJECT_KEY}} -t Bug --jql 'project = {{PROJECT_KEY}} AND "customfield_10001" = "82dc66a2-af52-404a-8663-a25bb3c10093" AND issuetype = Bug AND status != Done' --plain --paginate 0:100 |
| Issues completed last N days | jira issue list -p {{PROJECT_KEY}} --jql 'project = {{PROJECT_KEY}} AND "customfield_10001" = "82dc66a2-af52-404a-8663-a25bb3c10093" AND status = Done AND resolutiondate >= -Nd' --plain --paginate 0:100 |
| Issues of type X in status Y | jira issue list -p {{PROJECT_KEY}} -t X -s "Y" --plain --paginate 0:100 |
| Bugs due in ≤ N days | jira issue list -p {{PROJECT_KEY}} -t Bug --jql 'project = {{PROJECT_KEY}} AND "customfield_10001" = "82dc66a2-af52-404a-8663-a25bb3c10093" AND issuetype = Bug AND duedate <= Nd AND status != Done' --plain --paginate 0:100 |
| All open issues | jira issue list -p {{PROJECT_KEY}} --jql 'project = {{PROJECT_KEY}} AND "customfield_10001" = "82dc66a2-af52-404a-8663-a25bb3c10093" AND status != Done' --plain --paginate 0:100 |
| Issues by assignee in date range | jira issue list -p {{PROJECT_KEY}} -a "<email>" --created-after "YYYY-MM-DD" --plain --columns KEY,SUMMARY,STATUS,PRIORITY --paginate 0:100 |
Output format for queries
Show results as a markdown table with columns:
Key | Type | Summary | Status | Priority | Due Date | Assignee
Omit columns that are empty for all results. Include a total count at the end.
B. Creating issues
Step 1 — Determine issue type
If not stated, ask. Options: Epic, Story, Bug, Task, Sub-task.
Step 2 — Gather required fields by type
Epic
| Field | Required | Notes |
| Summary | Yes | Concise title |
| Description | Recommended | Context and goals |
| Start Date | Ask | customfield_10015 (YYYY-MM-DD) |
| Due Date | Ask | duedate (YYYY-MM-DD) |
| Parent | No | Epics are top-level by default |
Story
| Field | Required | Notes |
| Summary | Yes | Concise title, start with verb |
| Description | Yes | Use Story format (see §C) |
| Parent Epic | Ask | Query recent epics if not given; allow null |
Bug
| Field | Required | Notes |
| Summary | Yes | Describe the defect clearly |
| Description | Yes | Steps to reproduce, expected vs actual |
| Priority | Ask | Default Medium; consider High/Critical if user hints urgency |
| Due Date | Ask | Especially relevant for bugs |
| Parent Epic | Ask | Optional |
Task
| Field | Required | Notes |
| Summary | Yes | Action-oriented title |
| Description | Recommended | What needs to be done and why |
| Parent | Ask | Can be Epic or Story |
Sub-task
| Field | Required | Notes |
| Summary | Yes | |
| Description | Recommended | |
| Parent | Required | Must have a parent issue key |
Step 3 — Draft and confirm
Present the issue draft before creating. Ask the user to confirm or edit.
Do not create in Jira until explicit confirmation.
Step 4 — Create via CLI
Always try the CLI first. Do not skip to MCP because the description is long or structured — use --body or pass the description via stdin. Only fall back to MCP if the CLI command fails or explicitly does not support a required field.
jira issue create \
-p {{PROJECT_KEY}} \
-t "<IssueType>" \
-s "<summary>" \
[--priority "Medium"] \
[--custom "duedate=YYYY-MM-DD"] \
[--parent "<PARENT-KEY>"]If CLI flags don't support a field, fall back to createJiraIssue MCP with:
{
"cloudId": "{{CLOUD_ID}}",
"projectKey": "{{PROJECT_KEY}}",
"issueType": "<IssueType>",
"summary": "<summary>",
"description": "<ADF description>",
"priority": "Medium",
"duedate": "YYYY-MM-DD",
"parent": { "key": "<PARENT-KEY>" }
}ADF note: When using MCP, description must be in Atlassian Document Format (
type: "doc"). Use level-2 headings for sections and paragraphs for content.
Step 5 — Output after creation
Share:
- Direct link:
https://{{BASE_URL}}/browse/{{PROJECT_KEY}}-XXXX - Brief summary: type, title, parent (if any), due date (if set)
General rules
- Always scope queries to
project = {{PROJECT_KEY}}— never query without the team filter - Never invent issue keys, user IDs, or field values
- If a field value is unknown, ask — don't guess
- If the user says "N days", substitute the number directly into the JQL (e.g.
-7d) - For date fields use ISO format:
YYYY-MM-DD
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.

