CtrlK
BlogDocsLog inGet started
Tessl Logo

bugbash

Systematically explore and test any software project (CLI, API, Backend, Library, etc.) to find bugs, usability issues, and edge cases. Produces a structured report with full reproduction evidence (exact commands, inputs, logs, and tracebacks) for every issue.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/bugbash/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

The body is a lean, highly actionable guide with a well-sequenced workflow, explicit verification loops, and clean single-file organization. Only minor improvements are available: show the report.md template verbatim and trim the few chatty phrases.

DimensionReasoningScore

Conciseness

Sections are lean, using tables and exact commands with no explanation of concepts Claude already knows; only minor chattiness ('are your friends', 'Usability matters.') keeps it off the top anchor.

4 / 5

Actionability

Concrete throughout (mkdir command, severity definitions, evidence/issue-{NNN}.txt naming, echo $? / curl -w checks), but the report.md template is described rather than shown verbatim — a minor gap.

4 / 5

Workflow Clarity

A clear 5-step numbered sequence, each expanded, with explicit verification checkpoints: repro-retry feedback loop ('If it's flaky, note that and try to identify the conditions') and summary-count reconciliation. Not a destructive/batch operation, so no cap applies.

5 / 5

Progressive Disclosure

A self-contained, well-sectioned single file (Setup / Workflow / Guidance) with no bundle files; nothing is bulky enough to warrant splitting, so all content is appropriately placed.

5 / 5

Total

18

/

20

Passed

Description

67%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 specific, action-oriented description that clearly states what the skill does and produces, but it lacks an explicit 'Use when...' trigger clause and uses broad phrasing ('any software project') that risks overlap with review/verify skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when asked to test, QA, or dogfood a project, find bugs before a release, or hunt for edge cases in a CLI/API/backend/library.'

Include the natural synonyms users would say ('QA', 'testing', 'dogfooding', 'break the software') alongside 'bugs' and 'edge cases' to broaden trigger coverage.

Narrow the domain claim ('any software project') or state what it is not for (e.g. exclude web UIs, which appear to be handled by a sibling skill) to reduce conflict with code-review/security-review/verify skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('explore and test', 'find bugs, usability issues, and edge cases', 'Produces a structured report with full reproduction evidence (exact commands, inputs, logs, and tracebacks)') with comprehensive coverage of the task including the deliverable.

5 / 5

Completeness

The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance — the rubric caps this at 3.

3 / 5

Trigger Term Quality

Natural terms like 'bugs', 'usability issues', 'edge cases', 'test', 'CLI', and 'API' are present, but common user phrasings such as 'QA', 'testing', or 'dogfooding' are missing.

4 / 5

Distinctiveness Conflict Risk

'any software project... explore and test' is broad and overlaps with code-review, security-review, and verify-type skills; the bug-report deliverable gives it some distinctness but not enough for a 4.

3 / 5

Total

15

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
av/harbor
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.