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

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%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 well-structured, actionable strategy skill: concrete numbered guidance, explicit done-when and termination checkpoints, and clean one-level-deep reference navigation. The only meaningful weakness is repetition of the scope-guard statement and SEND framing across sections, which trims slightly from full token efficiency.

Suggestions

Consolidate the two explicit "Scope guard" paragraphs (after the intro and after the Instructions) into a single canonical statement to remove redundancy and save tokens.

Reduce repeated SEND-S / SEND-N framing to one defining mention near the top and refer back to it rather than restating the framing in the Skill Contract, Instructions, and Reference Materials sections.

Dimension	Reasoning	Score
Conciseness	Body is mostly lean, task-oriented prose with no padding of concepts Claude already knows, but the scope-guard statement is repeated ("Scope guard" appears both after the intro and after the Instructions) and the SEND-S/SEND-N framing recurs across sections, leaving minor trim opportunities versus the fully-lean anchor.	4 / 5
Actionability	Instruction-only guidance is concrete and specific: 8 numbered steps name exact deliverables ("timestamp, source, lawful basis, checkbox wording, IP/UA"), exact file paths ("memory/email/list-growth-designer/...", "memory/events/consent.ndjson"), and an exact protocol ("operation: propose request to registry-events.py").	5 / 5
Workflow Clarity	Steps are clearly sequenced with an explicit "Done when" checklist, a "Primary next skill" handoff, ask-before-write guards, and Termination rules (visited-set check, max-depth:3, ambiguity stop) providing explicit checkpoints and feedback guidance.	5 / 5
Progressive Disclosure	Clear overview with well-organized sections (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) and well-signaled one-level-deep markdown links to sibling references; no nested reference chains. No local bundle files exist to verify, but external reference structure is appropriately shallow.	5 / 5
	Total	19 / 20 Passed

Description

95%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, well-scoped description that pairs concrete trigger phrases with an explicit enumeration of deliverables and clear negative boundaries against sibling skills. The only minor weakness is that several deliverables are framed as plan components rather than discrete actions.

Dimension	Reasoning	Score
Specificity	Lists several 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"), but some are plan components framed as concepts rather than discrete actions and the SEND-S/SEND-N framing is abstract, leaving minor coverage gaps versus the comprehensive anchor.	4 / 5
Completeness	Explicitly answers both what ("produces a list-growth plan — ...") and when ("Use when the user asks to ...") with concrete trigger phrases, plus a clear negative-scope statement.	5 / 5
Trigger Term Quality	Quotes natural phrases a user would actually say ("grow my email list", "design a lead magnet / signup incentive", "set up double opt-in", "plan a referral / recommendation loop") with synonym coverage (lead magnet / signup incentive, referral / recommendation).	5 / 5
Distinctiveness Conflict Risk	Clear niche (owned email list growth strategy) with explicit out-of-scope disambiguation routing to landing-optimizer, consent-registry, and email-creative-builder, minimizing wrong-skill triggering.	5 / 5
	Total	19 / 20 Passed

Validation

81%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 888dd38

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.