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.

76

Quality

95%

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

100%

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

A tight, executable workflow with concrete commands, explicit validation/feedback loops, and clean organization. It respects Claude's intelligence and avoids unnecessary explanation or nested references.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, avoiding explanations of what GitHub or bugs are; even the one rationale line ('fixing without first reproducing... tends to produce incomplete fixes and regressions') earns its place by justifying a hard rule.

3 / 3

Actionability

It provides copy-paste-ready, executable commands (gh issue view with a full template, mkdir -p, npm run build && npm run bundle, node dist/cli.js) plus concrete agent spawns and file paths.

3 / 3

Workflow Clarity

A clearly sequenced 6-step workflow with explicit validation checkpoints (NOT_REPRODUCED stops; STILL_BROKEN loops back to Step 3; 'Do not proceed until VERIFIED_FIXED') and dedicated iteration rules.

3 / 3

Progressive Disclosure

The skill is self-contained with no bundle files, organized into clearly labeled sections (Input, Artifact Path, Steps 1-6, Iteration Rules); references to AGENTS.md and sibling skills are tooling pointers, not nested reference chains.

3 / 3

Total

12

/

12

Passed

Description

90%

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 concise, well-targeted description that clearly states both what it does and when to use it, with natural trigger terms and a distinct niche. The only weakness is that the listed actions are variations of a single task rather than a broad capability set.

DimensionReasoningScore

Specificity

Names the domain (GitHub issue bugfixes) and the reproduce-first workflow, and lists fix/investigate/debug actions, but these are near-synonyms for one task rather than a comprehensive set of distinct concrete capabilities.

2 / 3

Completeness

It states what the skill does ('Fix a bug from a GitHub issue, following the reproduce-first workflow') and gives an explicit 'Use when...' trigger clause covering multiple scenarios.

3 / 3

Trigger Term Quality

Phrases like 'fix a bug', 'investigate a GitHub issue', and 'debug a user-reported problem' are natural terms a user would actually say when requesting this skill.

3 / 3

Distinctiveness Conflict Risk

The niche is narrow (GitHub issue bugfixes with a reproduce-first workflow) with distinct triggers (issue URL/number, bug, debug), making conflict with other skills unlikely.

3 / 3

Total

11

/

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.

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.