CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

preference-frequency-manager

Use when the user asks to "build a preference center", "set up a frequency opt-down ladder", "give people a step-down instead of unsubscribe", or "design a topic/cadence preference page"; produces a preference-center field spec, a frequency/topic opt-down ladder (down-tier paths that substitute for a hard unsubscribe), a preference-to-suppression mapping, and a SEND N-dimension sub-item note on preference-center / frequency options offered. Not for the lifecycle flow map or cadence governance — use email-sequence-designer; not for the consent/suppression record itself — use consent-registry; not for computing EQS or ruling the N1 unsubscribe veto — use email-quality-auditor. 邮件偏好中心/降频阶梯设计/退订替代降档

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a well-structured instruction skill: concrete step-by-step guidance with explicit decision gates, a done-when checklist, and careful scope routing. Its main costs are heavy repetition of the same exclusion statements (four-plus restatements) and reliance on reference files that live outside the skill bundle, plus output formats that are described but never templated.

Suggestions

Consolidate the boundary/exclusion statements (currently repeated in the intro, step 7, the Scope guard, Reference Materials, and Next Best Skill) into a single 'Out of scope' table naming the owning skill per item.

Add a worked mini-template for the two core outputs — e.g., a 3-row choice-to-rule mapping table (topic mute / monthly tier / pause) and a short field-spec skeleton — so the emitted artifacts are copy-paste shaped rather than enumerated.

Ship the referenced detailed material (skill-contract.md, send-benchmark.md, CONNECTORS.md, SECURITY.md excerpts relevant here) inside the skill's own references/ directory, or inline the one or two sections actually needed, since every current reference resolves outside the bundle.

DimensionReasoningScore

Conciseness

The eight instruction steps are substantive, but the same boundary statements (not the N1 verdict, not the consent record, not EQS, not lifecycle flows) are restated in the intro paragraph, step 7, the Scope guard paragraph, Reference Materials, and Next Best Skill — at least four redundant passes. This is 'mostly efficient but could be tightened' rather than anchor 2, since the padding is concentrated in repetition rather than explaining concepts Claude already knows.

3 / 5

Actionability

Guidance is largely executable for an instruction-only skill: the mapping format is exemplified ('topic X → suppress topic-X stream; monthly tier → cap sends to 1/month; pause 90d → suppress until date, then resume prior tier'), tier ladders are concrete, and Decision Gates give defaults. It stops short of anchor 5 because the field-spec output itself is only enumerated ('topic groups, cadence tiers, channel toggles, save/confirm behavior') rather than shown as a template or worked example.

4 / 5

Workflow Clarity

The 8 steps are clearly sequenced with cross-skill dependencies, a 'Done when' checklist, explicit Stop/Continue decision gates, and an external repair loop ('if it returns BLOCK on N1, route back here to repair the opt-down path'). Not anchor 5 because there is no in-process validation step where the emitted spec/mapping is checked against the Done-when criteria before handoff — checkpoints exist but the verify-fix-retry loop sits only at the routing level.

4 / 5

Progressive Disclosure

The Reference Materials section is well-signaled with per-file purpose descriptions and all references are one level deep. It does not reach 5 because no bundle files (references/, scripts/, assets/) exist in this skill — every referenced file (send-benchmark.md, skill-contract.md, CONNECTORS.md, SECURITY.md, sibling SKILL.mds) resolves to paths outside the skill bundle, so the detailed material is not actually shipped alongside the overview.

4 / 5

Total

15

/

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.

A strong description: explicit what-and-when structure, concrete quoted trigger phrases, four named deliverables, and unusually thorough negative boundaries that disambiguate it from three sibling skills. The only gap is a handful of missing natural synonyms for the trigger space.

DimensionReasoningScore

Specificity

The description enumerates four concrete deliverables — 'a preference-center field spec', 'a frequency/topic opt-down ladder (down-tier paths that substitute for a hard unsubscribe)', 'a preference-to-suppression mapping', and 'a SEND N-dimension sub-item note' — giving comprehensive, specific coverage of what the skill produces. It clearly exceeds the 4 anchor ('several specific actions; minor gaps') since the full output surface is named.

5 / 5

Completeness

It explicitly answers both questions: 'Use when the user asks to…' supplies concrete trigger phrases, and 'produces a preference-center field spec…' states the what in full. This matches the 5 anchor's structure (both what and when with concrete trigger phrases), not the 4 anchor where 'when' is only loosely specified.

5 / 5

Trigger Term Quality

Quoted triggers like "build a preference center", "set up a frequency opt-down ladder", and "design a topic/cadence preference page" are natural user phrasings with good coverage. It falls short of 5 because common variants users would say — 'email preferences', 'unsubscribe page', 'reduce email frequency', 'let people choose what they get' — are missing.

4 / 5

Distinctiveness Conflict Risk

Beyond a clear niche, it carries explicit negative routing — 'Not for the lifecycle flow map or cadence governance — use email-sequence-designer; not for the consent/suppression record itself — use consent-registry; not for computing EQS or ruling the N1 unsubscribe veto — use email-quality-auditor' — minimizing conflict with sibling skills. Minimal conflict risk places it at the 5 anchor rather than 4's 'minor overlap risk'.

5 / 5

Total

19

/

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: 29 suspicious

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

email/nurture/preference-frequency-manager/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.