Automate Jira tasks via Rube MCP (Composio): issues, projects, sprints, boards, comments, users. Always search tools first for current schemas.
75
65%
Does it follow best practices?
Impact
95%
1.97xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/jira-automation/SKILL.mdSprint workflow tool sequencing
RUBE_SEARCH_TOOLS first
0%
100%
RUBE_MANAGE_CONNECTIONS called
0%
100%
Connection status verified
0%
100%
JIRA_LIST_BOARDS before JIRA_LIST_SPRINTS
70%
100%
boardId passed to LIST_SPRINTS
87%
100%
ISO date format for sprint
100%
100%
One-active-sprint constraint acknowledged
90%
100%
JIRA_CREATE_SPRINT used for new sprint
75%
100%
JIRA_MOVE_ISSUE_TO_SPRINT used
75%
100%
JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST for backlog
33%
100%
Correct tool names used
22%
100%
JQL search and user account ID patterns
RUBE_SEARCH_TOOLS first
0%
100%
RUBE_MANAGE_CONNECTIONS called
0%
100%
JQL search tool used
30%
100%
JQL uses correct operators
100%
100%
JQL field name case sensitivity noted
50%
100%
Pagination handling
100%
100%
maxResults within bounds
100%
100%
JIRA_FIND_USERS used for lookup
70%
100%
accountId used for assignment
83%
100%
JIRA_GET_ISSUE for full details
0%
0%
Correct tool names used
0%
100%
Issue creation prerequisites and ADF descriptions
RUBE_SEARCH_TOOLS first
0%
100%
RUBE_MANAGE_CONNECTIONS called
0%
100%
JIRA_GET_ALL_PROJECTS as prerequisite
30%
100%
JIRA_GET_FIELDS as prerequisite
30%
100%
Custom fields use ID format
100%
100%
ADF used for description
100%
100%
Correct issue creation parameters
62%
100%
JIRA_EDIT_ISSUE for updates
0%
100%
ADF used for comment
100%
100%
Account ID for user fields
0%
37%
Correct tool names used
11%
100%
7cc63f3
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.