jira

Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira workflow. Triggers on keywords like "jira", "issue", "ticket", "sprint", "backlog", or issue key patterns.

1.48x

Quality

—

Does it follow best practices?

Impact

95%

1.48x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

85%

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

A highly actionable, well-organized skill body with concrete commands, clear validation-gated workflows, and proper progressive disclosure into two real reference files. The only weakness is mild redundancy across the 'Before Any Operation', 'NEVER', and 'Safety' sections, which restate overlapping cautions.

Suggestions

Consolidate the overlapping cautionary content across 'Before Any Operation', 'NEVER', and 'Safety' so each risk is stated once, trimming redundant tokens.

In the 'Issue Key Detection' section, the MCP tool name 'mcp__atlassian__jira_get_issue' is inconsistent with the 'getJiraIssue' name used in the Quick Reference (MCP) table — align them to avoid confusion.

Dimension	Reasoning	Score
Conciseness	The body is largely lean — command tables and terse NEVER bullets assume Claude's competence and avoid explaining what Jira is — but the 'Before Any Operation', 'NEVER', and 'Safety' sections overlap on the same cautionary themes, adding some redundancy that could be tightened; not level 3 because of that repetition, not level 1 because it does not pad with concepts Claude already knows.	2 / 3
Actionability	Provides concrete, copy-paste-ready commands (`jira issue view ISSUE-KEY`) and named MCP tools, plus a concrete backend-detection procedure, matching the level-3 fully-executable anchor rather than the level-2 pseudocode anchor.	3 / 3
Workflow Clarity	Creating and updating workflows are clearly sequenced with explicit validation checkpoints — 'Always fetch the issue first', 'Get approval before updating', 'Verify updates after applying' — including feedback loops for destructive/batch operations, matching the level-3 anchor.	3 / 3
Progressive Disclosure	Clear overview with two one-level-deep, verified-real references (references/commands.md, references/mcp.md) that are well-signaled in tables and a 'Deep Dive' section with explicit load/skip criteria, matching the level-3 anchor.	3 / 3
	Total	11 / 12 Passed

Description

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.

A strong, well-structured description that clearly states concrete capabilities, provides natural trigger terms including a distinctive issue-key pattern, and explicitly answers both what the skill does and when to use it. No substantive weaknesses to address.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'create/view/update issues', 'check sprint status', 'manage their Jira workflow' — matching the level-3 anchor listing specific actions, rather than the level-2 anchor that names only a domain.	3 / 3
Completeness	Explicitly answers both what (create/view/update issues, sprint status) and when via the 'Use when the user mentions Jira issues' clause, matching the level-3 anchor with explicit triggers; not level 2 because the when is explicit, not implied.	3 / 3
Trigger Term Quality	Good coverage of natural terms users would say — 'jira', 'issue', 'ticket', 'sprint', 'backlog', and the 'PROJ-123' issue-key pattern — matching the level-3 anchor; not level 2 because common variations are not missing.	3 / 3
Distinctiveness Conflict Risk	Jira-specific triggers like the 'PROJ-123' issue-key pattern, 'sprint', and 'backlog' carve a clear niche unlikely to conflict with other skills, matching the level-3 anchor.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 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

	Total	14 / 16 Passed

Repository: jdrhyne/agent-skills
Commit: 292843f

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