CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

audience-segment-builder

Use when the user asks to "build audience segments from my customer list", "make value-based / lookalike seed lists", "set up exclusion / suppression segments", or "map audiences to funnel stages across platforms"; turns the user's OWN customer/CRM/GA4 export into seed audiences, value-based lookalike SEED lists, exclusion/suppression segments, and a cross-platform funnel-stage targeting map, informing the ROAS A (Audience) dimension. Not for building account structure or match types — use campaign-architect; not for organic SERP intent — use keyword-research. 付费广告受众分群/种子人群/排除人群/相似人群种子

Quality

86%

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

78%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, professional instruction skill: a clear skill contract, seven sequenced steps with NEEDS_INPUT checkpoints and a 'Done when' checklist, concrete segment examples, and clean one-level-deep reference pointers. It loses points on repetition of the campaign-architect handoff and on delegating the funnel-stage map and handoff-summary shapes entirely to external files without a minimal inline example. Workflow validation exists but lacks a recovery loop for wholly unusable exports.

Suggestions

Add a compact inline example of the funnel-stage targeting map and the handoff-summary shape (a few lines each), so the two central output artifacts are concrete without chasing external references (actionability).

State the campaign-architect handoff once (e.g. in Next Best Skill) and cut the repetitions in the intro, Skill Contract, scope guard, and Reference Materials (conciseness).

Add an explicit recovery step for wholly unusable exports — what to ask the user for and what minimal artifact to return when parsing fails entirely, complementing the existing no-value-columns fallback (workflow_clarity).

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence (no tutorials on what CRM or lookalike audiences are), but the campaign-architect handoff is repeated five times (intro, Skill Contract, scope guard, Reference Materials, Next Best Skill) and the opening paragraph restates the description nearly verbatim. This fits 'efficient; minor instances of over-explanation that could be trimmed' rather than the lean score-5 anchor.

4 / 5

Actionability

Guidance is concrete for an instruction-only skill: named segment examples ('repeat-buyers-90d', 'high-AOV', 'pricing-page-visitors'), explicit suppression windows (14–30 days), typed profile weights (0.15/0.30/0.10), and an exact save-path template. It stops short of score 5 because the two central output artifacts — the funnel-stage map and the handoff summary — are delegated to external references without even a compact inline example of their shape.

4 / 5

Workflow Clarity

Seven clearly sequenced steps with a 'Done when' completion checklist, NEEDS_INPUT flagging for missing columns, and an explicit degraded-input fallback in step 2 ('still return the segment plan... flag only the missing fields NEEDS_INPUT'). Not score 5: there is no step-level feedback loop, e.g. what to do when an export fails to parse at all or when segment sizes are unusable, so checkpoints are present but not complete.

4 / 5

Progressive Disclosure

No bundle files exist under ./references/, ./scripts/, or ./assets/, and the body is a ~65-line overview that keeps bulk detail in clearly signaled one-level-deep references, each annotated with its purpose ('roas-benchmark.md — ROAS framework, A-dimension items, typed profiles'). This matches the score-5 anchor: clear overview, well-signaled references, content appropriately split.

5 / 5

Total

17

/

20

Passed

Description

92%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 strong: it pairs an explicit 'Use when...' trigger clause with concrete, quoted user phrasings and a precise statement of the four output buckets, and it disambiguates against sibling skills with explicit negative boundaries. The only weakness is that a few natural trigger synonyms (custom audiences, customer match, retargeting) are missing. It is written in third person and stays concrete rather than padded.

DimensionReasoningScore

Specificity

The description lists four concrete deliverables — 'seed audiences', 'value-based lookalike SEED lists', 'exclusion/suppression segments', and a 'cross-platform funnel-stage targeting map' — plus the data inputs (customer/CRM/GA4 export), giving comprehensive coverage of what the skill produces. It clearly matches the score-5 anchor ('Extract text and tables from PDF files, fill forms, merge documents') rather than score 4, because the action coverage is complete for the domain rather than having minor gaps.

5 / 5

Completeness

It explicitly answers both questions: 'Use when the user asks to...' with concrete trigger phrases (when) and 'turns the user's OWN customer/CRM/GA4 export into...' (what). This matches the score-5 example pattern exactly; score 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Quoted natural trigger phrases ('build audience segments from my customer list', 'make value-based / lookalike seed lists', 'set up exclusion / suppression segments', 'map audiences to funnel stages across platforms') provide good coverage with synonyms (exclusion/suppression, lookalike/seed). It falls short of the score-5 anchor because common user phrasings like 'custom audiences', 'customer match', or 'retargeting audiences' are absent.

4 / 5

Distinctiveness Conflict Risk

Explicit negative boundaries — 'Not for building account structure or match types — use campaign-architect; not for organic SERP intent — use keyword-research' — carve out a clear niche with distinct triggers and route near-miss requests to the correct sibling skill. Conflict risk with adjacent marketing skills is minimal, matching the score-5 anchor.

5 / 5

Total

19

/

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

Warning

Total

13

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

ad/research/audience-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.