CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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/双重确认/推荐环

Quality

87%

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

73%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 professionally structured strategy skill: a crisp contract (Reads/Writes/Promotes/Done when), a sequenced instruction set with completion gates, and disciplined routing to sibling skills. Its main weaknesses are systematic duplication of the scope guard and sibling handoffs (conciseness) and dependence on out-of-bundle files for key templates and referenced material (progressive disclosure, actionability).

Suggestions

State the scope guard once — the 'does not build the signup UX / write the confirmation emails / record the opt-in' exclusions appear in the intro, the Scope guard paragraph, and again after Instructions; keep a single canonical version.

Consolidate the sibling-skill handoffs: Reference Materials and Next Best Skill both enumerate consent-registry, landing-optimizer, and email-sequence-designer with overlapping descriptions — merge them into one section or cross-reference it.

Inline a minimal example of the 'operation: propose' consent.ndjson payload (and a short handoff-summary template) so the capture-flow spec step does not depend on an external skill-contract.md that may not resolve from the skill directory.

DimensionReasoningScore

Conciseness

The scope exclusions ('It does not build the signup page, write the confirmation email, or record the opt-in') are stated three times — in the intro paragraph, the 'Scope guard' paragraph, and again after Instructions — and the sibling-skill handoffs (consent-registry, landing-optimizer, email-sequence-designer) are enumerated in both Reference Materials and Next Best Skill. The material is otherwise dense and free of concepts Claude already knows, but the systematic duplication is more than the 'minor instances' of the anchor-4 example, so it sits at 'mostly efficient but could be tightened'.

3 / 5

Actionability

For an instruction-only planning skill the guidance is concrete: an exact save path ('memory/email/list-growth-designer/YYYY-MM-DD-<audience-or-goal>-growth-plan.md'), the specific consent-evidence items to capture ('timestamp, source, lawful basis, checkbox wording, IP/UA if used'), the propose mechanism via registry-events.py, and copy-paste Quick Start prompt templates. It is not 5 because the propose-request payload and the handoff-summary shape are deferred to an out-of-bundle skill-contract.md, leaving small execution gaps.

4 / 5

Workflow Clarity

Eight clearly sequenced steps (confirm goal/jurisdiction → inventory → lead magnet → channels → capture flow → referral loop → metrics → compliance caveat) with an explicit 'Done when' checklist of four checkable criteria, missing-data handling ('Measured from the ESP export, or User-provided. Do not invent a baseline'), and human-in-the-loop checkpoints ('On user confirmation, save...', 'ask before writing'). It is not 4 because validation of completion and escalation/termination rules are explicit rather than implicit.

5 / 5

Progressive Disclosure

The body is a well-organized overview with clearly signaled, purpose-labeled, one-level-deep references (Reference Materials lists each link with its role), and SEND/connector/security detail is appropriately pushed to separate files. It is not 5 because the bundle contains none of the referenced files — critical templates (save-results template, handoff summary format) live in an external ../../../references/skill-contract.md, and the deep relative paths (e.g., ../../../influencer/report/landing-optimizer/SKILL.md) are unverifiable from the skill directory.

4 / 5

Total

16

/

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.

An exemplary description: explicit trigger phrasing users would naturally say, a comprehensive and concrete deliverable list, and explicit routing boundaries against adjacent skills. The only nitpick is length — the trailing Chinese summary duplicates the summary field and SEND-S/SEND-N references add internal jargon — but every clause carries information, so no dimension is penalized.

DimensionReasoningScore

Specificity

The description enumerates five concrete deliverables — '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)' — comprehensive and specific with no vague filler. This matches the anchor for multiple specific concrete actions with comprehensive coverage; it is not 4 because there are no meaningful gaps in the deliverable list.

5 / 5

Completeness

It opens with an explicit 'Use when the user asks to...' clause listing concrete trigger phrases and explicitly states what the skill produces, clearly answering both what and when. This is the anchor-5 pattern verbatim; it is not 4 because neither the 'what' nor the 'when' could be made more explicit.

5 / 5

Trigger Term Quality

It quotes natural phrases users would actually say ('"grow my email list"', '"design a lead magnet / signup incentive"', '"set up double opt-in"', '"plan a referral / recommendation loop"') and adds bilingual (Chinese) trigger terms. Synonym pairs are given inline ('referral / recommendation', 'lead magnet / signup incentive'), matching the comprehensive-coverage-with-synonyms anchor; it is not 4 because no common variations are noticeably absent.

5 / 5

Distinctiveness Conflict Risk

Beyond a clear niche, it adds explicit negative boundaries against three adjacent skills ('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'), minimizing wrong-skill triggering. It is not 4 because the disambiguation goes beyond minor overlap avoidance into explicit routing.

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.

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

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

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