CtrlK
BlogDocsLog inGet started
Tessl Logo

list-growth-designer

Use when the user asks to "grow my email list", "design a lead magnet / signup incentive", "set up double opt-in", or "plan a referral / recommendation loop"; produces a list-growth plan — acquisition channels, lead-magnet / incentive concepts, a compliant double-opt-in capture-flow spec, referral-loop mechanics, and subscriber-growth / cost-per-opt-in targets (labeled Estimated) — that feeds SEND-S (consent quality captured at acquisition) and SEND-N (lifecycle entry). Not for the signup page/popup UX itself — use landing-optimizer; not for recording the opt-in — use consent-registry; not for the confirmation-email copy — use email-creative-builder. 邮件列表增长/lead magnet/双重确认/推荐环

73

Quality

92%

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

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.

A well-structured, actionable strategy skill with clear workflow sequencing and one-level-deep references. Its main weakness is redundancy — the scope guard and several cross-skill handoffs are restated multiple times, inflating the token budget without adding guidance.

Suggestions

Collapse the two 'Scope guard' paragraphs (top of body and after Instructions) into a single canonical statement; the second is a near-duplicate of the first.

De-duplicate the consent-registry and SEND-S/SEND-N handoff references — they are restated in Skill Contract, Instructions, Reference Materials, and Next Best Skill; keep the canonical version in one place and link outward.

Trim the Reference Materials section to entries not already linked inline in Reads/Writes/Promotes, since most of those links are repeated verbatim earlier in the body.

DimensionReasoningScore

Conciseness

Mostly efficient domain guidance, but the Scope guard is stated twice (top of body and again after the Instructions) and consent-registry / S-N framing are re-explained multiple times; could be tightened. Not a 3 because the repetition is unnecessary, not a 1 because it never pads with concepts Claude already knows.

2 / 3

Actionability

For an instruction-only skill the guidance is concrete and specific — named consent-evidence fields (timestamp, source, lawful basis, checkbox wording, IP/UA), owned/earned/paid channel split, explicit memory paths, and labeled metric categories. Per scoring_notes, absence of code is not penalized when guidance is this actionable.

3 / 3

Workflow Clarity

Eight numbered steps are clearly sequenced with a 'Done when' completion checklist, checkable targets ('State the goal as a checkable target'), and termination rules (visited-set, max-depth, ambiguity stop). Not a 2 because explicit checkpoints are present; this is a planning skill so the destructive-operation feedback-loop cap does not apply.

3 / 3

Progressive Disclosure

No bundle directories (references/, scripts/, assets/) are present, so scoring is against the written structure: well-organized sections (Quick Start, Skill Contract, Data Sources, Instructions, Reference Materials, Next Best Skill) with one-level-deep, clearly signaled markdown links. Not a 2 because references are clearly signaled and not deeply nested.

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.

A strong, specific description with natural trigger phrasings, explicit when/what guidance, and clear scope exclusions that distinguish it from sibling skills. The trailing CJK summary tag is harmless redundancy.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'acquisition channels, lead-magnet / incentive concepts, a compliant double-opt-in capture-flow spec, referral-loop mechanics, and subscriber-growth / cost-per-opt-in targets' — matching the multi-action anchor rather than the single-domain anchor at 2.

3 / 3

Completeness

Explicitly answers both 'what' ('produces a list-growth plan ...') and 'when' ('Use when the user asks to ...'), with an explicit trigger clause; not capped at 2 since the 'Use when' guidance is present.

3 / 3

Trigger Term Quality

Quotes natural user phrasings ('grow my email list', 'design a lead magnet / signup incentive', 'set up double opt-in', 'plan a referral / recommendation loop') that users would actually say, giving good coverage rather than the partial coverage at 2.

3 / 3

Distinctiveness Conflict Risk

Clear niche (owned email-list growth strategy) plus explicit 'Not for ... use landing-optimizer / consent-registry / email-creative-builder' exclusions make it unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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: 26 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.