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. Part of the skills-for-java project

Quality

71%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

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 communicates what the skill does (Jira CLI operations including installation verification, configuration, issue listing, and fetching details) and when to use it. It includes natural trigger terms, specific actions, and a distinctive niche. The only minor note is the trailing 'Part of the skills-for-java project' which adds context but isn't critical for skill selection.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: verify installation, configure Jira Cloud access, list issues by JQL as markdown tables, fetch issue descriptions and comments for analysis. Also describes the interactive install gate behavior.	3 / 3
Completeness	Explicitly answers both what (verify installation, configure access, list issues, fetch descriptions/comments) and when ('Use when you need the Jira CLI') with a clear 'Use when...' clause at the start.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'Jira', 'jira', 'JQL', 'issues', 'comments', 'Jira Cloud', 'markdown tables'. These cover common variations of how users would reference Jira-related tasks.	3 / 3
Distinctiveness Conflict Risk	Clearly scoped to the Jira CLI tool specifically, with distinct triggers like 'jira', 'JQL', 'Jira Cloud', and the specific install gate behavior. Unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Implementation

42%

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

The skill has good structure and appropriate progressive disclosure with a clear reference to detailed documentation. However, it critically lacks actionable, executable examples—no concrete commands, JQL examples, or expected output formats are shown. The interactive gate concept is well-communicated but repeated too many times across sections.

Suggestions

Add concrete, executable command examples for key operations: e.g., `jira issue list --plain`, `jira issue list -q 'project = PROJ AND status = Open'`, `jira issue view PROJ-123 --comments 50`

Include an example of the expected markdown table output format so Claude knows exactly how to render issue lists

Add a numbered workflow with explicit validation steps, e.g., check `jira version` exit code, verify `jira me` returns valid user before proceeding to issue commands

Consolidate the repeated interactive gate instructions into a single, prominent section to reduce redundancy

Dimension	Reasoning	Score
Conciseness	The skill has some redundancy—the interactive gate concept is repeated multiple times (intro paragraph, constraints section, and 'What is covered' section). The 'What is covered' bullet list partially duplicates the constraints section. However, it's not excessively verbose and doesn't explain concepts Claude already knows.	2 / 3
Actionability	The skill provides no executable commands or code examples. It mentions commands like `jira version` and `jira configure` but never shows actual usage with arguments, expected output, or concrete examples of JQL queries, markdown table formatting, or issue creation commands. Everything is described abstractly rather than instructed concretely.	1 / 3
Workflow Clarity	There is a clear high-level sequence (check install → configure → list/query → deep read), and the interactive gate is well-emphasized. However, the steps lack explicit validation checkpoints, concrete commands at each step, and there's no feedback loop for error recovery (e.g., what to do if configuration fails or JQL returns errors).	2 / 3
Progressive Disclosure	The skill provides a clear overview with well-signaled one-level-deep reference to the detailed guide at references/044-planning-jira.md. The SKILL.md stays at summary level and delegates details appropriately.	3 / 3
	Total	8 / 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: 9ec21dd

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.