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

73%

Does it follow best practices?

Impact

95%

1.97x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/jira-automation/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

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

The body is a well-structured, actionable reference for Jira automation via Rube MCP, with concrete tool sequences, parameters, pitfalls, and a useful quick-reference table. Main gaps are minor: repeated pitfall content, no post-operation validation after create/edit/move actions, and an inline tool catalog that could live in a separate reference file.

Suggestions

Add verification steps after mutating operations (e.g., re-fetch the issue with JIRA_GET_ISSUE after CREATE/EDIT, or confirm sprint membership after MOVE_ISSUE_TO_SPRINT) to close the workflow-validation gap.

De-duplicate the custom-field and pagination guidance, keeping each pitfall in one place (the Known Pitfalls section) and referencing it from workflows.

Move the 19-row Quick Reference tool catalog into a references/ file (e.g., TOOL_REFERENCE.md) and keep only the highest-frequency tools inline.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational — tool sequences, exact parameters, and pitfalls with no explanation of concepts Claude already knows — but there is noticeable duplication: custom-field ID guidance appears in workflows 1, 2, and the Known Pitfalls section, and pagination is explained twice. This fits 'efficient; minor instances that could be trimmed' rather than the lean 5.	4 / 5
Actionability	Guidance is concrete and executable for an MCP-tool skill: exact tool slugs, parameter names with examples (e.g., 'project = PROJ AND status = "In Progress"'), and a quick-reference table. It falls short of fully copy-paste-ready 5 because there are no complete example calls (e.g., a sample ADF description body or a fully populated CREATE_ISSUE argument set).	4 / 5
Workflow Clarity	Each workflow has a clearly numbered tool sequence with [Required]/[Prerequisite]/[Optional] markers, and setup includes an explicit validation checkpoint ('Confirm connection status shows ACTIVE before running any workflows') plus a pagination feedback loop. It is not a 5 because create/edit/move operations (including batch-style MOVE_ISSUE_TO_SPRINT with an 'issues' list) lack post-operation verification steps.	4 / 5
Progressive Disclosure	The single file is well organized with clear section headers, per-task workflows, and one clearly signaled external reference (the Composio toolkit docs link); no bundle files exist so there are no nested or buried references. It is not a 5 because at ~180 lines with a 19-row inline tool catalog, the Quick Reference table functions as an inlined API reference that would fit better in a separate reference file.	4 / 5
	Total	16 / 20 Passed

Description

61%Weight 40%Scale 1-5

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 distinct niche (Jira automation via Rube MCP) with good domain-object keywords, but it lists objects rather than concrete actions and completely lacks a 'when to use' trigger clause. Adding an explicit 'Use when...' sentence and one or two concrete verbs (e.g., 'create and search issues, manage sprints') would raise it substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Jira, tickets, sprints, boards, or asks to create/search/assign issues.'

Replace the generic 'Automate Jira tasks' with concrete actions such as 'Create, search, and edit issues; manage sprints, boards, comments, and project roles.'

Include common user synonyms like 'tickets', 'backlog', 'epic', and 'JQL' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the Jira domain broadly ("issues, projects, sprints, boards, comments, users") but offers only one generic action verb ("Automate Jira tasks") with no concrete operations like creating, editing, or searching issues, matching the anchor for 1-2 concrete actions without comprehensiveness. It is not a 4 because no specific actions are enumerated, and not a 2 because the domain object coverage is substantial.	3 / 5
Completeness	The 'what' is reasonably clear (automating Jira operations across issues, projects, sprints, boards, comments, users), but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. The second sentence ('Always search tools first for current schemas') is usage advice for the model, not a 'when to use this skill' trigger.	3 / 5
Trigger Term Quality	Natural keywords users would say are present ("Jira", "issues", "sprints", "boards", "comments"), giving good coverage, but common synonyms and variations like "tickets", "epic", "backlog", or "JQL" are missing. This fits the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	"Jira" plus "Rube MCP (Composio)" carves out a clear niche that is unlikely to trigger for unrelated skills, fitting 'mostly distinct; minor overlap risk'. It is not a 5 because there are no explicit trigger phrases and it could softly overlap with a generic project-management or issue-tracking skill.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: davepoon/buildwithclaude
Path: plugins/all-skills/skills/jira-automation/SKILL.md
Commit: 10bfc43

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