Anti-Phishing Email Check
Verify a scary 'action required' email in 60 seconds: headers, link destinations, official-channel check.
The Anti-Phishing Email Check verifies whether a scary "action required" email is real or phishing before you click anything or share credentials. It is the five-minute triage from a real case: a "developer portal now open, complete the intake" email that turned out authentic (proper SPF, DKIM, and DMARC authentication, direct links, no redirectors) and would have been caught in sixty seconds if it had not been. The workflow has five steps. First, read the headers: in Gmail, open the message and choose "Show original", then check Authentication-Results for spf=pass, dkim=pass, and dmarc=pass, all three, with the DKIM d= domain matching the claimed sender's domain rather than a lookalike. Second, inspect every link: the visible text means nothing, the real destination is the href. Red flags are URL shorteners, redirector domains, punycode and lookalike domains, and mismatched display versus destination. Third, check the ask: credential demands, password resets, payments, or "urgent" downloads deserve high alert, and legitimate senders rarely lead with urgency plus a link. When in doubt, do not use the email's link: navigate to the official site yourself and look for the same notice in your account. Fourth, cross-check the channel: a real "portal is open" email has a public counterpart on the company's site, status page, or verified social. Fifth, decide: authentic means proceed via your own navigation, suspicious means report as phishing and delete, and if you already clicked, rotate the exposed credential immediately. The operating rules are simple: headers before links, because authentication results are harder to fake than link text. A familiar logo, your name, or "we have emailed before" proves nothing. Approval to read an email is never approval to click its links. Never forward a suspicious email's links to someone else "to check": describe it in words. And if mixed signals leave you inconclusive, treat it as suspicious and contact the company through a known-good channel.
Version:
Quick answer
The Anti-Phishing Email Check gives your Muse a five-step triage for a scary « action required » email, before you click anything or share credentials. It reads the authentication headers first (SPF, DKIM and DMARC), inspects every link's real destination, weighs what the message is asking for, cross-checks the official channel, and ends in a clear decision — proceed via your own navigation, or report and delete. Its working rules are strict: a familiar logo or your name proves nothing, and reading an email is never approval to click its links.
At a glance
| What it is | A five-step verification workflow that decides whether an « action required » email is authentic or phishing. |
|---|---|
| Who it's for | Anyone who receives urgent-looking security or account emails and wants a method instead of a gut feeling. |
| What you give it | The suspicious email — its headers (Show original in Gmail) and its links, described or pasted as text, never clicked. |
| What you get | A verdict with the evidence: authentication results, each link's real destination, red flags, and the safe next step. |
| Works with | Muse — install it from this listing's Install section with the copy-paste install prompt. |
| Cost | Free — Skill Harbor House License v1.0 |
| Time | A few minutes to install; about 60 seconds to check one email once you have its headers. |
Example — a « portal is open » email, checked
An example drawn from the real case behind this skill — an email claiming a developer portal had opened:
- Headers first: Authentication-Results shows spf=pass, dkim=pass and dmarc=pass, and the DKIM domain matches the claimed sender rather than a lookalike.
- Links second: every href points directly at the company's real domain — no shorteners, no redirectors, no punycode.
- Verdict: authentic. You still do not click the email's link; you navigate to the official site yourself and find the same notice in your account.
Install
Copy the install package below, then paste it into Muse🧪 Sandbox retest pending · Oct 14, 2026📌 Pinned version: commit aeaa0c8Before you start: tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead. Prerequisites: none for installing the skill files. No account, no key, no cost. Installing is offline: nothing is sent anywhere during installation, and anything that would ever send data later must be stated before it happens. Install "Anti-Phishing Email Check" for me. It checks whether a scary 'action required' email is real or phishing: it verifies the sender's authentication (SPF, DKIM, DMARC), inspects where every link really goes, and compares the message against the official channel before you click anything. Source: https://raw.githubusercontent.com/skill-harbor-hq/house-skills/aeaa0c837868e0972b6cfbfe3d1713b7dde80f23/anti-phishing-email-check/SKILL.md Pinned version: install the code at commit aeaa0c837868e0972b6cfbfe3d1713b7dde80f23 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Helper files, in the same skill folder in the repository (anti-phishing-email-check/): references/triage.md, and LICENSE at the folder root. 1. Download SKILL.md, the helper files and LICENSE into a temporary folder, keeping the helper file inside a references subfolder and LICENSE beside SKILL.md. 2. Compare each file with the fingerprint from Skill Harbor's review of 2026-10-10: - SKILL.md: SHA-256 90d500411ad448f7cbb27073cde6a3183254bc1865c1fd288c7c58ce367b89fb - references/triage.md: SHA-256 7ac22749ecfb49f1fa2a1a74ea6fbd9336f847b641234ec60aa48bb185be0c9d - LICENSE: SHA-256 d7db27db632a56a432d4f883c89507f031215e665f4806dfcd2dea15c0fb8271 If a file does not match, it changed since the review: do not install it yet, tell me what you found and let me decide. 3. Read the files and tell me in plain words: what the skill does when used, whether it connects to a service, whether it reads or sends any personal information or keys, and anything that seems unusual. 4. When I say yes, copy the files into my skills folder, in a folder named "anti-phishing-email-check", keeping the helper files in their subfolders. 5. Check the copy opens correctly (valid frontmatter, files in place) and tell me what was installed, where, and what is left for me to do: nothing to configure — I just ask it to check a suspicious email when one lands. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: only touch the temporary folder and the install target. If something seems off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- aeaa0c8 · 2026-10-13
- Sandbox install test
- Sandbox retest pending · Oct 14, 2026
- Creator identity
- Verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
More house skills
This skill is made by Skill Harbor itself. See all house skills →
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.