CtrlK
BlogDocsLog inGet started
Tessl Logo

list-segment-builder

Use when the user asks to "build email segments from my list", "make engaged / lapsed / RFM segments", "set up cart-abandoner or lifecycle-stage audiences", or "build a suppression list of unsubscribes and bounces"; turns the user's OWN list/CRM/GA4/ecommerce export into behavioral, attribute, and lifecycle-stage segments plus a suppression list, with per-segment sizes labeled Measured/Estimated, informing the SEND E (Engagement/targeting) dimension. Not for scoring EQS or running vetoes — use email-quality-auditor; not for authentication or spam-content checks — use deliverability-qa. 邮件列表分群/生命周期分群/抑制名单/流失召回

67

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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, actionable instruction skill with a clear sequenced workflow and good reference navigation. Its main weakness is repetition of scope/boundary statements and mild verbosity that could be trimmed.

Suggestions

Consolidate the repeated scope-guard / negative-boundary text (Data Sources, Scope guard, Next Best Skill) into a single canonical statement to reduce token cost.

Add an explicit validate→fix→retry loop for the batch segmentation pass (e.g. re-run NEEDS_INPUT reconciliation until no flags remain) to lift workflow_clarity.

Move the inline SEND-E weighting rationale out of step 1 into send-benchmark.md, keeping only the decision rule inline.

DimensionReasoningScore

Conciseness

The body is mostly efficient but repeats the same scope/negative-boundary messaging across Data Sources, the Scope guard callout, and Next Best Skill, and re-explains the SEND E dimension several times — it could be tightened without losing substance.

3 / 5

Actionability

It gives concrete, executable guidance — named segment definitions with explicit rules (e.g. engaged-90d = opened or clicked in last 90 days), specific write paths, a runnable resend.py command, and NEEDS_INPUT handling — with only minor gaps since the segment-building logic itself is instructional rather than coded.

4 / 5

Workflow Clarity

An 8-step numbered sequence is clearly laid out with verification checkpoints (Done-when criteria, NEEDS_INPUT flags, consent-registry reconciliation, definition hash/version freeze); it falls short of a 5 only because there is no explicit validate→fix→retry feedback loop for the batch list operation.

4 / 5

Progressive Disclosure

The SKILL.md is a well-organized overview with a dedicated Reference Materials section of clearly signaled, one-level-deep links and logical sections; it stops short of 5 because all references are external cross-skill paths with no local bundle files to confirm, and some referenceable detail is inlined.

4 / 5

Total

15

/

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.

The description is exemplary: third-person voice, concrete actions, natural trigger phrases, explicit what/when, and clear disambiguation from sibling skills. It is somewhat dense and jargon-laden (SEND E dimension, EQS) but that does not detract from the scored dimensions.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — building behavioral, attribute, and lifecycle-stage segments plus a suppression list, with sizes labeled Measured/Estimated — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

It explicitly answers both what (turns list/CRM/GA4/ecommerce exports into segments + suppression list) and when (a 'Use when...' clause with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

It quotes natural phrases a user would actually say ('build email segments from my list', 'make engaged / lapsed / RFM segments', 'set up cart-abandoner or lifecycle-stage audiences', 'build a suppression list of unsubscribes and bounces'), covering synonyms and variations comprehensively.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (email list segmentation / suppression) and adds explicit negative boundary guidance ('Not for scoring EQS — use email-quality-auditor; not for authentication or spam-content checks — use deliverability-qa'), minimizing conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation12 / 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: 30 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

12

/

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.