triage-validation

Finding validation before writing any report — 7-Question Gate (all 7 questions), 4 pre-submission gates, always-rejected list, conditionally valid with chain table, CVSS 3.1 quick reference, severity decision guide, report title formula, 60-second pre-submit checklist. Use BEFORE writing any report. One wrong answer = kill the finding and move on. Saves N/A ratio.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%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 highly actionable with strong, well-sequenced validation workflows and feedback loops. Its weaknesses are verbosity from a restating Operator Notes section and a monolithic structure that inlines reference material better suited to separate files.

Suggestions

Extract the CVSS 3.1 quick reference, Never-Submit list, and chain-required table into files under references/ and link to them one level deep, reducing SKILL.md to an overview.

Trim or remove the 'Operator Notes (Claude-BugHunter)' section whose 7Q, Pre-Severity, and retraction subsections duplicate content already present in the main body; keep only the net-new material (the 4 false-positive shapes table and the 7Q↔discipline-rule cross-link).

Consolidate the repeated 'kill the finding / move on' framing that appears in the intro, KILL FAST RULES, and Operator Notes into a single statement to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	Mostly efficient operational knowledge with no padding of basic concepts, but the 'Operator Notes (Claude-BugHunter)' section (~55 lines) restates the 7Q gate, Pre-Severity Gate, and retraction discipline already covered in the main body, which could be tightened.	3 / 5
Actionability	Fully executable guidance throughout: copy-paste curl probes for the layer-ordering trap, a fill-in Q1 template, retraction-entry template, gate checklists, concrete CVSS vectors, and a chain-required mapping table covering common cases.	5 / 5
Workflow Clarity	Clear ordered sequence (7Q asked in order, 4 sequential gates where 'ALL 4 must PASS', pre-severity gate) with explicit validation checkpoints and feedback loops (re-validate after fix; 'gather more evidence... then re-run the gate').	5 / 5
Progressive Disclosure	No bundle files exist and the ~418-line SKILL.md is monolithic, with large inlined reference blocks (CVSS quick reference table, Never-Submit list, chain table) that would be better placed in separate reference files; section headers provide structure but content is not split.	3 / 5
	Total	16 / 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.

The description is comprehensive, specific, and explicitly triggers on 'before writing any report', with a distinct validation niche. It is slightly jargon-heavy in places but strong overall.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — '7-Question Gate (all 7 questions), 4 pre-submission gates, always-rejected list, conditionally valid with chain table, CVSS 3.1 quick reference, severity decision guide, report title formula, 60-second pre-submit checklist' — giving comprehensive coverage of what the skill provides.	5 / 5
Completeness	Clearly answers both 'what' (the enumerated validation toolset) and 'when' via the explicit trigger 'Use BEFORE writing any report', satisfying the explicit-trigger requirement so completeness is not capped.	5 / 5
Trigger Term Quality	Includes natural phrases a researcher would say ('writing any report', 'kill the finding and move on', 'Saves N/A ratio') but leans on jargon (CVSS 3.1, chain table) and misses some common synonyms; good but not comprehensive keyword coverage.	4 / 5
Distinctiveness Conflict Risk	Occupies a distinct validation-gate niche ('Finding validation before writing any report') with clear triggers and minimal overlap with adjacent report-writing skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

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: elementalsouls/Claude-BugHunter
Path: skills/triage-validation/SKILL.md
Commit: 0ce18ba

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.