Name: jira
Rating: 59.2 (1 reviews)
Author: membranedev

jira

Jira integration. Manage project management and ticketing data, records, and workflows. Use when the user wants to interact with Jira data.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/jira/SKILL.md

Quality

Content

65%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 highly actionable with executable commands and a clear connection state machine, but it over-explains Jira basics, lacks validation steps around destructive operations, and inlines a large action catalogue that would benefit from a separate reference file.

Suggestions

Add a validation/confirmation checkpoint before destructive actions (e.g. verify the issue key with get-issue and confirm with the user before running delete-issue or transition-issue).

Move the Popular actions table into a references/ACTIONS.md file and link to it from a short overview so the SKILL.md body stays lean.

Remove the introductory paragraph defining what Jira is and trim 'so you can focus on the integration logic rather than auth plumbing' to assume Claude's familiarity.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with command tables and code blocks, but the opening paragraph explaining what Jira is ('Jira is a project management and issue tracking tool...') and phrasing like 'so you can focus on the integration logic rather than auth plumbing' pad text Claude does not need.	3 / 5
Actionability	Copy-paste-ready commands throughout (connection ensure, action list/run, request) with flag tables and a 20-row action catalogue keyed by action id, covering the common integration cases fully.	5 / 5
Workflow Clarity	The connection flow is well-sequenced with state polling and feedback loops, but destructive actions (delete-issue, delete-comment, transition-issue) are presented with a bare 'action run' command and no validation or confirmation checkpoint, capping this dimension at 3.	3 / 5
Progressive Disclosure	No bundle files exist and everything is inlined; the 20-row Popular actions table and proxy-options table are content that could live in a separate reference file, and there are no one-level-deep references to signal navigation to.	3 / 5
	Total	14 / 20 Passed

Description

73%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 clearly identifies the Jira niche and includes an explicit use-when clause, making it distinct and complete. It is weakened by generic 'manage... data/records/workflows' phrasing that lists no concrete Jira actions and omits common trigger synonyms like 'issues' or 'JQL'.

Suggestions

Replace abstract verbs with concrete Jira actions, e.g. 'Create and update issues, transition them through workflows, and add comments'.

Add common user trigger terms such as 'Jira issues', 'JQL', 'sprints', and 'boards' to the Use-when clause.

Tighten the trigger to be more specific than 'interact with Jira data', e.g. 'Use when the user wants to read, search, create, or update Jira issues and projects'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Jira integration', 'project management and ticketing') but the actions are abstract nouns ('Manage... data, records, and workflows') rather than concrete Jira verbs like create/transition/comment on issues.	3 / 5
Completeness	Provides both a 'what' ('Manage project management and ticketing data, records, and workflows') and an explicit 'when' ('Use when the user wants to interact with Jira data'), though the trigger is somewhat generic.	4 / 5
Trigger Term Quality	Good natural keywords ('Jira', 'project management', 'ticketing', 'interact with Jira data') but misses common variations users say such as 'issues', 'JQL', 'sprints', or 'boards'.	4 / 5
Distinctiveness Conflict Risk	'Jira integration' is a clear, narrowly-scoped niche with a distinct product-name trigger, so conflict with other skills is minimal.	5 / 5
	Total	16 / 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: membranedev/application-skills
Path: skills/jira/SKILL.md
Commit: f484c82

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