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 comprehensive and well-structured, 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.

The skill establishes a clear conceptual workflow with a well-defined interactive install gate pattern, but critically lacks actionable, executable content — no actual CLI commands with flags, no example outputs, and no markdown table format examples are shown. The content is moderately redundant, repeating the same concepts across multiple sections. Nearly all concrete guidance appears to be deferred to a reference file that cannot be verified.

Suggestions

Add concrete, executable CLI command examples for each workflow step (e.g., `jira issue list --plain --columns key,summary,status`, `jira issue view PROJ-123`, `jira issue list -q 'project=PROJ AND status="In Progress"'`)

Include at least one example of the expected markdown pipe table output format so Claude knows exactly how to render issue lists

Remove the duplicated 'What is covered' section — the workflow and constraints sections already cover this information, and the repetition wastes tokens

Add validation checkpoints with expected success/failure output patterns (e.g., what a successful `jira version` looks like vs. command not found)

Dimension	Reasoning	Score
Conciseness	The content has some redundancy — the interactive install gate is mentioned at least 4 times (intro, constraints, workflow, and 'What is covered' section). The 'What is covered' bullet list largely duplicates the workflow section. However, it avoids explaining basic concepts Claude already knows.	2 / 3
Actionability	There are no concrete commands, code examples, or executable snippets beyond mentioning `jira version` and `jira configure` by name. The workflow steps describe what to do abstractly ('Retrieve issues using basic listing or JQL filters') without showing actual CLI invocations, flags, or output formats. Everything is deferred to the reference file.	1 / 3
Workflow Clarity	The workflow has a clear 5-step sequence with a logical order and the interactive gate is well-emphasized. However, the steps lack concrete commands, validation checkpoints (e.g., what does a successful config check look like?), and error recovery/feedback loops for failed operations.	2 / 3
Progressive Disclosure	The skill references a single detailed file (references/044-planning-jira.md) which is good progressive disclosure structure, but no bundle files were provided to verify the reference exists or contains the promised detail. The SKILL.md itself is somewhat monolithic with repeated content that could be tightened, and the reference is only mentioned once at the very end rather than being signaled at relevant points throughout.	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: 3fa5789

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