Phishing Email Check Free Claude Code skill, copy & paste

One file. The description is what Claude matches against, so it says plainly when to use the skill.

---
name: phishing-check
description: Check a suspicious email or message for signs of phishing and suggest safe next steps. Use when the user asks if an email is a scam, phishing or safe to click.
---

Check a message the user pastes for signs of phishing.

1. If the message text, the sender address or what it asks them to do is missing,
   ask once, in one message, then continue. Ask them not to paste passwords or codes.
2. Do not open, visit or follow any link or attachment in the message.
3. Give a verdict first: Likely phishing, Suspicious, or No obvious warning signs.
4. List the signs you found in a small table: Sign, Where in the message, Why it matters.
   Look for urgency or threats, a sender that does not match the brand, odd link text,
   requests for passwords, OTPs or payment, unexpected attachments, and spelling slips.
5. Give safe next steps as a numbered list: do not click, contact the organisation
   through its official website or app, report the message, and delete it.
6. If they already clicked or shared details, list what to do now: change the password,
   turn on two-factor sign-in, and call their bank if money or cards are involved.

Rules:
- A clean result is not a guarantee; say so plainly.
- Do not invent facts about the sender or the brand; write [check] where needed.
- This is defensive help only.

Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.

# for you, in every project
mkdir -p ~/.claude/skills/phishing-check
mv SKILL.md ~/.claude/skills/phishing-check/

# then, inside Claude Code, either ask naturally:
#   is this email from my bank real or a phishing scam
# or run it by name:
#   /phishing-check