jira

Search and manage Jira issues using JQL queries, create/update tickets, and manage workflows. Use when asked to find Jira tickets, check the backlog, manage sprints, track bugs, or work with Atlassian project management.

1.90x

Quality

83%

Does it follow best practices?

Impact

95%

1.90x

Average score across 2 eval scenarios

Securityby

Low

Low-risk findings worth noting

Quality

Content

75%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 well-structured CLI reference with fully executable commands, sensible setup-verification flow, and clean one-level-deep reference files. The main weakness is redundancy: the standalone Examples section and the duplicated check documentation restate content already present in the Commands section.

Suggestions

Replace the ~40-line inline Examples section with a pointer to references/examples.md, since it almost entirely restates commands already shown under Commands.

Merge the 'check' documentation: the Setup Verification section and the Commands 'check' entry describe the same validation twice — keep one with the full validation list and error-recovery guidance.

Use a consistent invocation form throughout; the Commands section uses "$SKILL_DIR/scripts/jira.py ..." while Examples uses a bare "jira ..." prefix, which is not directly executable as written.

Dimension	Reasoning	Score
Conciseness	The command reference is lean and assumes Claude's competence, but the ~40-line "Examples" section ("jira search 'assignee = currentUser()...'", "jira issue create...", "jira transitions do...") duplicates commands already shown in full under "Commands", and "check" is documented twice (Setup Verification and Commands). Anchor 3 fits: mostly efficient but includes unnecessary repetition that should be tightened, exceeding anchor 4's 'minor instances'.	3 / 5
Actionability	Fully executable, copy-paste-ready commands throughout ("$SKILL_DIR/scripts/jira.py search 'project = DEMO AND status = Open'", "issue create --project DEMO --type Story --summary 'New story' --parent EPIC-123") with per-subcommand argument lists covering the common cases, matching the level-5 anchor.	5 / 5
Workflow Clarity	A clear sequence (Install → Verify → Authenticate → Commands) with an explicit validation checkpoint and error-recovery guidance ("This will check: Python dependencies... If anything is missing, the check command will provide setup instructions"). Not level 5 because state-mutating operations like "transitions do" and "issue update" lack post-operation verification steps.	4 / 5
Progressive Disclosure	Well-signaled, verified, one-level-deep references (permissions.md, jql-reference.md, scriptrunner.md with Cloud-vs-ScriptRunner routing, from-file-format.md, advanced-commands.md, configuration.md) with a clear overview. Minor gap: the inline "Examples" section duplicates the role of references/examples.md, so content is not perfectly split — anchor 4 rather than 5.	4 / 5
	Total	16 / 20 Passed

Description

92%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 pairs a concrete, third-person capability statement with an explicit and specific 'Use when...' trigger clause. Trigger term coverage is broad (tickets, backlog, sprints, bugs, Atlassian) with only minor synonym gaps such as epics or kanban boards.

Dimension	Reasoning	Score
Specificity	"Search and manage Jira issues using JQL queries, create/update tickets, and manage workflows" lists multiple specific concrete actions in third person, comprehensively covering the skill's capabilities like the level-5 anchor example. No minor gaps in coverage that would place it at anchor 4.	5 / 5
Completeness	Explicitly answers both what ("Search and manage Jira issues using JQL queries, create/update tickets") and when ("Use when asked to find Jira tickets, check the backlog, manage sprints, track bugs...") with concrete trigger phrases, exactly matching the level-5 anchor structure.	5 / 5
Trigger Term Quality	Natural trigger phrases like "find Jira tickets", "check the backlog", "manage sprints", "track bugs", and "Atlassian" give good keyword coverage, but common variations such as "epics", "user stories", or "kanban/agile boards" are absent, fitting anchor 4 rather than anchor 5's comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	"Jira", "JQL", and "Atlassian" establish a clear niche with distinct triggers and minimal conflict risk with other skills, matching the level-5 anchor; nothing about the description is generic enough to overlap other skills.	5 / 5
	Total	19 / 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: odyssey4me/agent-skills
Path: skills/jira/SKILL.md
Commit: 666332c

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