find-contact
Resolve a 3CX contact or extension by email, extension, or name
Phishing-simulation results and click-rate trend for a given window
$ npx -y skills add wyre-technology/msp-claude-plugins --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/phishing-resultsContext preview
What this command does when you run it.
Phishing-simulation results and click-rate trend for a given window
description: Phishing-simulation results and click-rate trend for a given window argument-hint: "[window]" arguments: [window]
Cross-vendor phishing-simulation results report: click-rate trend and named repeat clickers over the given window, pulled from whatever phishing-simulation platform the org has connected, with optional correlation against real-world click signal from a connected email-security tool where available.
phishing-simulation connector. Without one, there is no simulation data to report.
1. **Discover available tools.** Call `conduit__search_tools` to determine which phishing-simulation connector is live and its actual tool names (e.g. `knowbe4__list_campaigns`). Also check for a connected email-security tool with phishing-adjacent signal (`proofpoint__list_vap_users`, `avanan__list_threats`) as optional enrichment — never assume it's present.
2. **Resolve the window.** Parse `window` (default `90d` if omitted). Accept shorthand like `30d`, `90d`, `180d`. Pull all campaigns whose run date falls within the window.
3. **Compute click-rate trend** across the campaigns in the window, ordered chronologically, per the `phishing-simulation-analysis` skill. Label trend direction as Improving / Flat / Worsening, or "insufficient history" if fewer than 3 campaigns fall within the window.
4. **Identify repeat clickers** — users with 2+ failures within the window — sorted by failure count then recency. Cross-reference remedial-training completion for each.
5. **Correlate with real-world signal where available.** If an email-security tool with phishing-adjacent data is connected, check each repeat clicker for a matching real-world finding and flag any match as a compounding risk signal. If not connected, note explicitly that this enrichment wasn't performed.
report, e.g. `30d`, `90d`, `180d`.
/awareness-pack:phishing-results
/awareness-pack:phishing-results 180d
/awareness-pack:phishing-results 30d
================================================================================ Phishing Results — window: [window] ================================================================================ CLICK-RATE TREND -------------------------------------------------------------------------------- [client] — [N] campaigns in window — latest: [X]% Trend: [Improving/Flat/Worsening/Insufficient history] REPEAT CLICKERS ([N], sorted by failures then recency) -------------------------------------------------------------------------------- [user] ([client]) — [N] failures, most recent [date] Remedial training complete: [yes/no] Real-world incident match: [yes — summary / no / not checked] TOTAL SUMMARY -------------------------------------------------------------------------------- Campaigns analyzed: [N] Repeat clickers: [N] Compounding-risk matches: [N] ================================================================================
phishing-results report can't be produced without one, and stop rather than fabricating click data.
default `90d`, stating that the fallback was used.
label trend as "insufficient history" rather than asserting a direction.
the core simulation report and note that real-world correlation wasn't performed.
the companion metric to phishing-simulation performance
training completion into a single human risk score
One command to supercharge Claude Code for MSP workflows. Then restart Claude Code. That's it. Documentation: mcp.wyre.ai
Repo: wyre-technology/msp-claude-plugins
Resolve a 3CX contact or extension by email, extension, or name
Search for specific threat patterns in Abnormal Security by sender, recipient, attack type, or keywords
Triage recent email threats detected by Abnormal Security by severity and attack type