Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Get Started Free →

Jira Automation via Rube MCP · sickn33 | DecimalAI

Jira Automation

SkillScore8Maintained

jira-automation

Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.

productivityby sickn33

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Project Management pack

1 · One-time — install the CLI (docs ↗)

pip install decimalai

2 · Get the skill — writes .claude/skills/jira-automation/SKILL.md

decimalai skills pull jira-automation --out .claude/skills/

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/jira-automation/SKILL.md https://app.decimal.ai/s/jira-automation/SKILL.md

Raw file: /s/jira-automation/SKILL.md ↗ · machine-readable summary at /s/jira-automation.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

25 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 54d ago

—+139% tokens0% turns8% of whole cases pass with skill (2/25)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-24	✗→✓	▲ Improved	—	—
case-22	✓→✓	＝ Same ✓	—	—
case-02	✗→✗	＝ Same ✗	—	—
case-12	✗→✗	＝ Same ✗	—	—
case-17	✗→✗	＝ Same ✗	—	—

Showing 5 of 25 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v5 — 9/11/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

sickn33 / antigravity-awesome-skills

skills/jira-automation/SKILL.md

View on GitHub ↗

License MITImported 9/11/2026Version v2

Skill contents

SKILL.md

Jira Automation via Rube MCP

Automate Jira operations through Composio's Jira toolkit via Rube MCP.

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Jira connection via RUBE_MANAGE_CONNECTIONS with toolkit jira
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit jira
If connection is not ACTIVE, follow the returned auth link to complete Jira OAuth
Confirm connection status shows ACTIVE before running any workflows

Core Workflows

1. Search and Filter Issues

When to use: User wants to find issues using JQL or browse project issues

Tool sequence:

JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST - Search with JQL query Required]
JIRA_GET_ISSUE - Get full details of a specific issue Optional]

Key parameters:

jql: JQL query string (e.g., project = PROJ AND status = "In Progress")
maxResults: Max results per page (default 50, max 100)
startAt: Pagination offset
fields: Array of field names to return
issueIdOrKey: Issue key like 'PROJ-123' for GET_ISSUE

Pitfalls:

JQL field names are case-sensitive and must match Jira configuration
Custom fields use IDs like customfield_10001, not display names
Results are paginated; check total vs startAt + maxResults to continue

2. Create and Edit Issues

When to use: User wants to create new issues or update existing ones

Tool sequence:

JIRA_GET_ALL_PROJECTS - List projects to find project key Prerequisite]
JIRA_GET_FIELDS - Get available fields and their IDs Prerequisite]
JIRA_CREATE_ISSUE - Create a new issue Required]
JIRA_EDIT_ISSUE - Update fields on an existing issue Optional]
JIRA_ASSIGN_ISSUE - Assign issue to a user Optional]

Key parameters:

project: Project key (e.g., 'PROJ')
issuetype: Issue type name (e.g., 'Bug', 'Story', 'Task')
summary: Issue title
description: Issue description (Atlassian Document Format or plain text)
issueIdOrKey: Issue key for edits

Pitfalls:

Issue types and required fields vary by project; use GET_FIELDS to check
Custom fields require exact field IDs, not display names
Description may need Atlassian Document Format (ADF) for rich content

3. Manage Sprints and Boards

When to use: User wants to work with agile boards, sprints, and backlogs

Tool sequence:

JIRA_LIST_BOARDS - List all boards Prerequisite]
JIRA_LIST_SPRINTS - List sprints for a board Required]
JIRA_MOVE_ISSUE_TO_SPRINT - Move issue to a sprint Optional]
JIRA_CREATE_SPRINT - Create a new sprint Optional]

Key parameters:

boardId: Board ID from LIST_BOARDS
sprintId: Sprint ID for move operations
name: Sprint name for creation
startDate/endDate: Sprint dates in ISO format

Pitfalls:

Boards and sprints are specific to Jira Software (not Jira Core)
Only one sprint can be active at a time per board

4. Manage Comments

When to use: User wants to add or view comments on issues

Tool sequence:

JIRA_LIST_ISSUE_COMMENTS - List existing comments Optional]
JIRA_ADD_COMMENT - Add a comment to an issue Required]

Key parameters:

issueIdOrKey: Issue key like 'PROJ-123'
body: Comment body (supports ADF for rich text)

