CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conducting-phishing-incident-response

Respond to phishing incidents by analyzing reported emails, extracting indicators, sandboxing URLs/attachments, assessing credential compromise, quarantining malicious messages organization-wide, and remediating affected accounts. Use when investigating a reported phishing or credential-phishing email, a suspected spearphishing incident, or when a mailbox-wide purge and account remediation is needed.

Quality

81%

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

63%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-structured, professional IR workflow with concrete commands, good scoping guidance, and a useful scenario/pitfalls section, held back by an unnecessary key-concepts glossary and a complete failure to reference the bundle's api-reference.md and agent.py. Tightening the boilerplate sections and linking the existing reference files would lift the skill substantially.

Suggestions

Remove or drastically trim the "Key Concepts" table — terms like SPF, DKIM, DMARC, and spear phishing are standard knowledge Claude already has; keep only niche items like "OAuth Consent Phishing" if any.

Link the existing bundle files from the body (e.g., under "Tools & Systems" or a new "Automation" section: "See [references/api-reference.md](references/api-reference.md) for automated EML analysis via scripts/agent.py") so the reference material is discoverable rather than orphaned.

Make the mailbox purge step copy-paste executable by adding the actual New-ComplianceSearch / New-ComplianceSearchAction -Purge cmdlets, since this is the workflow's most destructive batch operation.

DimensionReasoningScore

Conciseness

The workflow steps, checklists, and PowerShell block are lean, but the "Key Concepts" table explains concepts Claude already knows well ("SPF (Sender Policy Framework)", "DMARC", "Spear Phishing", "Credential Harvesting") — exactly the unnecessary explanation the rubric penalizes — and the "Tools & Systems" section partly re-describes well-known platforms. This fits the score-3 anchor (mostly efficient with some unnecessary explanation) rather than score 4, where only minor trimming would be needed.

3 / 5

Actionability

Mostly executable guidance: concrete PowerShell commands (Revoke-AzureADUserAllRefreshToken, Get-InboxRule), named tools per step (VirusTotal, URLscan.io, ANY.RUN, olevba, Threat Explorer/Content Search), and specific search methods (proxy logs, EDR hash search). It falls short of score 5 because some destructive operations lack copy-paste commands — the org-wide purge step says only "Purge the phishing email from all mailboxes using Microsoft 365 Content Search and Purge" without the actual New-ComplianceSearch/-Purge cmdlets.

4 / 5

Workflow Clarity

The six-step sequence (triage → analyze → scope → contain → eradicate → post-incident) is clearly ordered with decision gates (classification criteria, containment keyed to impact assessment), and Step 5 provides verification for the batch purge ("Confirm email purge completed successfully across all mailboxes"), so the destructive/batch cap at 3 does not apply. It stays at 4 rather than 5 because explicit feedback loops (what to do when a purge fails or a compromised account shows continued unauthorized access) are absent.

4 / 5

Progressive Disclosure

The body is well-sectioned, but the bundle's reference material — references/api-reference.md and scripts/agent.py — is never mentioned anywhere in SKILL.md, so the references are effectively buried despite existing. Per the rubric's instruction to score against the actual bundle structure, this matches the score-3 anchor (references present but not clearly signaled; content that should be separate is inline, e.g., the full output-format template) rather than score 4, where references are mostly clear.

3 / 5

Total

14

/

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 description that pairs a comprehensive, verb-led action list with an explicit, multi-trigger "Use when" clause in third person. Trigger coverage is good but omits a few natural synonyms ("suspicious email", "email scam", "quishing") that would make invocation even more reliable.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "analyzing reported emails, extracting indicators, sandboxing URLs/attachments, assessing credential compromise, quarantining malicious messages organization-wide, and remediating affected accounts" — comprehensively covering the phishing IR lifecycle. This matches the score-5 anchor (multiple specific concrete actions, comprehensive coverage) and is clearly above score 4, which expects minor gaps in coverage.

5 / 5

Completeness

Both halves are explicit: the "what" is the full action list, and the "when" is a concrete "Use when investigating a reported phishing or credential-phishing email, a suspected spearphishing incident, or when a mailbox-wide purge and account remediation is needed" clause. This directly matches the score-5 anchor (clearly and explicitly answers both what AND when with concrete trigger phrases).

5 / 5

Trigger Term Quality

Natural triggers include "reported phishing or credential-phishing email", "suspected spearphishing incident", and "mailbox-wide purge" — phrases a user or Claude would plausibly say. A few common variations are missing (e.g., "suspicious email", "email scam", "quishing"), so it falls just short of the score-5 anchor's comprehensive synonym coverage but is clearly above score 3's missing-variation level.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche — phishing email incident response with org-wide mailbox quarantine and account remediation — with distinct trigger phrases unlikely to fire for unrelated skills. Only trivial overlap with adjacent BEC/account-takeover procedures exists, matching the score-5 anchor (clear niche, distinct triggers, minimal conflict risk) rather than score 4's "minor overlap 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.

Validation — 15 / 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

mukul975/Anthropic-Cybersecurity-Skills

Path

skills/conducting-phishing-incident-response/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.