CtrlK
BlogDocsLog inGet started
Tessl Logo

bugfix

Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

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 lean, well-sequenced bugfix workflow with strong validation checkpoints and feedback loops. It is highly actionable with concrete commands, with only minor conciseness and actionability gaps in delegation guidance.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, with only minor over-explanation such as the rationale for not skipping reproduction and the Iteration Rules section restating logic already embedded in the steps.

4 / 5

Actionability

Provides concrete, executable commands (gh issue view template, npm run build && npm run bundle, node dist/cli.js) and explicit status codes, though agent-delegation guidance ('State only the goal') and 'Read the relevant code and make the fix' remain somewhat abstract.

4 / 5

Workflow Clarity

A clearly sequenced six-step process with explicit validation checkpoints (NOT_REPRODUCED, STILL_BROKEN, VERIFIED_FIXED), feedback loops back to Step 3, a self-audit pass, and a bounded iteration limit.

5 / 5

Progressive Disclosure

Well-organized with clear section headers and a self-contained single-file workflow that needs no external bundle; stops short of 5 only because there is no overview-to-detail file split, which is not strictly needed here.

4 / 5

Total

17

/

20

Passed

Description

82%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, well-structured description that clearly states capability, trigger conditions, and input format. It is concise and distinguishable, with only minor room to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (GitHub issue bugfix) and one concrete approach ('following the reproduce-first workflow') plus the input format, but describes a single workflow rather than listing several distinct capabilities.

3 / 5

Completeness

Explicitly answers both what ('Fix a bug from a GitHub issue, following the reproduce-first workflow') and when ('Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('fix a bug', 'investigate a GitHub issue', 'debug a user-reported problem') with synonyms, though a few common variants are absent.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche (GitHub issue bugfix with reproduce-first workflow) and distinct triggers tied to a specific input (issue URL or number), minimizing conflict with general debugging skills.

5 / 5

Total

17

/

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
QwenLM/qwen-code
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.