jira-management

Create and update Jira issues, epics, and sprints; manage backlog and sprint transitions. Use when you say: 'create a ticket', 'open a story', 'link an epic', 'start a sprint', or 'search the backlog'.

Quality

90%

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

Quality

Content

92%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.

A tightly written, token-efficient body that packs project-specific gotchas, conventions, ready-to-use JQL, and a validated session workflow into about 30 lines. The sole weakness is that the actual Jira create/update/transition call syntax is never shown, leaving minor gaps between the concrete conventions and their execution.

Dimension	Reasoning	Score
Conciseness	The ~30-line body is lean and assumes Claude's competence — it contains no explanation of what Jira is or how issue trackers work, and every line carries project-specific knowledge (workflow gotchas, summary format, JQL, session flow). Only the one-line OpenCastle banner is non-instructional, which is not enough to drop below the anchor-5 fit.	5 / 5
Actionability	Mostly executable guidance: a copy-paste JQL block, exact summary-format examples ("[Schema] Add priceRange field"), required description fields, and a concrete completion checklist. However, the actual create/update/transition invocation syntax is never shown and "project = PROJ" is a placeholder the reader must substitute from jira-config.md — minor gaps that fit anchor 4 rather than the fully copy-paste-ready anchor 5.	4 / 5
Workflow Clarity	The session flow is explicitly sequenced ("query in-progress work first → decompose into issues → link dependencies → transition before/after each → on completion verify all Epic issues Done, run build/lint/test, close the Epic") with explicit validation steps ("A create call is only successful if it returns an issue key") and a bounded feedback loop ("retry once, then stop"), matching the anchor-5 pattern; the destructive/batch cap does not apply because validation is present.	5 / 5
Progressive Disclosure	This is an under-50-line, single-file skill with no external reference files needed; its sections (Gotchas, Conventions, JQL) are well organized and it points one level deep to a clearly signaled config file ("Project keys, workflow state IDs, and board config: .opencastle/project/jira-config.md"), which the rubric's simple-skill guideline scores at 5.	5 / 5
	Total	19 / 20 Passed

Description

87%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.

A strong description that explicitly answers both what the skill does and when to use it, with natural, entity-specific trigger phrases and a distinct Jira niche. The only flaws are the second-person "Use when you say" construction (which costs it a specificity point per the rubric) and a few missing common trigger terms like assign, comment, and close.

Suggestions

Rewrite the trigger clause in third person, e.g. "Use when the user asks to 'create a ticket', 'open a story', ...", to avoid the second-person voice penalty.

Add a few common natural trigger terms such as 'assign an issue', 'add a comment', or 'close a ticket' to the when-clause for fuller trigger coverage.

Dimension	Reasoning	Score
Specificity	"Create and update Jira issues, epics, and sprints; manage backlog and sprint transitions" lists multiple specific concrete actions with near-comprehensive coverage of the task-management domain (an anchor-5 list), but the second-person phrasing "Use when you say" incurs the rubric's mandated 1-point deduction on this dimension.	4 / 5
Completeness	Both parts are explicit: a clear 'what' ("Create and update Jira issues, epics, and sprints; manage backlog and sprint transitions") and a concrete 'when' clause ("Use when you say: 'create a ticket', 'open a story'...") with concrete trigger phrases, exactly matching the anchor-5 pattern.	5 / 5
Trigger Term Quality	Trigger phrases like 'create a ticket', 'open a story', 'link an epic', 'start a sprint', or 'search the backlog' are natural phrasings covering synonyms across entity types (ticket/story/epic/sprint/backlog), but a few common natural terms (assign, comment, resolve/close) are missing — good coverage rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	The description names a specific tool (Jira) with a clear niche and distinct entity-specific triggers ('link an epic', 'start a sprint'), giving minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 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: monkilabs/opencastle
Path: src/orchestrator/plugins/jira/SKILL.md
Commit: c0f4566

Reviewed: 1 day 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.