Pitfalls:

Comments support ADF (Atlassian Document Format) for formatting
Mentions use account IDs, not usernames

5. Manage Projects and Users

When to use: User wants to list projects, find users, or manage project roles

Tool sequence:

JIRA_GET_ALL_PROJECTS - List all projects Optional]
JIRA_GET_PROJECT - Get project details Optional]
JIRA_FIND_USERS / JIRA_GET_ALL_USERS - Search for users Optional]
JIRA_GET_PROJECT_ROLES - List project roles Optional]
JIRA_ADD_USERS_TO_PROJECT_ROLE - Add user to role Optional]

Key parameters:

projectIdOrKey: Project key
query: Search text for FIND_USERS
roleId: Role ID for role operations

Pitfalls:

User operations use account IDs (not email or display name)
Project roles differ from global permissions

Common Patterns

JQL Syntax

Common operators:

project = "PROJ" - Filter by project
status = "In Progress" - Filter by status
assignee = currentUser() - Current user's issues
created >= -7d - Created in last 7 days
labels = "bug" - Filter by label
priority = High - Filter by priority
ORDER BY created DESC - Sort results

Combinators:

AND - Both conditions
OR - Either condition
NOT - Negate condition

Pagination

Use startAt and maxResults parameters
Check total in response to determine remaining pages
Continue until startAt + maxResults >= total

Known Pitfalls

Field Names:

Custom fields use IDs like customfield_10001
Use JIRA_GET_FIELDS to discover field IDs and names
Field names in JQL may differ from API field names

Authentication:

Jira Cloud uses account IDs, not usernames
Site URL must be configured correctly in the connection

Quick Reference

| Task | Tool Slug | Key Params | |------|-----------|------------| | Search issues (JQL) | JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST | jql, maxResults | | Get issue | JIRA_GET_ISSUE | issueIdOrKey | | Create issue | JIRA_CREATE_ISSUE | project, issuetype, summary | | Edit issue | JIRA_EDIT_ISSUE | issueIdOrKey, fields | | Assign issue | JIRA_ASSIGN_ISSUE | issueIdOrKey, accountId | | Add comment | JIRA_ADD_COMMENT | issueIdOrKey, body | | List comments | JIRA_LIST_ISSUE_COMMENTS | issueIdOrKey | | List projects | JIRA_GET_ALL_PROJECTS | (none) | | Get project | JIRA_GET_PROJECT | projectIdOrKey | | List boards | JIRA_LIST_BOARDS | (none) | | List sprints | JIRA_LIST_SPRINTS | boardId | | Move to sprint | JIRA_MOVE_ISSUE_TO_SPRINT | sprintId, issues | | Create sprint | JIRA_CREATE_SPRINT | name, boardId | | Find users | JIRA_FIND_USERS | query | | Get fields | JIRA_GET_FIELDS | (none) | | List filters | JIRA_LIST_FILTERS | (none) | | Project roles | JIRA_GET_PROJECT_ROLES | projectIdOrKey | | Project versions | JIRA_GET_PROJECT_VERSIONS | projectIdOrKey |

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Example

User request:

> Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users.

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Illustrative Want to see what jira-automation would put in front of your model? Preview the rendered body and check its trigger phrases — no LLM call, no signup.

Latest benchmark · publisher runVerifiedfrom v1 · older version

7/28/2026, 21:21 UTC · 25 cases

Measured on 10 comparable cases — below the 22 needed to publish a lift, so this result is shown here but not on the registry card or leaderboard.

Lift

+4%

8% vs 4%

Agent turns

0%

1.0 vs 1.0

Tokens

+139%

2,690.3 vs 1,126.1

fail → pass · 1pass → pass · 1fail → fail · 23

Per-case results (25)

