← Back to list
inbox-placement-monitor ✓ Security reviewed
Use when the user asks to "track where my emails are actually landing after I send", "read my see…
⚡ Productivity By aaron-he-zhu Version v1.0.0 Updated 2026-09-03
7.3Overall rating

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "inbox-placement-monitor" skill by following the instructions at https://skill123.me/install/inbox-placement-monitor.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/inbox-placement-monitor.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 7 KB

About this skill

Overview

Use when the user asks to "track where my emails are actually landing after I send", "read my seed-list inbox vs spam vs promotions results", "trend my Gmail Postmaster / Microsoft SNDS reputation", or "did placement drop after my last send"; produces a per-provider inbox/spam/promotions placement read, a domain/IP reputation trend from Postmaster + SNDS, a send-over-send delta with named regressions, and a reusable SEND-S placement snapshot on your own exported telemetry. Not for the pre-send SPF/DKIM/DMARC auth pre-flight — use deliverability-qa; not for computing the EQS or running the vetoes — use email-quality-auditor. 邮件收件箱落点监测/收件箱vs垃圾邮件/Postmaster声誉趋势

Source

  • Repo: https://github.com/aaron-he-zhu/aaron-marketing-skills
  • Path: email/deliver/inbox-placement-monitor

Evaluation

AI-evaluated 2026-09-03: Clear per-provider placement read procedure with receipt/segment binding, no-fabrication rules, NEEDS_INPUT handling instead of pass-by-default, and explicit scope guards against sibling overlap. Keyless own-account telemetry makes prerequisites realistic, though seed-test workflow is manual and the audience is email deliverability specialists; send automation requires explicit per-operation authorization.

Score breakdown

Quality
8.0
Usability
6.0
Security
8.0
Popularity
7.0