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.

74

Quality

92%

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

The canonical home for this skill is hunt in tw93/Waza

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 playbook with pervasive validation checkpoints and clean one-level-deep reference structure. The only minor weakness is that some hard rules are long prose rather than executable snippets.

DimensionReasoningScore

Conciseness

Dense and operational throughout — no padded concept explanations, every line is actionable guidance, a hard rule, or a template; assumes Claude's competence and earns its tokens.

5 / 5

Actionability

Provides concrete commands (git status, git bisect, grep -rn), exact templates (root-cause sentence, Success/Handoff blocks), and a file:line specificity requirement; minor gap is the prose-heavy regression-guard rule rather than a copy-paste script.

4 / 5

Workflow Clarity

Multi-step processes carry explicit validation checkpoints — the Outcome Contract "Done when", Confirm-or-Discard feedback loop, the five-rung Runtime Evidence Ladder, and the red-green regression guard — with feedback loops for risky operations.

5 / 5

Progressive Disclosure

Overview SKILL.md links five well-signaled one-level-deep references (durable-context, failure-patterns, logging-techniques, rendering-debug, ime-unicode), all verified as real files, each placed at its relevant section.

5 / 5

Total

19

/

20

Passed

Description

92%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, specific description with explicit what/when guidance and a useful exclusion clause. Trigger-term quality is the only mild gap, as a few natural phrasings are split off into when_to_use.

DimensionReasoningScore

Specificity

States the core action ("Finds root cause before applying fixes") and comprehensively enumerates concrete defect types — errors, crashes, regressions, failing tests, broken behavior, screenshot-reported defects — matching the multiple-concrete-actions anchor.

5 / 5

Completeness

Explicitly answers both what (finds root cause before fixes for named defect types) and when ("Use when users report…"), plus an exclusion clause ("Not for code review or new features").

5 / 5

Trigger Term Quality

Strong natural-term coverage ("errors, crashes, broken behavior, regressions, screenshot evidence, something that used to work and now fails"), but a few common phrasings like "why broken" or "not working" live only in when_to_use rather than the description field itself.

4 / 5

Distinctiveness Conflict Risk

Clear diagnose-before-fix niche with distinct triggers and an explicit boundary against code review and new features, minimizing 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.