Menu
SkillsMP has collected 13 skills from danielrosehill/Claude-SpamHole-Plugin. Open a skill to review its source and details.
Showing 13 of 13 collected skills.
One-time setup for AdGuard Home integration. Captures the AdGuard Home base URL, credentials, and target blocklist filename, validates connectivity, and persists to corpus/config.json. Use before adguard-push.
Push the user's accumulated tracking-pixel + ad-tracker domains from the SpamHole corpus into a self-hosted AdGuard Home instance, using the credentials configured by adguard-configure. Network-layer block — every device on the LAN benefits, not just one…
Run the full SpamHole analysis pipeline on a single email — semantic spam reasoning, tracking-pixel detection, sender block, processed-emails log, markdown report. Use when the user wants a deep dive on one email rather than the lighter capture-spam-sample…
Create a server-side Gmail filter that auto-trashes (or labels + archives) future mail from a sender, via an available email MCP. Falls back to recording the block in the local sender-blocklist.json if no MCP is wired up. Use when the user says "block this…
Process every unanalysed .eml file in the user's corpus inputs/emails/ directory through the full analyse-email pipeline. Skips files that already have a corresponding analysis report. Use when the user has dropped many .eml files into the corpus at once.
Capture an unsolicited email into the user's SpamHole corpus, ask why it's spam (what pattern it represents), copy the raw email into the corpus, suggest a filter pattern, suggest system-prompt tuning to catch similar emails, optionally push a server-side…
Strip per-recipient identifiers from the user's tracking inventories and prepare a redacted contribution suitable for opening a PR against collaborative public anti-tracking lists (EasyPrivacy, hagezi, oisd, Pi-hole community, AdGuard's tracker filter).…
Draft (and optionally send) a manual unsubscribe-request reply to a spam sender — used when the email has no working List-Unsubscribe header or the user wants to make the request human-to-human. Threads on the original message via the available email MCP. Use…
Aggregate the user's accumulated tracking-domains.json + ad-trackers.json into a portable DNS blocklist (Pi-hole / AdGuard / hosts / dnsmasq formats). Writes to corpus/exports/. Use when the user wants to push their pixel inventory to a network-level blocker.
Bulk scan of recent inbox messages (default last 30) for tracking pixels and ad-tracker beacons. For every detection logs which email it came from, sender, time, recipient, the raw pixel URL, and a suggested block pattern. Appends to the user's tracking…
Scan a single email (raw .eml or live message via email MCP) for tracking pixels and ad-tracker beacons, then append every detected pixel host to the user's tracking inventories (tracking-domains.json + ad-trackers.json). Use when the user wants to surgically…
First-run setup for SpamHole. Creates the user's spam-corpus workspace (configurable path) and seeds the JSON inventories — tracking-domains, sender-blocklist, processed-emails, ad-trackers. Use when the user first installs the plugin or wants to point it at…
Summarise the user's accumulated tracking-pixel and ad-tracker inventory — totals by type, top domains, top senders, recent additions. Read-only — does not modify any inventory. Use when the user wants visibility into what their corpus has captured.