Agent skill

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. 付费广告受众分群/种子人群/排除人群/相似人群种子

aaron-he-zhu2,508★ · 1 repos on radarProfile →
claude-codeApache-2.0
Install
npx skills add aaron-he-zhu/aaron-marketing-skills --skill audience-segment-builder --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Version: 19.1.0
Requires: Claude Code and compatible agent-skill hosts
Path: ad/research/audience-segment-builder/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,508
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Audience Segment Builder 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. It defines **who the audiences are and how they are seeded and suppressed** — campaign-architect then consumes these segments into account structure and match types; this skill does not build campaigns, and it is distinct from organic keyword-research, which reads SERP intent rather than paid segments. ## Quick Start ``` Build audience segments from my customer export: [path]. Goal is DR. Platforms: Google + Meta. ``` ``` Make a value-based lookalike SEED list from my top customers and the exclusion list for people who already bought. [customer CSV] ``` ``` Map my GA4 audiences to funnel stages so I can reuse the same targeting across Google and Meta. [GA4 audience/demographics export] ``` ## Skill Contract **Expected output**: a set of named audiences in four buckets — (1) **seed audiences** grouped by trait/behavior, (2) **value-based lookalike SEED lists** (the high-value seed rows themselves, not a platform key), (3) **exclusion/suppression segments** (existing customers, r

What's inside
Steps it walks through
  1. Quick Start
  2. Skill Contract
  3. Handoff Summary
  4. Data Sources
  5. Instructions
  6. Save Results
  7. Reference Materials
  8. Next Best Skill
More from aaron-marketing-skills
All skills →
About this skill
What does the audience-segment-builder skill do?

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. 付费广告受众分群/种子人群/排除人群/相似人群种子

How do I install it?

Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill audience-segment-builder --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going