jira-automation

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

1.97x

Quality

65%

Does it follow best practices?

Impact

95%

1.97x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/jira-automation/SKILL.md

Quality

Discovery

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and specific about what it does (Jira automation across multiple entity types) and names the integration mechanism clearly. Its main weakness is the lack of an explicit 'Use when...' clause, which caps completeness, and it could benefit from more natural user-facing trigger terms beyond the entity list. The technical reference to 'Rube MCP (Composio)' aids distinctiveness but doesn't help with user-facing discoverability.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create, update, or manage Jira tickets, sprints, or boards.'

Include more natural trigger terms users would say, such as 'create ticket', 'assign task', 'move to sprint', 'backlog', 'bug report', or 'story points'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete entities/actions: 'issues, projects, sprints, boards, comments, users' and specifies the integration method 'Rube MCP (Composio)'. Also includes a concrete operational instruction to 'search tools first for current schemas.'	3 / 3
Completeness	The 'what' is clearly stated (automate Jira tasks involving issues, projects, sprints, etc.), but there is no explicit 'Use when...' clause or equivalent trigger guidance telling Claude when to select this skill. The when is only implied by the domain mention.	2 / 3
Trigger Term Quality	Includes good domain keywords like 'Jira', 'issues', 'projects', 'sprints', 'boards', 'comments', 'users', but misses common natural user phrases like 'create ticket', 'assign task', 'backlog', 'story points', 'JIRA board', or 'bug report'. The term 'Rube MCP (Composio)' is technical jargon unlikely to be used by end users.	2 / 3
Distinctiveness Conflict Risk	The description is clearly scoped to Jira automation via a specific MCP integration (Rube/Composio), making it highly distinctive and unlikely to conflict with other skills. The combination of 'Jira' + 'Rube MCP (Composio)' creates a very clear niche.	3 / 3
	Total	10 / 12 Passed

Implementation

62%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, well-structured skill that clearly maps out Jira workflows with good tool sequencing and validation steps. Its main weaknesses are moderate verbosity with repeated information (custom field IDs pitfall appears 3 times), lack of concrete executable examples showing actual tool invocations, and all content being inline rather than using progressive disclosure for reference material.

Suggestions

Add at least one concrete, complete example of an actual MCP tool invocation with real parameter values (e.g., a full RUBE_SEARCH_TOOLS call followed by a JIRA_CREATE_ISSUE call with sample parameters) to improve actionability.

Consolidate repeated pitfalls (custom field IDs, ADF format, account IDs vs usernames) into the 'Known Pitfalls' section only, and remove duplicates from individual workflow sections.

Move the JQL syntax reference and quick reference table into separate linked files (e.g., JQL_REFERENCE.md, TOOLS_REFERENCE.md) to reduce the main skill's token footprint.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably well-structured but includes some redundancy—pitfalls about custom field IDs are repeated across multiple sections, and some explanations (like JQL syntax basics and pagination patterns) are things Claude already knows well. The quick reference table at the end duplicates information already covered in the workflows.	2 / 3
Actionability	The skill provides specific tool names, parameter names, and tool sequences, which is good. However, it lacks executable examples—no actual MCP call invocations with concrete parameter values are shown. The guidance is specific enough to follow but not copy-paste ready.	2 / 3
Workflow Clarity	Each workflow has a clear 'when to use' trigger, a numbered tool sequence with explicit prerequisite/required/optional labels, key parameters, and pitfalls. The setup section includes a validation step (confirm ACTIVE status before proceeding), and the tool sequences are well-ordered with clear dependencies.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections and a quick reference table, but it's quite long (~150+ lines of substantive content) with no references to external files for detailed content like JQL syntax or ADF formatting. The JQL syntax section and quick reference table could be split into separate reference files to keep the main skill leaner.	2 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: Lingjie-chen/MT5
Commit: 3069d33

Reviewed: 26 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.