CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

inbox-placement-monitor

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声誉趋势

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured instruction-only skill with a clearly sequenced, validation-gated workflow and proper offloading of detail to a genuine reference file. The main costs are token redundancy — the scope guard and EQS disclaimer repeated four times — and an undefined inbox-placement threshold that the verdict logic depends on.

Suggestions

State the scope guard once (in the intro paragraph) and delete the repeats in instruction 1 and the standalone 'Scope guard' paragraph — the boundary is already enforced by the description and Next Best Skill sections.

Define the inbox-placement threshold numerically (or name where the user declares it) in the body or checklist, since steps 3 and 7 both hinge on 'against the inbox threshold' without a value.

Trim the per-step restatement of checklist detail (e.g., provider lists and complaint thresholds) so the body stays an overview and references/placement-telemetry-checklist.md carries the procedure, reducing duplication between the two.

DimensionReasoningScore

Conciseness

The body is dense and free of concept-explaining padding, but the scope guard ("does NOT run the S1 auth pre-flight… does NOT compute the EQS") is repeated four times — in the intro, instruction 1, a standalone Scope guard paragraph, and Next Best Skill — which is more than minor over-explanation. This fits the 3 anchor ('could be tightened') better than 4 ('minor instances'): a full paragraph-level redundancy could be cut without losing information.

3 / 5

Actionability

Guidance is largely executable for an instruction-only skill: concrete thresholds (spam-complaint < 0.1%), typed profile weights (0.30/0.20/0.35/0.25), named data sources per provider, exact memory write paths, a runnable command (`resend.py emails --id <id>`), and three Quick Start invocations. It falls short of 5 because the central "inbox threshold" the placement verdict depends on is never numerically defined or sourced, and the full per-provider procedure is deferred to the reference file.

4 / 5

Workflow Clarity

The eight numbered steps are clearly sequenced (scope → bind → placement → Postmaster → SNDS → delta → sub-items → verdict) with explicit validation checkpoints at each stage: NEEDS_INPUT for missing providers, `binding_status: incomplete` for unbound sends, "no prior baseline means this run becomes the baseline; do not fabricate a delta", and Termination stop conditions. This matches the 5 anchor (explicit validation steps, checklists for complex processes); the workflow is analytical rather than destructive, so no batch-validation cap applies.

5 / 5

Progressive Disclosure

The detailed procedure is correctly split into a real, well-signaled one-level-deep reference (references/placement-telemetry-checklist.md, verified to exist, with an accurate one-line description in Reference Materials). It is not a 5 because many cross-links (../../../references/skill-contract.md, send-benchmark.md, CONNECTORS.md, SECURITY.md, sibling SKILL.md files) point outside the submitted bundle and cannot be verified, and the body duplicates some of the checklist's threshold content rather than staying purely at overview level.

4 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete multi-output 'what', four natural quoted trigger phrases for 'when', third-person voice, and explicit not-for carve-outs that disambiguate it from sibling deliverability skills. The trailing bilingual summary line adds minor redundancy but does not dilute the trigger value.

DimensionReasoningScore

Specificity

The description lists multiple concrete outputs — "per-provider inbox/spam/promotions placement read", "domain/IP reputation trend from Postmaster + SNDS", "send-over-send delta with named regressions", and a "reusable SEND-S placement snapshot" — giving comprehensive, specific coverage of what the skill does. It sits at the 5 anchor rather than 4 because coverage of the skill's actions is complete, not just 'several with minor gaps'.

5 / 5

Completeness

It explicitly answers both questions: "Use when the user asks to…" gives concrete trigger phrases, and the middle clause states exactly what the skill produces. This matches the 5 anchor example's structure (what + when with concrete triggers); a 4 would require the 'when' to be less explicit than the four quoted scenarios.

5 / 5

Trigger Term Quality

Four natural quoted user phrasings ("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", "did placement drop after my last send") plus the domain vocabulary (inbox vs spam, seed-list, Postmaster, SNDS, placement) give comprehensive natural-term coverage. It is not a 4 because the trigger set includes the colloquial variations users would actually say, not just keyword nouns.

5 / 5

Distinctiveness Conflict Risk

The description ends with explicit negative scope — "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" — carving a clear niche with distinct triggers and naming where adjacent needs belong. Minimal conflict risk; not a 4 because the disambiguation is explicit rather than merely implied by specificity.

5 / 5

Total

20

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 25 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

email/deliver/inbox-placement-monitor/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.