CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

incident-triage

Guide rapid triage and initial response to a live security incident happening right now (ransomware hitting a file server, an attacker still in the network, a new admin user nobody created, a host compromised through a CVE) following NIST SP 800-61 Rev. 3 (CSF 2.0 Respond and Recover) — declare, validate and prioritize, contain, preserve evidence, scope, extract IOCs, start the notification clocks, and hand off to eradication, recovery and lessons learned. Use when the user mentions 'incident response,' 'security incident,' 'incident triage,' 'active incident,' 'we've been hacked,' 'we've been breached,' 'compromised,' 'ransomware,' 'contain the incident,' 'malware detected,' 'suspicious activity,' 'IOC,' 'indicators of compromise,' or needs help handling a security event.

Quality

94%

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.

Excellent operational content: executable commands, a clearly sequenced seven-step workflow with validation and approval checkpoints, and a complete report template, with the dev-tool playbook correctly offloaded to a real one-level reference. The only weakness is token efficiency — the long cross-reference paragraph, framework revision history, and inline dated details could be trimmed or relocated.

DimensionReasoningScore

Conciseness

The body is dense and tactical — no padding explaining what ransomware or IOCs are, and commands appear without library tutorials — but the ~12-skill cross-reference paragraph and the NIST revision-history sentence ("replaced Rev. 2's four-phase lifecycle…") could be trimmed, and time-sensitive details ("Rev. 3 (April 2025)", the "October 2026" IOC list) sit inline rather than in a dated/deprecated section. Efficient overall with minor over-explanation, matching the 4 anchor; it is well above 3 (mostly efficient with several unnecessary explanations) but short of 5 (every token earning its place).

4 / 5

Actionability

Provides an executable evidence-capture block (ps auxf, ss -tupn, lsof -nP, journalctl --since "1 hour ago"), concrete severity and incident-type taxonomies, a notification-deadline table with specific clocks, and a complete copy-paste report template with tables and checklists. Fully executable guidance covering the common cases matches the 5 anchor.

5 / 5

Workflow Clarity

Seven clearly sequenced steps with explicit validation checkpoints: validate the alert against a second source and rule out a known change before mobilizing, approval gates before every containment action ("name the action and its blast radius, and get the incident lead's go-ahead"), coordinate isolate/disable/rotate together to avoid tipping off an active attacker, and an escalation checklist plus known/suspected/ruled-out scoping. Explicit validation, checkpoints, and checklists match the 5 anchor; the destructive-operation cap at 3 does not apply because containment is validation-gated.

5 / 5

Progressive Disclosure

The body is a well-organized overview with clear section headers, and the dev-tool-compromise playbook is appropriately split into a real, well-signaled one-level-deep reference ([references/dev-tool-compromise.md](references/dev-tool-compromise.md), verified to exist). Inline content (severity taxonomy, IOC table, report template) is core triage-time material that belongs in SKILL.md. Clear overview with one-level references and easy navigation matches the 5 anchor.

5 / 5

Total

19

/

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 comprehensive, concrete action chain in third person and pairs it with an explicit, natural-language trigger list. The only weakness is that several broad trigger phrases ("malware detected," "suspicious activity") could also fire for closely adjacent security skills, creating minor conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions covering the full triage lifecycle — "declare, validate and prioritize, contain, preserve evidence, scope, extract IOCs, start the notification clocks, and hand off to eradication, recovery and lessons learned" — with concrete incident examples ("ransomware hitting a file server, an attacker still in the network"), in third person. Comprehensive coverage matches the 5 anchor; 4 would require minor gaps, and none are evident.

5 / 5

Completeness

Clearly answers both questions: the "what" is the full action chain from declaration through handoff, and the "when" is an explicit "Use when the user mentions…" clause with concrete trigger phrases. Both are explicit and concrete, matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

The "Use when the user mentions" clause covers natural terms including colloquial synonyms users would actually say: "incident response," "we've been hacked," "we've been breached," "ransomware," "IOC," "indicators of compromise," plus "needs help handling a security event." Coverage includes synonyms and phrasing variations with no common terms missing, matching the 5 anchor rather than 4.

5 / 5

Distinctiveness Conflict Risk

The niche (live security-incident triage following NIST SP 800-61) is clear and mostly distinct, but broad triggers like "malware detected," "suspicious activity," and "compromised" create minor overlap risk with closely related security skills (e.g., malware triage or SOC operations skills). This sits between the 4 anchor ("minor overlap risk with closely related skills") and 5; the overlap terms keep it at 4 rather than 5, while the unmistakable niche keeps it well above 3.

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