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

60%

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 ./plugins/all-skills/skills/jira-automation/SKILL.md

Quality

Discovery

57%

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 identifies a clear niche (Jira automation via Rube MCP) and lists relevant entity types, but lacks concrete action verbs and an explicit 'Use when...' clause. It would benefit from specifying what operations are performed and when Claude should select this skill.

Suggestions

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

Replace the entity list with concrete actions, e.g., 'Create and update issues, manage sprints, search boards, add comments, assign users in Jira.'

Include common user trigger terms like 'tickets', 'backlog', 'story points', 'assign ticket', 'Jira board' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists domain areas (issues, projects, sprints, boards, comments, users) but these are nouns/entities rather than concrete actions. 'Automate Jira tasks' is somewhat vague—it doesn't specify what actions are performed (e.g., create issues, assign users, move sprints).	2 / 3
Completeness	The 'what' is partially addressed (automate Jira tasks across several entities), but there is no explicit 'Use when...' clause or equivalent trigger guidance. The instruction 'Always search tools first for current schemas' is an implementation note for Claude, not a trigger condition.	2 / 3
Trigger Term Quality	Includes 'Jira', 'issues', 'projects', 'sprints', 'boards', 'comments', 'users' which are relevant keywords users might say. However, it misses common variations like 'tickets', 'backlog', 'story points', 'assign', 'create issue', or 'Jira board'. Also 'Rube MCP (Composio)' is technical jargon unlikely to appear in user requests.	2 / 3
Distinctiveness Conflict Risk	The description is clearly scoped to Jira via a specific MCP integration (Rube/Composio), making it highly distinctive and unlikely to conflict with other skills. The combination of 'Jira' and 'Rube MCP (Composio)' creates a clear niche.	3 / 3
	Total	9 / 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 reference skill with clear workflow sequencing and good structural organization. Its main weaknesses are the lack of concrete invocation examples (showing actual tool calls with real parameter values) and some redundancy across sections. The content would benefit from being more concise by deduplicating pitfalls and either providing executable examples or splitting detailed reference material into separate files.

Suggestions

Add at least one concrete, copy-paste-ready MCP tool invocation example per core workflow showing actual parameter values (e.g., a full RUBE_SEARCH_TOOLS call followed by a JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST call with real parameters).

Consolidate the repeated pitfalls about custom field IDs and account IDs into the single 'Known Pitfalls' section and remove duplicates from individual workflow sections.

Move the JQL syntax reference and quick reference table into separate bundle files (e.g., JQL_REFERENCE.md, TOOLS_REFERENCE.md) and link to them from the main skill to reduce 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 the quick reference table partially duplicates information already covered in the workflow sections. Some sections like 'Manage Comments' are thin enough to fold into a table. The JQL syntax section explains basic operators Claude already knows.	2 / 3
Actionability	The skill provides specific tool names, parameter names, and JQL examples, which is good. However, there are no executable code/command examples showing actual MCP tool invocations with concrete parameter payloads. The guidance stays at the level of listing tool names and parameters rather than showing copy-paste-ready invocation patterns.	2 / 3
Workflow Clarity	Each workflow has a clear numbered sequence with prerequisite/required/optional annotations, explicit tool ordering, and pitfall warnings. The setup section includes a validation checkpoint (confirm ACTIVE status before proceeding). The pagination pattern includes a clear loop condition. The workflows are well-sequenced with logical dependencies.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections and a quick reference table, but it's a monolithic file with no bundle files to offload detail into. The JQL syntax reference, the full quick reference table, and the detailed workflow sections could benefit from being split into separate referenced files. For a standalone file, it's reasonably structured but long.	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: davepoon/buildwithclaude
Commit: 74c7031

Reviewed: about 18 hours 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.