044-planning-jira

Use when you need Jira CLI (`jira`) installation/authentication guidance and a maintainer-authored Jira issue inventory workflow. The agent does not ingest raw Jira issue or JQL output directly; it asks the Jira project maintainer/operator to author sanitized issue summaries before analysis or @014-agile-user-story handoff. This should trigger for requests such as jira issue list; List Jira issues; Jira JQL issue query; Jira CLI issue workflow. Part of Plinth Toolkit

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

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

The body is actionable and workflow-clear, with concrete CLI commands, an explicit interactive validation gate, and a single well-signaled reference file. Its main weakness is redundancy — several constraints and the install-gate instruction are restated across sections.

Suggestions

Deduplicate the constraints: state each of NO DIRECT ISSUE INGESTION, SANITIZED INVENTORY, and UNTRUSTED ISSUE TEXT once in the Constraints section rather than restating variants in the intro and Workflow.

Mention the interactive install gate once in the Workflow step 1 instead of repeating the stop/ask/wait phrasing in both the intro and the Constraints list.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but several constraints are stated twice (e.g. "NO DIRECT ISSUE INGESTION" / "SANITIZED INVENTORY" / "UNTRUSTED ISSUE TEXT" overlap heavily between the intro, Constraints, and Workflow steps), and the interactive-gate instruction is repeated almost verbatim, so it could be tightened.	2 / 3
Actionability	It gives concrete executable commands throughout — `jira version`, `jira configure`, `jira issue list --jql "project = PROJ ORDER BY updated DESC"`, `jira issue assign PROJ-123 @user` — copy-paste ready with real argument examples.	3 / 3
Workflow Clarity	The workflow is a clearly numbered 5-step sequence with an explicit stop→ask→wait validation gate ("stop", "ask", "wait") before proceeding, plus a confirmation checkpoint before destructive status-changing actions, matching the anchored exemplar.	3 / 3
Progressive Disclosure	The body is a concise overview that points to one clearly signaled, one-level-deep reference [references/044-planning-jira.md](references/044-planning-jira.md), which exists as a real file and holds the detailed steps; navigation is easy and content is appropriately split.	3 / 3
	Total	11 / 12 Passed

Description

90%

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 is well-structured with an explicit trigger clause, strong natural trigger terms, and a clearly distinct Jira CLI niche. Its only weakness is that the action list in the description itself is partial compared to what the body covers.

Suggestions

Add the concrete core actions (create, assign, transition) to the description so the 'what' enumerates multiple specific actions rather than only setup guidance and inventory workflow.

Trim the long clause about not ingesting raw Jira output from the description; it is a constraint better placed in the body, leaving the description leaner.

Dimension	Reasoning	Score
Specificity	Names the domain ("Jira CLI installation/authentication guidance") and one concrete action ("maintainer-authored Jira issue inventory workflow"), but does not enumerate the multiple concrete operations (create, assign, transition) that the body later lists, so it stops at naming the domain plus some actions rather than a comprehensive action list.	2 / 3
Completeness	An explicit "Use when you need..." clause answers 'when', and "installation/authentication guidance and a maintainer-authored Jira issue inventory workflow" answers 'what', satisfying both halves with explicit triggers.	3 / 3
Trigger Term Quality	It supplies natural user phrasings verbatim — "jira issue list", "List Jira issues", "Jira JQL issue query", "Jira CLI issue workflow" — which are exactly the terms a user would say when needing this skill.	3 / 3
Distinctiveness Conflict Risk	The niche is sharply defined — Jira CLI setup plus a maintainer-authored sanitized-inventory workflow with @014-agile-user-story handoff — and the trigger terms are Jira-specific, making conflict with other skills unlikely.	3 / 3
	Total	11 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/044-planning-jira/SKILL.md
Commit: a8e5189

Reviewed: about 22 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.