CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

breach-patterns

Learn from public breach disclosures — extract the audit question each one implies and check your own stack. Capital One IMDS abuse, LastPass vault exfiltration, Okta Lapsus$, Snowflake credential reuse, MOVEit, SolarWinds, Equifax, Target POS, Codecov, Uber, Twilio, Polymarket's compromised DebugBear script — what would you check now if your boss said 'could that happen to us?' Use when the user mentions 'breach analysis,' 'lessons learned,' 'security postmortem,' 'breach patterns,' 'breach lessons,' 'has this happened to us,' 'apply breach lessons,' 'preempt breaches,' 'security retrospective,' 'real-world security incidents,' or wants to harden against known attacker playbooks.

Quality

87%

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

78%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 well-built instruction-only audit skill: eleven pattern sections with specific, named controls and cross-references, a clear repeatable workflow with explicit dispositions and an output template, and exemplary progressive disclosure for its one deep-dive topic. The main improvements are trimming the well-known breach narratives, adding executable check commands beyond Pattern 11, and making the 'Clean' disposition verifiable before recording.

Suggestions

Trim the 'What happened' narratives for the most widely documented breaches (Capital One, SolarWinds, Equifax) to one or two sentences each, keeping only the pattern-relevant specifics.

Add a small set of executable grep or CLI check examples for one or two more patterns (as the third-party-scripts reference does) instead of delegating all execution to other audit skills.

Add an explicit validation step to the workflow instructing Claude to substantiate each 'Clean' disposition with evidence (command output, config excerpt) before recording it in the coverage table.

DimensionReasoningScore

Conciseness

The body is efficient: each pattern is a tight What happened / Audit questions / Check triple with no padding or explanation of basic concepts, and the intro and boundaries are brief. Not 5 because several 'What happened' paragraphs (Capital One, SolarWinds, Equifax) re-tread very widely known incidents in 3-4 sentences that could be trimmed to the pattern-relevant detail. Not 3 because these summaries directly feed the audit questions and the rest of the body earns its tokens.

4 / 5

Actionability

Checks are concrete and specific — 'IMDSv2 enforced on every EC2 launch template (MetadataOptions.HttpTokens: required),' named metadata IPs, 'CVE-2023-34362,' 'Number matching enabled on push MFA,' SRI pinning rules, plus a full markdown output template — and Pattern 11 has a companion reference with copy-paste rg/curl commands. Not 5 because for the other ten patterns execution depth is delegated to other skills ('see iam-audit,' 'see secrets-audit') with no in-bundle commands, leaving minor gaps in copy-paste-ready guidance.

4 / 5

Workflow Clarity

The 'How to use this skill' section gives a clear 4-step sequence (Read, Ask, Map, Decide) with an explicit disposition decision per pattern ('we've confirmed this can't happen' / 'we have a gap' / 'we accept-risk'), a defined output format, and boundary guidance to pivot to incident-triage on active issues. Not 5 because there is no validate-then-record checkpoint — nothing tells Claude how to substantiate a 'Clean' disposition before writing it into the coverage table, so checkpoints are present but implicit in places.

4 / 5

Progressive Disclosure

Clear sectioned overview in SKILL.md, and the single bundle reference is well-signaled ('TP1-TP6, greps and sources in [references/third-party-scripts.md]'), exists as a real file, and is exactly one level deep with its own organized structure (incident summary, checks table TP1-TP6, executable greps, sources). Content is appropriately split: only the pattern needing deep detail was extracted; the inline patterns are compact enough to stay in the body.

5 / 5

Total

17

/

20

Passed

Description

91%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 concrete capabilities, grounds them in named real-world breaches, and carries an unusually thorough 'Use when' trigger list with natural synonyms. Third person voice is used throughout. The only weaknesses are minor — the output deliverable is not mentioned and a couple of trigger phrases could overlap with an internal-postmortem skill.

DimensionReasoningScore

Specificity

Concrete actions are named — 'extract the audit question each one implies and check your own stack' — and the enumerated breach specifics (Capital One IMDS abuse, LastPass vault exfiltration, Polymarket's compromised DebugBear script) ground the domain. Not 3 because multiple specific actions plus concrete examples exceed '1-2 concrete actions'; not 5 because coverage has minor gaps (the output artifact — a breach-pattern coverage document — and mapping to other audit skills are unstated in the description).

4 / 5

Completeness

Both halves are explicit: 'what' is answered by 'Learn from public breach disclosures — extract the audit question each one implies and check your own stack,' and 'when' by the full 'Use when the user mentions...' clause with concrete trigger phrases. This clearly matches the anchor 'clearly and explicitly answers both what AND when with concrete trigger phrases.'

5 / 5

Trigger Term Quality

The trigger list is comprehensive with natural synonyms: 'breach analysis,' 'lessons learned,' 'security postmortem,' 'breach patterns,' 'has this happened to us,' 'apply breach lessons,' 'preempt breaches,' 'security retrospective,' 'real-world security incidents,' plus 'wants to harden against known attacker playbooks.' These are phrases a user would naturally say when they need this skill, matching the anchor for comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

The niche — learning from public breach disclosures to preemptively check one's own stack — is clear and the named-breach enumeration makes it unlikely to fire for unrelated skills. Not 5 because triggers like 'security postmortem' and 'lessons learned' carry minor overlap risk with a skill for running one's own internal incident retrospectives.

4 / 5

Total

18

/

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/breach-patterns/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.