Case	Status	Duration (ms)			Turns			Tokens			Tool calls
Case	Status	Without	With	Δ	Without	With	Δ	Without	With	Δ	Without	With	Δ
case-02 Could you search Jira for all 'In Progress' tasks in project 'DEV' created over the last 14 days? Format the output as a Markdown table with columns for Issue Key, Summary, Assignee, and Priority.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-12 Add Alice Smith to the Developer project role for project key 'BACKEND'.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-17 We need to log a user story for the mobile team, but I'm not sure of the exact project key or required fields. How should we proceed before creating the issue?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-20 Search for active Jira users matching the query string 'developer' to find their account IDs.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-10 We need to process all 250 tickets in project 'FRONTEND'. Explain how to fetch every record sequentially using Jira search tool parameters without missing issues.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-06 Write a JQL query to find all issues in project 'OPS' that are linked with the link relation 'blocks'.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-16 Fetch full details including description and fields for Jira issue key 'SEC-303'.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-05 Write a JQL query to list all unresolved issues in project 'SEC' where the due date is before today.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-09 Assign issue 'PROJ-789' to john.doe@company.com.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-25 Add a comment to issue 'TEST-5' mentioning team member John Doe. What format or ID must be used for mentioning John Doe in the comment?	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-11 Create a new sprint named 'Sprint 42' on Board 5 starting today in ISO 8601 format and ending 14 days later.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-07 Write a JQL query to select all closed issues in project 'CLOUD' where the resolution was marked as 'Cannot Reproduce'.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-23 Fetch full project metadata and details for project key 'CLOUD'.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-24 Explain the tool sequence to move issue 'DEV-99' from sprint 10 to sprint 11.	fail→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-03 Please post a comment on issue 'DEV-456' stating 'Investigating root cause in auth service' and move the issue into the currently active sprint on Board 12. Send back a status report summarizing the actions completed.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-15 I want to create a task in Jira for project 'OPS' titled 'Server Migration'. Ensure the tool environment is properly connected and authenticated before proceeding.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-13 Retrieve all existing comments on issue 'BUG-101' and then post 'Reproduced on latest build' if the issue exists.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-19 Retrieve the list of all available Jira agile boards to find the board ID for our team.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-14 Construct and run a JQL query to find all issues assigned to the logged-in user with type 'Bug' created within the last 7 days.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-01 I need to file a high-priority bug report in Jira for project 'ALPHA'. The summary should be 'Login button unresponsive on iOS' and the description should state 'Users report tapping login does nothing on iOS 17.' Please set the priority to High, assign it to Jane Doe, and return a summary confirmation containing the new ticket key and URL.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-22 When checking Jira connection status via Rube MCP, the connection status returned is INACTIVE along with an authorization link. What must be done next?	pass→pass	—	—	—	—	—	—	—	—	—	—	—	—
case-08 Search Jira for issues where the 'Customer Impact' field is marked as 'Critical'. Construct the JQL query and execute the search.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-04 Write a JQL query to find all unassigned bugs in project 'OPS' created in the last 3 days.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-18 Update issue 'DATA-12' with new summary 'ETL Job Failure' and description 'Pipeline timed out during night run'.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—
case-21 Write and execute a JQL query for project 'IOS' to list open bugs sorted from newest to oldest.	fail→fail	—	—	—	—	—	—	—	—	—	—	—	—

These cases were also screened by the skill’s intent / safety pass.See the Trust review ↗Reproduce this benchmark in Colab ↗

How this skill was measured

DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 25 cases were attempted, and 10 counted toward the lift figure. The other 15 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +4 percentage points is the difference between those two pass rates over the 10 comparable cases. 4 cases got worse with the skill loaded, and they are included in that figure.

Model measured: gemini-3.6-flash
Graded by: gemini-3.6-flash
Grading method: judged
Verification: verified
Pass rate without the skill: 4%
Pass rate with the skill: 8%
Cases attempted: 25
Cases counted toward lift: 10
Cases that regressed: 4
Skill version measured: v1
Run completed: 7/28/2026, 21:21 UTC

The publisher has shipped newer versions since this run, so these numbers describe v1, not the version currently listed.

The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.

SkillScore blends 4 signals1 of 4 complete

BenchmarkPass rate WITH skill on a verified run8

Live evalNeeds ≥10 evaluated traces in 30 days

AI ratingNeeds ≥10 rated traces

AdoptionNeeds ≥10 serves across ≥2 orgs in 30 days

Efficiency · separate axis (at equal correctness)+0% turns+226% tokens

Shown for transparency; not credited unless a verified run shows no correctness regression.

Backed by 1 of 4 signals — each added signal makes the score more robust.

Verified on gemini-3.6-flash · re-tested 53 days ago

Other measured skills in the registry, with their headline benchmark lift.