CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/github-issues-bug-workflow

Author and run GitHub Issues bug workflows via REST API (2026-03-10): issue creation, state changes (open / closed with `state_reason`), label-based severity/priority classification, and comment attachment. Covers `POST /repos/{owner}/{repo}/issues`, `PATCH` for `state_reason` transitions (completed / not_planned / duplicate / reopened), and label conventions for GitHub's binary open/closed model; Projects v2, `gh` CLI, and CI wiring live in references/. Use when programmatically managing the GitHub Issues bug lifecycle; for the same workflow on another tracker use azuredevops-bug-workflow, jira-bug-workflow-runner, or linear-bug-workflow-runner.

80

Quality

100%

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, executable, and well-structured: complete code functions, explicit validation/feedback loops around destructive close and batch dedupe operations, and a clean one-level split into the reference file. It is a strong, production-quality skill body.

DimensionReasoningScore

Conciseness

The body is code- and table-forward with minimal prose, assumes Claude's competence, and avoids explaining basic concepts; the few framing sentences (Overview state model, API-version rationale, Limitations) are justified context rather than fluff, so it does not fall to the score-2 "mostly efficient but could be tightened" level.

3 / 3

Actionability

It provides complete, executable Python functions (create_bug, close, reopen, search_issues, add_comment, create_or_attach) with real endpoints, headers, and payloads that are copy-paste ready, matching the score-3 anchor; it is not pseudocode or abstract description.

3 / 3

Workflow Clarity

A numbered "How to use" sequence and a worked idempotent example pair with explicit validation checkpoints — close() asserts the landed state, and the Verify note instructs asserting title matches before attaching/closing then skipping, logging, and re-running dedupe — a real verify/fix/retry feedback loop for destructive and batch operations.

3 / 3

Progressive Disclosure

SKILL.md is an overview that keeps the core REST API inline and offloads Projects v2, gh CLI, and CI wiring to the real one-level-deep references/github-issues-reference.md via clearly signaled markdown links; the reference file does not nest further, matching the score-3 anchor.

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, complete, and distinctive: it enumerates concrete actions and endpoints, includes an explicit Use-when trigger, and disambiguates from sibling tracker skills. It is dense but every phrase is load-bearing rather than padded.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "issue creation, state changes (open / closed with state_reason), label-based severity/priority classification, and comment attachment" — plus specific endpoints (POST /repos/{owner}/{repo}/issues, PATCH), matching the score-3 anchor for multiple specific concrete actions; it is not merely naming a domain and some actions.

3 / 3

Completeness

Explicitly answers both what (creation, state changes, labels, comments) and when via the explicit "Use when programmatically managing the GitHub Issues bug lifecycle" clause, satisfying the score-3 anchor; the when is not merely implied.

3 / 3

Trigger Term Quality

Natural terms a user would say ("GitHub Issues", "bug", "bug lifecycle", "bug workflows") appear alongside the technical phrasing, giving good coverage; it is not reduced to 2 because the everyday terms users actually voice are present and explicit.

3 / 3

Distinctiveness Conflict Risk

It carves a clear niche (GitHub Issues bug lifecycle) and explicitly disambiguates against siblings ("for the same workflow on another tracker use azuredevops-bug-workflow, jira-bug-workflow-runner, or linear-bug-workflow-runner"), so it is unlikely to trigger the wrong skill.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents