CtrlK
BlogDocsLog inGet started
Tessl Logo

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

72

Quality

92%

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

85%Weight 40%Scale 1-3

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

The body is a well-organized, actionable instruction skill with a clear sequenced workflow and a properly separated reference file. Its main weakness is verbosity from repeated scope-guard restatements and overlapping sections that could be consolidated.

Suggestions

State the scope guard once (e.g. in the intro) and reference it rather than repeating the near-verbatim 'does NOT run S1… does NOT compute EQS' block in the Skill Contract, Instructions, and closing Scope Guard sections.

Consolidate the overlapping content between 'Skill Contract', 'Handoff Summary', and 'Instructions' so each section adds distinct information instead of restating the reads/writes/done-when criteria.

Trim the repeated 'Measured / User-provided / Estimated' labeling instructions to a single defined rule early in the procedure rather than re-stating it in nearly every step.

DimensionReasoningScore

Conciseness

Mostly efficient and free of generic concept explanations, but the scope guard ('does NOT run the S1 auth pre-flight… does NOT compute the profile-weighted EQS…') repeats near-verbatim three times and the Skill Contract, Handoff Summary, and Instructions sections overlap materially, so it could be tightened.

2 / 3

Actionability

Concrete and specific guidance throughout — named profile weights (0.30/0.20/0.35/0.25), a hard red line (spam-complaint < 0.1%), per-provider enumeration, example output phrasings ('Gmail domain reputation dropped High → Medium, spam-rate 0.08% → 0.14%'), and a copy-paste resend.py seed command.

3 / 3

Workflow Clarity

A clearly sequenced numbered procedure (steps 1–7) with explicit validation checkpoints — NEEDS_INPUT handling for missing providers, a 'Done when' checklist, and termination rules (visited-set, max-depth 3, ambiguity stop).

3 / 3

Progressive Disclosure

A well-sectioned overview that offloads the detailed per-provider placement/reputation/delta procedure to one real one-level-deep bundle reference (references/placement-telemetry-checklist.md, verified present), with clearly signaled links to external framework docs.

3 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

The description is concrete, trigger-rich, and clearly scoped: it names specific outputs, quotes natural user utterances as triggers, and explicitly fences off two adjacent skills. It is a strong, low-conflict trigger description.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — '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'.

3 / 3

Completeness

Explicitly answers both: 'Use when the user asks to…' (when) and 'produces a per-provider…placement read…' (what), with explicit triggers rather than implied usage.

3 / 3

Trigger Term Quality

Quoted natural-language utterances users would actually say — 'track where my emails are actually landing after I send', 'read my seed-list inbox vs spam vs promotions results', 'did placement drop after my last send' — give good coverage of natural terms.

3 / 3

Distinctiveness Conflict Risk

Clear niche with explicit disambiguation — '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' — making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

Passed

Validation

75%

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

Validation12 / 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: 24 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository
aaron-he-zhu/aaron-marketing-skills
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.