CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/jira-bug-workflow-runner

Jira Cloud bug workflow runner using the REST API v3: issue creation with an ADF description, runtime transition lookup and apply, JQL search for triage queues and duplicate detection, severity/priority field updates, label-based classification (severity/priority/regression), and idempotent CI-driven filing from JUnit XML test failures. Use when the target tracker is Jira Cloud and the task involves Jira lifecycle states (create, triage, transition, close). Distinct from a platform-agnostic event-driven CI defect filer, and from linear-bug-workflow-runner / github-issues-bug-workflow for other trackers.

79

Quality

99%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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

The body is lean and actionable with executable code, explicit validation checkpoints on risky batch operations, and well-structured one-level-deep references. It assumes Claude's competence and adds only non-obvious domain knowledge. No changes needed.

DimensionReasoningScore

Conciseness

The body is dense with executable, domain-specific content (ADF requirement, runtime transition lookup, idempotency, JQL injection) and avoids explaining concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Provides fully executable Python helpers (auth, create_bug, get_transitions, transition, search_jql, create_or_attach), CI YAML, and curl+jq snippets that are copy-paste ready.

3 / 3

Workflow Clarity

CI filing and bulk-transition workflows include explicit 'Verify:' checkpoints, dry-run gating, fail-closed behavior on search errors, and HTTP-code-specific recovery — clear validation feedback loops for risky batch operations.

3 / 3

Progressive Disclosure

A concise overview points to a single, well-signaled one-level reference (references/jira-rest-api.md, which exists and holds custom-field/update/parsing detail), with a References section organizing siblings and consumers.

3 / 3

Total

12

/

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.

The description is specific, trigger-rich, complete, and clearly distinct from sibling skills. It uses third-person voice and an explicit 'Use when' trigger, with no vague fluff. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'issue creation with an ADF description, runtime transition lookup and apply, JQL search for triage queues and duplicate detection, severity/priority field updates' — rather than vague language.

3 / 3

Completeness

Explicitly answers both 'what' (the enumerated Jira operations) and 'when' via a clear 'Use when...' clause, satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

'Use when the target tracker is Jira Cloud and the task involves Jira lifecycle states (create, triage, transition, close)' covers natural terms a user would say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

An explicit 'Distinct from...' clause differentiates it from a platform-agnostic CI filer and names sibling trackers, giving it a clear niche unlikely to conflict.

3 / 3

Total

12

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents