Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    SOC Email Threat Triage Assistant

    1

    Triages suspicious emails into analyst-ready evidence, risk scoring, containment guidance, and escalation notes.

    $2.84

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    SOC Email Threat Triage Assistant

    SOC Email Threat Triage Assistant

    Example session with this skill installed

    I have a suspicious email with failed SPF. Can you analyze these headers and generate an analyst report with a disposition?

    • Read your context and instructions
    • Compiled the soc email threat

    I have analyzed the provided headers. The SPF failure and mismatched Return-Path suggest a high-confidence spoofing attempt.

    SOC Email Triage Report

    Executive Disposition: Flagged for analyst review
    Confidence Score: 85/100
    Reasoning: SPF hard fail from sender IP 192.0.2.1. Return-Path (attacker@malicious.com) does not align with From address (billing@trustedcorp.com).

    Authentication Summary

    CheckStatusDetails
    SPFFAILIP 192.0.2.1 not in authorized list
    DKIMPASSSigned by trustedcorp.com
    DMARCFAILAlignment failed due to SPF

    Extracted Indicators

    TypeValue (Defanged)SourceStatus
    URLhxxps[://]urgent-invoice-portal[.]net/loginBodyPending Enrichment
    IP192[.]0[.]2[.]1HeadersKnown bad (Reputation)
    Hash853cf9... (SHA256)AttachmentNo detections reported

    Analyst Actions

    1. Containment: Block sender IP 192.0.2.1 at the perimeter.
    2. Purge: Search and remove messages with Subject "Urgent: Unpaid Invoice" from all mailboxes.
    3. Validation: Verify if any user navigated to the defanged URL via proxy logs.

    Next steps

    • Run tools/render_triage_report.py to generate a redacted version for your ticketing system.
    • Check VirusTotal for the pending URL enrichment status.
    • Confirm if the recipient interacted with the attachment.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Manual email triage is slow, inconsistent, and prone to analyst error. This skill provides a SOC-style copilot to turn suspicious Outlook messages into structured, evidence-backed reports using a hash-first, consent-aware workflow.

    What it does

    • Workflow automation: Guides the deployment and configuration of a reference n8n triage workflow.
    • Authentication analysis: Reviews SPF, DKIM, and DMARC alignment plus Received-hop timing for spoofing indicators.
    • Indicator enrichment: Manages the extraction and defanging of URLs, IPs, and hashes for threat intelligence lookups.
    • Structured reporting: Generates analyst-ready Markdown and JSON reports with executive dispositions and confidence levels.
    • Offline preflight: Processes local RFC 5322 .eml files to extract metadata without network exposure.

    How it works

    1. Preflight: The user confirms authorization, mailbox scope, and data-sharing consent for external services.
    2. Ingestion: The skill analyzes provided headers or guides the n8n workflow to extract indicators like hashes and URLs.
    3. Enrichment: It interprets provider signals (like VirusTotal) using a cautious, specific vocabulary.
    4. Finalization: It produces a formatted report including an indicator table and containment suggestions.

    Frameworks & tools

    The skill is designed for n8n orchestration using Python-based offline tools (triage_eml.py). It integrates with Microsoft Outlook for ingestion and supports VirusTotal for threat intelligence enrichment.

    Why this beats prompting it yourself

    Standard prompts often hallucinate security verdicts or fail to handle malformed headers correctly. This skill uses a fixed vocabulary for provenance and a schema-validated reporting structure to ensure every analysis remains grounded in evidence rather than model guesswork.

    Use cases

    • Review a suspicious email manually by providing redacted headers and body.
    • Deploy a reference n8n workflow for automated mailbox monitoring.
    • Generate a standardized incident report for a ticketing system or SIEM.
    • Perform a privacy-preserving batch digest of local .eml files.

    Known limitations

    The skill cannot directly access mailboxes or credentials. It requires a pre-configured n8n instance and valid API keys for threat intelligence providers.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.

    Requires external n8n instance and threat-intel API keys. Cannot directly access credentials or mailboxes. Not a certified malware detector.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 day ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Listed1 day ago

    What's inside

    Frequently Asked Questions

    This skill solves the problem of manual, inconsistent email analysis by providing a structured framework that converts suspicious emails into evidence-based security reports, reducing human error and analyst fatigue.

    No, the skill is designed for privacy; it processes metadata locally using an offline preflight tool and requires your explicit consent and pre-configured API keys before sending any indicators to external threat intelligence providers.

    You will receive the n8n workflow configuration files, the Python-based 'triage_eml.py' tool for offline processing, and comprehensive documentation for deployment and API integration.

    The skill requires a self-hosted or cloud n8n instance and a Microsoft Outlook account for ingestion; it is compatible with any AI agent platform that supports n8n orchestration.

    Unlike basic prompts, this skill uses a schema-validated reporting structure and a fixed security vocabulary to prevent AI hallucinations, ensuring that every verdict is grounded in technical evidence like SPF/DKIM alignment.

    The skill is built to handle standard RFC 5322 (.eml) files and Outlook headers, and updates are periodically released to ensure compatibility with the latest n8n nodes and threat intelligence API schemas.

    New in Security