Parse and analyze email headers (Received chain, Return-Path, Message-ID) to trace the true origin of a phishing email and validate SPF, DKIM, and DMARC results to confirm or rule out sender spoofing. Use when triaging a suspicious or reported email, investigating a phishing incident, or verifying whether a message's sender domain was spoofed.
67
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Security
1 high severity finding. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill contains curl examples that embed API keys in HTTP headers (e.g., "Key: YOUR_API_KEY", "x-apikey: YOUR_VT_API_KEY"), which instructs placing secrets verbatim into commands and therefore requires the LLM to handle/output secret values directly.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The skill’s runtime workflow reads and parses user-supplied raw email headers/body from local EML/PST-derived files (e.g., `parse_email_file(eml_path)` → `email.message_from_file` and `get_body()`/`get_all()`), so outsider-authored phishing content in the message is directly ingested as free text.
e612f49
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.