CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

list-hygiene-monitor

Use when the user asks to "watch my list health over time", "flag decaying / unengaged subscribers on a schedule", "why is my open rate drifting down / bounces creeping up", or "build me a re-permission and prune worklist"; runs the scheduled SEND list-decay + suppression-drift watch — an engagement-recency cohort read (30/90/180/365-day), hard-bounce and spam-complaint trend vs benchmark, suppression-list growth/leakage check, and a segmented re-permission / sunset / prune worklist tied to SEND S (list hygiene) and E (engagement-decay) sub-items. Not for the one-time pre-send authentication pre-flight — use deliverability-qa; not for the consent/suppression record itself — use consent-registry; not for computing the EQS or enforcing vetoes — use email-quality-auditor. 邮件列表健康度监控/退订漂移/沉睡用户清理

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

81%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 strong, highly actionable body: concrete numbers, executable connector commands, a well-sequenced validated workflow, and a real one-level-deep reference file carrying the detail. The main cost is repetition — a duplicated scope guard and repeated sibling-skill pointers — which inflates token cost without adding guidance.

Suggestions

Delete the standalone "Scope guard" paragraph after the Instructions (or the equivalent sentence in the intro) — the boundary is stated twice nearly verbatim.

Consolidate the sibling-skill pointers: keep the "Next Best Skill" section and trim the repeated deliverability-qa / email-quality-auditor / reactivation-specialist explanations in the intro, Skill Contract, and Reference Materials.

Let references/hygiene-checklist.md own the numeric detail (cohort bands, thresholds, profile weights) and keep only the bands' names in SKILL.md to sharpen the overview/reference split.

DimensionReasoningScore

Conciseness

The body is information-dense with no filler explaining concepts Claude already knows, but it is noticeably repetitive and could be tightened: the scope guard appears nearly verbatim twice (intro paragraph and the closing "Scope guard" section), reactivation-specialist is pointed to three times, and deliverability-qa / email-quality-auditor are each re-explained in multiple sections. This sits at 'mostly efficient but includes some unnecessary content that could be tightened' rather than the minor-trim level 4.

3 / 5

Actionability

Guidance is fully concrete and executable: exact cohort bands ("active (≤30d), cooling (31–90d), dormant (91–180d), deep-dormant (181–365d)"), a numeric red line ("spam-complaint red line < 0.1%"), typed-profile weights ("S 0.30 / 0.20 / 0.35 / 0.25"), exact memory paths, and copy-paste commands such as `python3 "${CLAUDE_PLUGIN_ROOT}/scripts/connectors/resend.py" contacts --limit 100` and the ledger record/diff loop. Per the instruction-skill note, the absence of more code is not penalized since the procedural guidance is this specific.

5 / 5

Workflow Clarity

The seven numbered steps are clearly sequenced with explicit validation checkpoints and feedback handling: "If no prior baseline is supplied, mark the trend NEEDS_INPUT ... never invent a delta", "evidence-based, never pass-by-default", leakage routed as an N1 candidate rather than self-verdicted, plus a "Done when" contract and termination rules with an ambiguity stop. This matches the top anchor (clear sequence, explicit validation, error/stop loops).

5 / 5

Progressive Disclosure

Good structure: the body is a well-sectioned overview and the one bundle file, references/hygiene-checklist.md, exists, is one level deep, clearly signaled, and genuinely holds the detailed rubric (threshold tables, decision rules) — matching the level-4 anchor. It falls short of 5 because the body re-inlines a fair amount of the checklist's specifics (cohort bands, thresholds, weights) rather than cleanly splitting, and navigation leans on many cross-repo paths outside the bundle.

4 / 5

Total

17

/

20

Passed

Description

92%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.

An exemplary description: concrete capabilities with numeric parameters, natural quoted trigger phrases, explicit what/when, and explicit negative boundaries against sibling skills. The only weakness is a handful of missing common synonyms ("list cleaning", "inactive subscribers") and a length that flirts with padding, though nearly every clause is load-bearing.

Suggestions

Add one or two of the most common user phrasings for this job — e.g. "clean my email list" or "what should I do with inactive subscribers" — to the trigger list.

Trim the internal framework jargon (e.g. "tied to SEND S (list hygiene) and E (engagement-decay) sub-items") to shorten the description without losing trigger value.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with parameters: "engagement-recency cohort read (30/90/180/365-day)", "hard-bounce and spam-complaint trend vs benchmark", "suppression-list growth/leakage check", and a "segmented re-permission / sunset / prune worklist" — comprehensive coverage of the skill's capabilities. It clearly exceeds the level-4 anchor ('several specific actions; minor gaps') since every component of the watch is explicitly named.

5 / 5

Completeness

Both halves are explicit: the "what" is the scheduled list-decay + suppression-drift watch with four named components, and the "when" opens with 'Use when the user asks to...' followed by four concrete quoted trigger phrases. This matches the level-5 anchor pattern (clear what + when with concrete trigger phrases), and additionally supplies negative boundaries for when not to use it.

5 / 5

Trigger Term Quality

Strong natural trigger phrases users would actually say ("watch my list health over time", "why is my open rate drifting down / bounces creeping up", "build me a re-permission and prune worklist") with good synonym variation (decaying, unengaged, drifting, creeping). A few common variations are still missing — e.g. "clean my email list" / "list cleaning" and "inactive subscribers" — which keeps it at the 'good coverage, a few natural terms missing' anchor rather than fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

The description explicitly disambiguates against three sibling skills ("Not for the one-time pre-send authentication pre-flight — use deliverability-qa; not for the consent/suppression record itself — use consent-registry; not for computing the EQS or enforcing vetoes — use email-quality-auditor"), carving a clear recurring-hygiene niche with minimal conflict risk.

5 / 5

Total

19

/

20

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.

Validation — 12 / 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: 27 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

Path

email/setup/list-hygiene-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.