CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/bug-tracker-workflow

Use when defect counts or reports are wrong (missing top-severity bugs, fixed items counted as new, unmerged duplicates) or bug filing and transitions need automating. One workflow for Jira, Linear, GitHub Issues and Azure DevOps: dedupe before filing, severity vs priority, lifecycle and CI filing.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Overview
Quality
Evals
Security
Files

Quality

Content

81%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 strong, tracker-agnostic workflow body with executable code and exemplary validation discipline around batch and destructive operations. The main improvements are tightening the redundancy between the overview table and the "Other trackers" section, defining the add_comment/timestamp helpers, and directly linking the two orphaned reference files.

Suggestions

Define add_comment and timestamp (or inline them) in the idempotent-creation example, and either ship scripts/file-jira-bug.py in the bundle or rephrase the CI section to say Claude writes it from the helpers above.

Cut the overlap between the overview table and the "Other trackers" section — keep the table as the router and reduce the section to one line per tracker, or fold its per-platform details entirely into the reference files.

Add direct links to references/taxonomy.md and references/tracker-vocabulary-map.md in the References section so every bundle file is discoverable from SKILL.md in one hop.

DimensionReasoningScore

Conciseness

Efficient throughout — assumes Claude's competence (never explains what Jira, REST, or CI are) and keeps rules to terse bullets — but the "Other trackers" section re-summarizes what the overview table already routes to, and the References section repeats links already given inline, so a trim would reach the lean 5 anchor.

4 / 5

Actionability

Mostly executable guidance: complete, copy-paste-ready auth, create_bug, transition, search_jql, dedupe, and bulk-transition code plus CI YAML. Minor gaps keep it from 5: add_comment and timestamp are called but never defined, and scripts/file-jira-bug.py is referenced in the CI wiring yet no scripts/ directory exists in the bundle.

4 / 5

Workflow Clarity

Clear sequences with explicit validation checkpoints and fix-and-retry feedback loops on every risky operation: dedupe search must "return 0 open matches before create_bug fires" with fail-closed on search errors; bulk transitions are gated behind a DRY_RUN flag with "assert the dry-run count and keys match" before applying; CI filing verifies 2xx + non-empty key with per-status recovery (fix payload on 400, back off on 429). The batch-operation cap at 3 does not apply because validation is present.

5 / 5

Progressive Disclosure

Good structure: an overview table routing each tracker to its one-level-deep deep dive, a single worked platform inline, and classification/lifecycle delegated to references — all six directly referenced files exist in the bundle. Minor gaps versus the 5 anchor: taxonomy.md and tracker-vocabulary-map.md are only reachable via sibling links (never linked from SKILL.md itself), and the "Other trackers" section partially duplicates the overview table's routing.

4 / 5

Total

17

/

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 well-crafted description with an explicit 'Use when' clause containing concrete, naturally-spoken trigger phrases and a clear multi-platform 'what' statement. Trigger coverage is strong but misses a few common synonyms (tickets, triage), and the operation list is slightly telegraphic.

DimensionReasoningScore

Specificity

Lists several concrete operations — "dedupe before filing", "bug filing and transitions", "CI filing" — across four named platforms, but "severity vs priority, lifecycle and CI filing" reads as compressed topic labels rather than fully described actions, so it falls short of the comprehensive 5 anchor.

4 / 5

Completeness

Explicitly answers both: "Use when defect counts or reports are wrong (missing top-severity bugs, fixed items counted as new, unmerged duplicates) or bug filing and transitions need automating" gives concrete when-triggers, and "One workflow for Jira, Linear, GitHub Issues and Azure DevOps: dedupe before filing..." states what it does. Uses third person with no fluff.

5 / 5

Trigger Term Quality

Strong natural terms — "bug", "defect", "duplicates", "top-severity", "transitions", plus all four platform names (Jira, Linear, GitHub Issues, Azure DevOps) — but common variations users would say such as "tickets", "triage", "backlog", or "issue tracker" are missing, matching the 4 anchor (good coverage, a few natural terms missing) rather than comprehensive.

4 / 5

Distinctiveness Conflict Risk

Clear niche — cross-tracker bug lifecycle automation with specific trigger failure modes (wrong defect counts, unmerged duplicates, fixed items counted as new) — that is minimally likely to fire for unrelated skills; not the 4 anchor because the overlap with adjacent QA/test-reporting skills is negligible given the bug-count/dedupe/filing trigger framing.

5 / 5

Total

18

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Reviewed

On this page