Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.
npxskills add sickn33/antigravity-awesome-skills--skill jira-automationLoading…
Automate Jira operations through Composio's Jira toolkit via Rube MCP.
RUBE_MANAGE_CONNECTIONS with toolkit jiraRUBE_SEARCH_TOOLS first to get current tool schemasGet 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.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit jiraWhen 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 offsetfields: Array of field names to returnissueIdOrKey: Issue key like 'PROJ-123' for GET_ISSUEPitfalls:
customfield_10001, not display namestotal vs startAt + maxResults to continueWhen 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 titledescription: Issue description (Atlassian Document Format or plain text)issueIdOrKey: Issue key for editsPitfalls:
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_BOARDSsprintId: Sprint ID for move operationsname: Sprint name for creationstartDate/endDate: Sprint dates in ISO formatPitfalls:
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:
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 keyquery: Search text for FIND_USERSroleId: Role ID for role operationsPitfalls:
Common operators:
project = "PROJ" - Filter by projectstatus = "In Progress" - Filter by statusassignee = currentUser() - Current user's issuescreated >= -7d - Created in last 7 dayslabels = "bug" - Filter by labelpriority = High - Filter by priorityORDER BY created DESC - Sort resultsCombinators:
AND - Both conditionsOR - Either conditionNOT - Negate conditionstartAt and maxResults parameterstotal in response to determine remaining pagesstartAt + maxResults >= totalField Names:
customfield_10001Authentication:
| 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 |
This skill is applicable to execute the workflow or actions described in the overview.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.
CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).