CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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. 邮件列表分群/生命周期分群/抑制名单/流失召回

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

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 strong, highly structured instruction skill: an unambiguous eight-step workflow with NEEDS_INPUT error handling, dry-run-by-default mutation, a done-when checklist, and concrete segment definitions and commands. The main costs are cross-section repetition of the consent-registry and sibling-skill disclaimers, and heavy dependence on external files for output templates that are not part of this bundle.

Suggestions

State the 'reads memory/consent/, never writes it' rule once (e.g. in Data Sources or Scope guard) and reference it elsewhere in a few words instead of restating the full caveat four times.

Collapse the overlap between Reference Materials, Scope guard, and Next Best Skill — each currently re-lists email-creative-builder, email-sequence-designer, and consent-registry with near-identical annotations; one routing section would tighten the body noticeably.

Inline a minimal example of the segment-map / handoff-summary output shape (or include it as a bundled reference file) so the expected artifact does not depend solely on the external ../../../references/skill-contract.md.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious domain detail, but the consent-registry caveat "this skill reads it, never writes it" / "never writes `memory/consent/`" is restated at least four times (Data Sources, Skill Contract Promotes, Instructions step 6, Reference Materials), and the sibling-skill disclaimers are repeated across the intro, Scope guard, Reference Materials, and Next Best Skill — matching "mostly efficient but... could be tightened". Not a 4: the redundancy is pervasive across sections rather than a few minor trimmable instances; not a 2 because nothing explains concepts Claude already knows and every section carries real information.

3 / 5

Actionability

Concrete, executable guidance throughout: named segment definitions tied to exported columns ("engaged-90d = opened or clicked in last 90 days", "cart-abandoners-7d"), copy-paste commands ("python3 \"${CLAUDE_PLUGIN_ROOT}/scripts/connectors/resend.py\" contacts"), an explicit save path template, and freeze fields (segment_ref, definition_version, definition_hash, evaluated_at). Not a 5: the actual output artifact shapes (handoff summary format, save-results template) are delegated to external skill-contract.md rather than shown, so a reader cannot fully produce the expected output from this file alone; not a 3 because what is present is executable, not pseudocode or vague hints.

4 / 5

Workflow Clarity

Eight clearly sequenced steps with explicit validation checkpoints and error handling: missing columns "become NEEDS_INPUT flags, not guesses", step 6 reconciles the suppression list against consent/suppression snapshot refs, step 7 freezes definitions with version/hash and evaluated_at, mutating connector subcommands are "dry-run by default (--live to execute)", and a "Done when" checklist closes the loop (every size labeled, no raw PII in artifacts, reconciliation or NEEDS_INPUT). This matches the anchor with explicit validation steps, error-recovery paths, and a checklist; a 4 would require missing or merely implicit checkpoints, which is not the case.

5 / 5

Progressive Disclosure

The body is a well-sectioned ~75-line overview keeping the core workflow inline and pointing outward with clearly annotated, one-level-deep links (send-benchmark.md, CONNECTORS.md, SECURITY.md, send-control.md, sibling SKILL.md files). Not a 5: no bundle files exist here (references/, scripts/, assets/ are absent), so the many ../../../ references — including the output templates the skill depends on — cannot be verified and pull essential detail outside this skill's own bundle; not a 3 because the structure and signaling are genuinely good, with nothing inlined that clearly belongs in a separate file.

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.

A model description: explicit quoted trigger phrases, a concrete third-person capability statement, bilingual keywords, and explicit negative scope that routes adjacent jobs to sibling skills. All four dimensions sit at the top anchors with no padding or over-claims.

DimensionReasoningScore

Specificity

The description lists multiple concrete, comprehensive actions: "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" — matching the anchor for several specific concrete actions with comprehensive coverage. It is not below level 5 because no meaningful capability of the skill is left unnamed, and not above because 5 is the scale maximum.

5 / 5

Completeness

Both 'what' and 'when' are answered explicitly and concretely: 'when' via four quoted trigger requests, 'what' via the segment/suppression outputs and the SEND E (Engagement/targeting) purpose. It even adds negative triggers ("Not for scoring EQS or running vetoes — use email-quality-auditor"), exceeding the anchor's requirement rather than fitting the weaker level 4 where 'when' is only implicitly specific.

5 / 5

Trigger Term Quality

It quotes natural user phrasings directly — "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 segments, RFM, cart-abandoner, lifecycle, suppression, unsubscribes, and bounces with synonyms, plus a Chinese keyword tail for bilingual triggers. This matches the comprehensive natural-term coverage anchor; a score of 4 would require noticeably missing common variations, which is not the case.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (pre-send audience segmentation) and actively disambiguates from adjacent skills by name: "Not for scoring EQS or running vetoes — use email-quality-auditor; not for authentication or spam-content checks — use deliverability-qa". This is the minimal-conflict anchor; level 4's 'minor overlap risk with closely related skills' is superseded because the overlaps are explicitly redirected.

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.

Validation — 12 / 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

Path

email/setup/list-segment-builder/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.