CtrlK
BlogDocsLog inGet started
Tessl Logo

github-qa-labels

Label GitHub issues and PRs found during QA testing. Use when organizing QA findings with proper labels.

67

Quality

80%

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

SKILL.md
Quality
Evals
Security

Quality

Content

87%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 concise, highly actionable labeling skill with clean organization. Its main gap is the absence of validation checkpoints around the batch labeling workflow, which the rubric caps at 3 for workflow clarity.

Suggestions

Add a precondition check that a label exists before adding it (e.g., `gh label list | grep` or create-if-missing), and verify application after batch runs.

Include an explicit error-recovery note for batch commands chained with `&&` so a failed edit is caught and retried rather than silently skipped.

DimensionReasoningScore

Conciseness

Lean throughout: only concrete gh commands and label definitions, with no explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Fully executable, copy-paste-ready gh commands covering label creation, issue/PR labeling, severity tiers, and batch labeling; specific examples cover the common cases.

5 / 5

Workflow Clarity

Sections provide a clear sequence but include no validation/verification for this batch operation (no check that a label exists before adding, no confirmation it applied, no error-recovery loop), which caps the score at 3 per the rubric.

3 / 5

Progressive Disclosure

A short, single-purpose skill with well-organized section headers and no need for external references; no bundle files are present, so the clean in-body structure satisfies the bar.

5 / 5

Total

18

/

20

Passed

Description

73%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 clear, third-person description with explicit what-and-when structure and natural trigger terms, well-distinguished from other skills. It could name more concrete labeling actions to lift specificity and completeness.

Suggestions

Enumerate the concrete actions in the description (e.g., add upgrade-tracking and severity labels) to raise specificity.

Broaden the 'when' clause with more trigger variations (e.g., 'Use when triaging QA results, applying severity, or batch-labeling release findings').

DimensionReasoningScore

Specificity

Names the domain ('GitHub issues and PRs', 'QA testing') and one concrete action ('Label') but does not enumerate the several labeling actions the body covers (severity, tracking, batch), so it is not comprehensive.

3 / 5

Completeness

Explicitly answers both what ('Label GitHub issues and PRs found during QA testing') and when ('Use when organizing QA findings with proper labels'), though the 'when' clause is somewhat narrow rather than fully enumerated.

4 / 5

Trigger Term Quality

Includes natural phrases users would say ('GitHub issues and PRs', 'QA testing', 'QA findings', 'labels'); coverage is good though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (QA-test labeling of GitHub issues/PRs) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

16

/

20

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.

Repository
storybookjs/storybook
Reviewed

Table of Contents

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.