lead-list-segmentation
Skill9 starsChanged 5 months agoMITView on GitHub
Divides a lead list into useful commercial segments. Use when the user provides a combined lead list and wants segments with criteria, sizes, recommended treatment, and priority.
In this repository23 other files it gives its agents.
- account-prioritizationSkill
- b2b-lead-qualificationSkill
- candidate-qualificationSkill
- company-data-normalizationSkill
- company-researchSkill
- company-research-workflow-plannerSkill
- company-segmentationSkill
- competitor-researchSkill
- directory-research-plannerSkill
- duplicate-record-reviewSkill
- job-title-normalizationSkill
- lead-list-analysisSkill
- lead-research-workflow-plannerSkill
- market-researchSkill
- outreach-brief-generatorSkill
- partner-qualificationSkill
- persona-classificationSkill
- person-researchSkill
- prospect-list-cleanupSkill
- recruiting-sourcing-plannerSkill
- research-gap-analysisSkill
- supplier-qualificationSkill
- territory-segmentationSkill
The file
Files
Lead List Segmentation
Purpose
Divide a lead list into useful commercial segments with criteria, size, and priority.
When to use this skill
- Splitting one list into messaging-ready segments
- Prioritizing where to spend outreach effort
- Tailoring campaigns per segment
- Reporting list composition to stakeholders
When not to use this skill
- The list has no fields to segment on
- You need per-record scoring (use Lead Qualification)
- The list is too small to segment meaningfully
Required inputs
- A lead list
Optional inputs
- Segmentation dimensions (industry, size, region, fit)
- A priority rule
- Target segment count
Rules
- Define explicit, non-overlapping criteria per segment.
- Report accurate segment sizes.
- Base segments on supplied fields only.
- Recommend treatment proportional to value.
- Make priorities consistent and justified.
Process
- Profile the list fields.
- Choose segmentation dimensions.
- Define segment criteria.
- Assign records and count sizes.
- Recommend treatment and priority.
Output format
Return one record per segment with the following fields:
- segment_name
- segment_criteria
- included_records
- segment_size
- recommended_treatment
- priority
Validation
- Confirm segment criteria do not overlap.
- Confirm sizes sum sensibly to the list.
- Confirm priorities follow the value logic.
Limitations
- Segment quality depends on field completeness.
- Static segments need refreshing as the list grows.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

