CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

finding-triage

Triage a single security finding — from a scanner, audit, advisory, report, or a findings.json record — to a defensible disposition with calibrated severity, a mitigation plan, false-positive justification, or accepted-risk writeup. Use when the user mentions 'triage this finding,' 'is this a real vulnerability,' 'mitigation plan,' 'false positive,' 'accept this risk,' 'compensating controls,' 'risk justification,' 'security ticket,' 'CVSS this,' 'what severity is this,' 'is this really high,' 'severity calibration,' 'needs validation,' 'hardening note,' 'findings.json,' 'should we fix this,' 'disposition,' 'sign off on,' or has a single security finding and needs to decide what to do.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 high-quality workflow skill: the seven-step triage process is unambiguous, validation checkpoints and feedback loops are built in at every stage, and the guidance is concrete down to exact commands, field names, and copy-ready templates. The main costs are token weight — the inline template block and a closing list of generic framework citations — which keep it just under top marks on conciseness and progressive disclosure.

Suggestions

Move the six disposition templates into a references/templates.md file and keep one-line summaries of each in Step 5, cutting roughly 150 lines from SKILL.md while preserving copy-paste readiness.

Trim the closing References list of generic framework citations (CVSS, EPSS, NIST SP 800-30, FAIR, ISO 27005, OWASP Risk Rating) to the two or three that actually change a triage decision, or fold them into severity-calibration.md where they are applied.

Move the default SLA table to severity-calibration.md alongside the rest of the calibration rules, keeping only the principle that 'SLA is separate from severity' inline.

DimensionReasoningScore

Conciseness

The body is dense, imperative, and almost entirely org-specific policy Claude cannot infer (the boundary + result gate, verdict handling, disposition required-fields tables), with no tutorial padding. What keeps it below the 5 anchor is the trailing name-drop reference list ("CVSS v4.0 specification — first.org/cvss," "NIST SP 800-30," "FAIR," "ISO 27005," "OWASP Risk Rating Methodology") that points at frameworks Claude already knows, plus a few rhetorical flourishes ("an audit trail that survives a regulator reading it six months later") that could be trimmed.

4 / 5

Actionability

For an instruction-only skill this is fully executable: a concrete validation command ("node references/validate-findings.mjs findings.json"), six complete copy-paste-ready ticket templates, the six-element boundary + result gate, a six-item High/Critical acceptance checklist, named record fields to write back ("ext.fixed_in, ext.fix_verified_on and ext.regression_test"), and a five-step fix-verification procedure. It sits above the 4 anchor because concrete examples cover every common case with no meaningful gaps.

5 / 5

Workflow Clarity

Steps 1–7 are clearly sequenced (restate → verify truth → contextual severity → disposition → writeup → validate writeup → verify fix) with explicit validation checkpoints: Step 6 is a pre-submission checklist, record edits require re-running the validator, and the guidance includes feedback loops ("downgrade rather than delete," reopen as a regression if the same fingerprint returns, re-open a rejected finding if the control moved). This matches the 5 anchor's sequence + validation + feedback loops + checklists; the destructive/batch cap does not apply because validation is pervasive.

5 / 5

Progressive Disclosure

The bundle structure is sound: every reference cited in the body (severity-calibration.md, findings-format.md, verification.md, fix-verification.md, independent-verification.md, validate-findings.mjs, to-sarif.mjs) exists as a real, substantive file exactly one level deep, and each pointer is signaled with its content ("the full severity rules this skill summarizes"). It falls short of the 5 anchor because roughly 150 lines of ticket templates and the default SLA table live inline in SKILL.md, making it heavier than a clear overview that delegates bulk detail to references.

4 / 5

Total

18

/

20

Passed

Description

96%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 description: it states a concrete multi-outcome capability, includes an explicit 'Use when' clause with an unusually thorough set of natural trigger phrases and synonyms, and scopes itself to single-finding disposition. The only weakness is that several trigger terms overlap with the vocabulary of sibling audit skills in the same plugin, which could occasionally fire the wrong skill in a security-heavy environment.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with comprehensive coverage of the disposition space: "Triage a single security finding ... to a defensible disposition with calibrated severity, a mitigation plan, false-positive justification, or accepted-risk writeup." It names every outcome type the skill produces, matching the comprehensive-coverage anchor rather than the 4 anchor, which reserves room for coverage gaps.

5 / 5

Completeness

It explicitly answers both questions: the "what" is triage to a disposition with named artifacts (calibrated severity, mitigation plan, false-positive justification, accepted-risk writeup), and the "when" is an explicit "Use when the user mentions ..." clause listing concrete trigger phrases plus a scope fallback ("has a single security finding and needs to decide what to do"). This is a direct match to the 5 anchor; the 4 anchor applies only when the 'when' is less explicit.

5 / 5

Trigger Term Quality

Trigger phrases are natural user phrasings with rich synonym coverage: 'triage this finding,' 'is this a real vulnerability,' 'should we fix this,' 'is this really high,' 'CVSS this,' 'sign off on,' plus the record-type name 'findings.json' — the equivalent of the anchor's file-extension coverage. Not the 4 anchor because no common variation of the request is obviously missing.

5 / 5

Distinctiveness Conflict Risk

"Triage a single security finding" and "needs to decide what to do" carve a clear niche (disposition, not generation, of findings), but broadly shared security vocabulary like 'false positive,' 'severity calibration,' and 'mitigation plan' risks overlap with the sibling audit skills this repo contains. Mostly distinct with minor overlap risk against closely related skills — the 4 anchor — since the 5 anchor requires minimal conflict risk and this plugin family has many adjacent security skills.

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

briiirussell/cybersecurity-skills

Path

skills/finding-triage/SKILL.md

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.