CtrlK
BlogDocsLog inGet started
Tessl Logo

hunt

Finds root cause before applying fixes for errors, crashes, regressions, failing tests, broken behavior, and screenshot-reported defects. Use when users report in any language errors, crashes, broken behavior, regressions, failing tests, screenshot evidence, or something that used to work and now fails. Not for code review or new features.

75

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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, highly actionable diagnostic skill body with concrete commands, explicit validation/feedback workflows, and well-organized one-level-deep reference files. Slight conciseness dip comes from thematic repetition of the "re-read from scratch" directive.

DimensionReasoningScore

Conciseness

Dense and operational throughout — it assumes Claude's competence (no explaining what git bisect or a debugger is) and every section is actionable rules rather than padded explanation. Minor repetition of the "re-read the execution path from scratch" theme across Hard Rules, Confirm or Discard, and rationalization smells keeps it just below the lean 5 anchor.

4 / 5

Actionability

Fully executable guidance with concrete commands ("git status --short --branch -uall", "git diff <last-good>..HEAD -- <suspect path>", "git bisect good/bad", "sample <process>", "sw_vers", "grep -rn"), specific file:line examples, and copy-paste output/handoff templates covering the common cases.

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints (Runtime Evidence Ladder 1–5, Native App Freeze evidence 1–4, Bisect Mode, regression guard red-green run), plus feedback loops (Confirm or Discard, hard stops, 3-hypothesis handoff) — no destructive/batch cap applies since validation is pervasive.

5 / 5

Progressive Disclosure

Clear overview body with five well-signaled one-level-deep references ("See references/durable-context.md", "Load references/failure-patterns.md", etc.), all of which exist and contain no nested references — content appropriately split with easy navigation.

5 / 5

Total

19

/

20

Passed

Description

95%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, third-person description that crisply states what it does, when to use it, and what it is not for, with comprehensive natural trigger terms. The only minor gap is single-verb action diversity versus multi-action examples.

DimensionReasoningScore

Specificity

Names the concrete core action ("Finds root cause before applying fixes") and comprehensively enumerates defect categories ("errors, crashes, regressions, failing tests, broken behavior, screenshot-reported defects"), but action diversity is essentially single-verb rather than the multiple distinct actions the 5 anchor expects.

4 / 5

Completeness

Explicitly answers what ("Finds root cause before applying fixes for ...") and when ("Use when users report in any language ...") with concrete trigger phrases, plus an explicit exclusion ("Not for code review or new features").

5 / 5

Trigger Term Quality

Comprehensive natural-language triggers users actually say ("errors, crashes, broken behavior, regressions, failing tests, screenshot evidence") plus the synonym phrase "something that used to work and now fails", matching the 5 anchor's coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

Clear niche (root-cause diagnosis for defects) with an explicit out-of-scope clause ("Not for code review or new features") and distinct triggers, giving minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
tw93/Waza
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.