044-planning-jira

Use when you need the Jira CLI (`jira`) to verify installation, configure Jira Cloud access, list issues (all or by JQL) as markdown tables, and fetch issue descriptions and comments for analysis. Uses an interactive install gate - if `jira` is missing, ask whether to show installation guidance before any issue commands. This should trigger for requests such as jira issue list; List Jira issues; Jira JQL issue query; jira issue view comments; Jira CLI issue workflow. Part of cursor-rules-java project

Quality

67%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/044-planning-jira/SKILL.md

Quality

Discovery

100%

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

This is a strong skill description that clearly specifies concrete capabilities (installation verification, Jira Cloud configuration, issue listing via JQL, fetching comments), provides explicit trigger guidance with natural user phrases, and occupies a distinct niche around the Jira CLI tool. The description is well-structured and comprehensive, covering both what the skill does and when it should be selected.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: verify installation, configure Jira Cloud access, list issues as markdown tables, fetch issue descriptions and comments for analysis, and describes the interactive install gate behavior.	3 / 3
Completeness	Clearly answers both 'what' (verify installation, configure access, list issues, fetch descriptions/comments) and 'when' with an explicit 'Use when' clause at the start and a 'This should trigger for requests such as...' section providing concrete trigger examples.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'jira issue list', 'List Jira issues', 'Jira JQL issue query', 'jira issue view comments', 'Jira CLI issue workflow', plus terms like 'JQL', 'Jira Cloud', and 'jira' CLI references.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — focuses specifically on the Jira CLI (`jira`) for Jira Cloud issue operations, with clear niche triggers like 'JQL', 'jira issue view comments', and 'Jira CLI'. Unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Implementation

35%

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

This skill establishes a reasonable workflow structure with a good interactive gate pattern, but critically lacks actionable, executable content — no actual CLI commands, flags, output examples, or markdown table formats are shown. The content is largely descriptive rather than instructive, repeating the same concepts across multiple sections without adding concrete value. The reference to an external file suggests progressive disclosure intent, but the SKILL.md body doesn't provide enough standalone utility.

Suggestions

Add concrete, executable CLI command examples for each workflow step (e.g., `jira issue list --plain`, `jira issue list -q'project = MYPROJ AND status = Open'`, `jira issue view PROJ-123 --comments 50`).

Include a sample markdown pipe table showing expected output format for issue listings, so Claude knows exactly how to render results.

Remove the redundant 'What is covered' section — the workflow and constraints already convey this information.

Add error handling examples: what does a failed `jira version` look like, what does a misconfigured CLI return, and how to recover from common errors.

Dimension	Reasoning	Score
Conciseness	The content has some redundancy — the interactive gate concept is repeated across the intro, constraints, and workflow sections. The 'What is covered' bullet list largely duplicates the workflow section. However, it's not excessively verbose and doesn't explain concepts Claude already knows.	2 / 3
Actionability	There are no concrete commands, executable code examples, or copy-paste ready snippets. The workflow steps describe what to do abstractly ('Check jira version', 'Retrieve issues using basic listing or JQL filters') without showing actual CLI invocations, flags, or output formats. The skill essentially describes rather than instructs.	1 / 3
Workflow Clarity	The workflow has a clear 5-step sequence with the interactive gate as step 1, which is good. However, there are no validation checkpoints beyond the initial install check, no error recovery/feedback loops for failed commands, and no explicit verification after configuration or issue operations.	2 / 3
Progressive Disclosure	The skill references a detailed file (references/044-planning-jira.md) for deeper guidance, which is good progressive disclosure structure. However, no bundle files were provided to verify the reference exists, and the SKILL.md body itself contains too much abstract description that could either be cut or moved to the reference file, while lacking the concrete quick-start content that should remain inline.	2 / 3
	Total	7 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/cursor-rules-java
Commit: ef4eba3

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.