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

53%

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 domain (Jira automation) and lists relevant entity types, giving it reasonable distinctiveness. However, it lacks concrete action verbs describing what operations are performed, and critically missing an explicit 'Use when...' clause that would help Claude know when to select this skill. The mention of 'Rube MCP (Composio)' is internal implementation detail that doesn't help with skill selection.

Suggestions

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

Replace entity-only listing with concrete action phrases, e.g., 'Create and update Jira issues, manage sprints and boards, add comments, assign users, search projects.'

Move implementation details like 'Rube MCP (Composio)' and 'always search tools first' to the skill body rather than the description, and use that space for user-facing trigger terms.

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 to 'always search tools first' is operational guidance 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 mention. However, it misses common action-oriented terms users would say like 'create ticket', 'assign issue', 'update sprint', 'JIRA board', or 'backlog'. Also 'Rube MCP (Composio)' is internal 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 tool (Rube/Composio), which creates a distinct niche. It's unlikely to conflict with other skills unless there's another Jira-related skill.	3 / 3
	Total	9 / 12 Passed

Implementation

50%

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-style skill that covers Jira operations comprehensively with clear workflow sequences and useful JQL examples. Its main weaknesses are the lack of concrete executable examples (actual tool call payloads), missing validation/error-recovery steps in workflows, and some redundancy across sections that inflates token usage. Adding example tool invocations with sample inputs/outputs and explicit verification steps would significantly improve it.

Suggestions

Add at least one concrete, complete example of an MCP tool invocation with actual input parameters and expected response structure (e.g., a full RUBE_SEARCH_TOOLS call followed by a JIRA_CREATE_ISSUE call with sample payload).

Add explicit validation/verification steps to workflows—e.g., after creating an issue, verify with GET_ISSUE; after moving to sprint, confirm the issue appears in the sprint.

Consolidate the repeated pitfalls about custom field IDs and account IDs into the 'Known Pitfalls' section only, removing duplicates from individual workflow sections to reduce token usage.

Consider splitting the JQL reference and quick reference table into a separate REFERENCE.md file to improve progressive disclosure and reduce the main file's length.

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 trimming would improve token efficiency.	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 payloads—everything remains at the level of listing tool slugs and parameter names without showing a complete call with example input/output.	2 / 3
Workflow Clarity	Workflows are clearly sequenced with labeled steps and prerequisite/required/optional annotations, which is helpful. However, there are no explicit validation checkpoints or error recovery loops—e.g., after creating an issue, there's no step to verify it was created correctly, and the setup flow lacks a retry/error handling path if connection fails.	2 / 3
Progressive Disclosure	The content is well-organized with clear sections and a quick reference table, but it's a long monolithic file (~170 lines) with no bundle files to offload detailed content like the full JQL reference or ADF format details. The repeated pitfalls and the comprehensive quick reference table could be split into separate reference files.	2 / 3
	Total	8 / 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: d065ead

Reviewed: 2 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.