CtrlK
BlogDocsLog inGet started
Tessl Logo

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. 邮件偏好中心/降频阶梯设计/退订替代降档

71

Quality

88%

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

77%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 thorough, well-sequenced instruction skill with strong workflow checkpoints and clean one-level-deep referencing. Its main liability is repetition of the same scope-boundary language across multiple sections, which inflates token cost without adding clarity.

Suggestions

State the email-sequence-designer / consent-registry / email-quality-auditor boundary once in the Scope Guard and reference it from elsewhere instead of restating it verbatim in the Skill Contract, Instructions steps 6–7, Reference Materials, and Next Best Skill.

Inline a compact version of the handoff/save-results output shape (from skill-contract.md) so Claude can produce the deliverable without a follow-up file read.

Trim the trailing CJK tag ('邮件偏好中心/降频阶梯设计/退订替代降档') from the description — it duplicates the displayName/summary and adds tokens that do not aid triggering.

DimensionReasoningScore

Conciseness

Mostly efficient domain-specific content, but the scope boundaries (the email-sequence-designer / consent-registry / auditor division) are restated nearly verbatim in the Skill Contract, Instructions steps 6–7, the Scope Guard paragraph, Reference Materials, and Next Best Skill — material that could be tightened.

3 / 5

Actionability

Concrete, specific guidance throughout: example topic groups, a cadence-tier ladder (weekly → monthly → quarterly → pause 90 days), an ordered opt-down path, and copy-paste-style mapping rules ('topic X → suppress topic-X stream; monthly tier → cap sends to 1/month'). It is instruction-only, so the absence of code is not penalized; the gap is that the actual handoff/save output format is delegated to an external template not shown inline.

4 / 5

Workflow Clarity

Eight explicitly numbered steps with a 'Done when' completion checklist, 'Decision Gates' (stop-and-ask vs. continue-silently), data-provenance labeling (Measured/User-provided/Estimated), and a feedback loop in the termination note (auditor returns BLOCK on N1 → route back to repair the opt-down path).

5 / 5

Progressive Disclosure

Well-organized sections (Quick Start, Skill Contract, Data Sources, Instructions, Decision Gates, Save Results, Reference Materials, Next Best Skill) with clearly signaled, one-level-deep references to sibling skills and shared docs ([send-benchmark.md], [skill-contract.md], [CONNECTORS.md], [SECURITY.md]); no nested reference chains.

5 / 5

Total

17

/

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 dense, well-structured description that explicitly covers what it does, when to invoke it, and where it stops relative to sibling skills. Its only weakness is verbosity — the negative-boundary clauses and trailing CJK summary make it longer than ideal.

DimensionReasoningScore

Specificity

Names four concrete deliverables — 'a preference-center field spec', 'a frequency/topic opt-down ladder', 'a preference-to-suppression mapping', and 'a SEND N-dimension sub-item note' — giving comprehensive coverage of what the skill produces.

5 / 5

Completeness

Explicitly answers both 'what' (the four deliverables produced) and 'when' (a leading 'Use when the user asks to...' clause with concrete trigger phrases).

5 / 5

Trigger Term Quality

Quotes multiple natural user phrasings — "build a preference center", "set up a frequency opt-down ladder", "give people a step-down instead of unsubscribe", "design a topic/cadence preference page" — covering the natural ways a user would request this.

5 / 5

Distinctiveness Conflict Risk

Three explicit 'Not for...use <sibling-skill>' boundary clauses (email-sequence-designer, consent-registry, email-quality-auditor) carve out a clear niche with minimal conflict risk.

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.

Validation13 / 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
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.