jira

Manage Jira issues, boards, sprints, and projects via the jira-cli. Search, create, update, and transition issues directly from the command line.

Quality

81%

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

The canonical home for this skill is jira in jdrhyne/agent-skills

Quality

Content

93%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 content is an exemplary lean CLI reference: fully executable commands, sensible output-format guidance for scripting, and explicit confirmation checkpoints for destructive operations. The only gap is the absence of a post-setup verification step or error-recovery guidance.

Suggestions

Add a setup verification step, e.g. run `jira me` (or `jira project list`) after `jira init` to confirm authentication works before proceeding.

Include a brief note on the most common failure mode (expired/invalid API token) and how to recover from it.

Dimension	Reasoning	Score
Conciseness	A lean command reference with zero padding: no explanation of what Jira is, every line is an executable command, flag, or operational note. Assumes Claude's competence and every token earns its place, matching the 5 anchor.	5 / 5
Actionability	All commands are copy-paste ready with realistic placeholders (`jira issue create -p PROJECT -t "Task" -s "Summary" -b "Description"`, JQL examples) and cover the common cases across issues, sprints, boards, epics, and projects. Fully executable guidance per the 5 anchor.	5 / 5
Workflow Clarity	Setup is a clear 1-2-3 sequence, and the Notes section provides explicit checkpoints for destructive and batch operations ("Confirm with user before creating/editing/transitioning issues", "show what will change before executing"), so the missing-validation cap does not apply. Falls short of 5 because there is no verification that setup succeeded (e.g., a smoke-test command like `jira me`) and no error-recovery guidance.	4 / 5
Progressive Disclosure	The body is under 50 lines, self-contained with no external references needed, and organized into clear sections (Issues, Sprints, Boards, Epics, Projects, Output formats, Tips, Notes). Per the rubric's simple-skill exception, well-organized sections with no need for external references score 5.	5 / 5
	Total	19 / 20 Passed

Description

70%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 is concise, concrete, and clearly Jira-scoped with named actions and entities, making it highly distinguishable. Its main weakness is the missing 'when to use' clause and absent common synonyms like 'tickets' or 'JQL', which limits trigger matching and completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Jira, Jira tickets, sprints, or asks to create, update, or transition issues."

Include common user-facing synonyms such as "tickets", "backlog", "epics", and "JQL" in the description to improve trigger term coverage.

Mention one or two more high-frequency operations (e.g., assign, comment, JQL search) to round out capability coverage without adding length.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ("Search, create, update, and transition issues") across named entities ("issues, boards, sprints, and projects"), but coverage has minor gaps — common operations like assign, comment, and JQL queries are absent. It exceeds the 3 anchor (only 1-2 concrete actions) but does not match the comprehensive coverage of the 5 anchor.	4 / 5
Completeness	Has a clear 'what' ("Manage Jira issues, boards, sprints, and projects via the jira-cli" plus four concrete verbs) but no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric guideline. Not 4 because 'when' is entirely absent rather than merely implicit or underspecified.	3 / 5
Trigger Term Quality	Natural terms users would say are present ("Jira issues", "boards", "sprints", "projects"), but common synonyms and variations are missing — notably "tickets", "backlog", "epics", and "JQL". Good coverage per the 4 anchor rather than the comprehensive synonym coverage of the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	Explicitly scoped to Jira with the specific tool named ("via the jira-cli"), giving it a clear niche with distinct triggers and minimal conflict risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

81%

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 — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: bap-jorkim/agent-skills-fork-feb-25
Path: skills/jira/SKILL.md
Commit: f4ed46f

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