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.

72

Quality

87%

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

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 well-structured, actionable skill body with concrete commands, a clear sequenced workflow including verification checkpoints, and clean organization that needs no external references.

DimensionReasoningScore

Conciseness

Lean and table/bullet-driven with no concept-explanation padding; every section earns its place, with only mild redundancy in the opening line restating the description.

3 / 3

Actionability

Provides concrete executable commands (mkdir -p {OUTPUT_DIR}/logs, {TARGET} --help, curl -w "%{http_code}", echo $?) with defined placeholders and a copy-paste-ready severity rubric.

3 / 3

Workflow Clarity

A clearly sequenced 5-step workflow with explicit validation checkpoints (verify reproducibility before documenting; re-read and reconcile severity counts in Wrap Up), appropriate for a non-destructive testing skill.

3 / 3

Progressive Disclosure

No bundle files are present and none are needed; the self-contained process skill is well-organized into Setup, Workflow, and Guidance sections with easy navigation.

3 / 3

Total

12

/

12

Passed

Description

75%

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-rich description with good natural trigger terms, but it lacks an explicit 'Use when...' clause and its core trigger ('find bugs') is generic enough to risk overlap with debugging skills.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger scenarios, e.g. 'Use when the user asks to find bugs, dogfood, or stress-test a CLI, API, backend, or library.'

Sharpen distinctiveness by leading with the repro-evidence/report output framing rather than the generic 'find bugs' phrasing.

Surface the report deliverable ('structured report with full reproduction evidence') earlier as the distinguishing promise of the skill.

DimensionReasoningScore

Specificity

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)'), matching the score-3 anchor.

3 / 3

Completeness

Clearly answers 'what' but provides no explicit 'Use when...' trigger clause; the 'when' is only implied, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Includes natural terms users would say ('bugs', 'usability issues', 'edge cases') alongside target-type keywords (CLI, API, Backend, Library), giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The repro-evidence framing narrows the niche, but 'find bugs' is generic enough to overlap with general debugging/testing skills, so it is not a clear distinct trigger.

2 / 3

Total

10

/

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