jira-sync

Use this skill when you want to sync GitHub activity with Jira — create tickets from issues, link PRs to tickets, update status from commits, or generate sprint summaries.

Quality

84%

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

76%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 body is highly actionable and concise, led by executable code with clean section structure. Its main weaknesses are the absence of validation/verification steps for state-changing Jira operations and a hardcoded model version that will age.

Suggestions

Add verification after write operations — e.g. re-fetch the created issue to confirm the ticket key exists, or check transition_issue actually moved the status — to satisfy the validation requirement for destructive/batch workflows and lift workflow_clarity above 3.

Replace the hardcoded 'claude-opus-4-6' with a current model identifier or a configurable variable, or move version guidance to a dedicated section, to avoid stale time-sensitive information.

Consider extracting the longer code blocks (Sprint Summary Generator, GitHub Issue→Jira) into a reference file referenced one level deep, to improve progressive_disclosure for a skill that exceeds the simple-skill line count.

Dimension	Reasoning	Score
Conciseness	The body is lean and mostly executable code with minimal prose, assuming Claude's competence; however the hardcoded model version 'claude-opus-4-6' (appearing twice) is time-sensitive and will go stale, which the guidelines penalize, pulling it just below a 5.	4 / 5
Actionability	Provides fully executable, copy-paste-ready Python for the core cases (create_ticket, transition_ticket, sync_github_issue_to_jira, generate_sprint_summary) with real API calls and concrete env setup, matching the score-5 anchor.	5 / 5
Workflow Clarity	Functions are presented clearly but the skill performs state-changing external operations (creating and transitioning Jira tickets, batch sync) with no validation or verification checkpoints that the writes succeeded; per the rubric cap, destructive/batch operations without validation cannot exceed 3.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections (Overview, Setup, Jira Client, sync, Sprint Summary, Quick Reference) with no nested references and no bundle files; it is slightly longer than the under-50-line simple-skill threshold, so it sits at 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 concisely states both the capability and the trigger condition with concrete, domain-specific actions. Trigger-term coverage is good though a couple of natural synonyms could broaden it.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions — 'create tickets from issues', 'link PRs to tickets', 'update status from commits', 'generate sprint summaries' — giving comprehensive coverage of the GitHub-Jira sync domain, matching the score-5 anchor.	5 / 5
Completeness	Explicitly answers both what ('sync GitHub activity with Jira — create tickets from issues, link PRs to tickets, update status from commits, or generate sprint summaries') and when ('Use this skill when you want to sync GitHub activity with Jira') with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Natural terms like 'sync GitHub activity with Jira', 'tickets', 'issues', 'PRs', 'commits', and 'sprint summaries' align with what users would say, but a few synonyms (e.g. 'pull requests' alongside PRs) are missing, fitting the score-4 anchor.	4 / 5
Distinctiveness Conflict Risk	The GitHub-Jira sync niche has distinct triggers and minimal overlap risk with other skills, matching the score-5 anchor for a clear niche with distinct triggers.	5 / 5
	Total	19 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing, 1 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: ProwlrBot/prowlr-marketplace
Path: external/goose-recipes/jira-sync/SKILL.md
Commit: 32f0050

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