CtrlK
BlogDocsLog inGet started
Tessl Logo

bughunt

Fully autonomous bug hunting pipeline — discover bugs in a scoped area using parallel subagents, independently triage each finding, fix confirmed issues with subagents, then audit all fixes against repo constraints and target platforms. Runs end-to-end without user interaction.

62

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

Quality

Content

77%

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

The content is a well-sequenced, highly actionable five-phase pipeline with strong validation feedback loops. Its weaknesses are repeated autonomy emphasis that could be tightened and a monolithic single-file structure that doesn't leverage progressive disclosure.

Suggestions

Consolidate the repeated 'do not wait for user input' reminders into the single Guidance bullet and drop the per-phase restatements to reduce token overhead.

Consider moving the subagent prompt templates into a referenced file (e.g. prompts.md) so SKILL.md reads as a lean overview with one-level-deep navigation.

DimensionReasoningScore

Conciseness

The body is dense and mostly free of basic-concept explanations, assuming Claude's competence, but the autonomy directive is restated repeatedly ('Proceed immediately to X — do not wait for user input' at the end of each phase plus a dedicated Guidance bullet), which is tightening-eligible padding; not quite level-3 lean.

2 / 3

Actionability

Provides copy-paste-ready subagent prompt templates, concrete commands ('mkdir -p {OUTPUT_DIR}/evidence', 'bash -n', 'python -m py_compile', 'tsc --noEmit'), explicit verdict definitions, and a precise audit checklist — fully executable guidance.

3 / 3

Workflow Clarity

A clear five-phase sequence with explicit validation checkpoints (syntax/parse checks after Fix, audit re-run 'to confirm') and a feedback loop for audit failures (identify violation -> apply correction -> re-run check), matching the top anchor.

3 / 3

Progressive Disclosure

The skill is a single self-contained SKILL.md with well-labeled sections and no nested references (no bundle files exist), but the full prompt templates and audit detail live inline in a ~200-line file rather than being split out, so it sits at 'some structure, could be better organized' rather than a clean overview-plus-references layout.

2 / 3

Total

10

/

12

Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive, clearly conveying a multi-stage autonomous bug-hunting pipeline. Its main weakness is the absence of an explicit 'Use when...' trigger clause and limited variation in trigger terms.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to find, triage, and fix bugs in a specific area of a codebase, or to run an autonomous bug hunt.'

Broaden trigger terms with natural phrasings users are likely to say, such as 'bug hunt', 'find bugs', 'bugbash', or 'sweep for bugs'.

DimensionReasoningScore

Specificity

Lists multiple concrete pipeline actions — 'discover bugs', 'independently triage each finding', 'fix confirmed issues', 'audit all fixes against repo constraints and target platforms' — matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Clearly states what the skill does (the find/triage/fix/audit pipeline) but provides no explicit 'Use when...' trigger clause; 'Runs end-to-end without user interaction' describes behavior, not when to invoke it, so completeness is capped at 2 per the guidelines.

2 / 3

Trigger Term Quality

Contains relevant natural terms like 'bug hunting', 'discover bugs', 'triage', 'fix', and 'audit', but offers only one phrasing rather than the common variations a user might say (e.g. 'find bugs', 'bug hunt', 'code review for bugs').

2 / 3

Distinctiveness Conflict Risk

Occupies a clear niche — an autonomous multi-phase bug-hunting pipeline with parallel subagents and an audit step — that is unlikely to trigger for the wrong skill.

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