create-segment-lists — Claude Code skill: HubSpot segment lists
Builds a library of HubSpot segment lists — customers, partners, competitors, employees, ICP tiers, industries. Feeds targeting, suppression and reporting.
npx skills add TomGranot/hubspot-admin-skills --skill create-segment-lists -a claude-codeWhat create-segment-lists does
The skill starts with an interview. It asks which segments matter for your business and what counts as engagement, then walks through creating active (smart) lists with the Lists API v3. A list like “All Customers” is built on lifecycle stage; ICP tiers are built on the ICP tier property. Static lists, competitors for instance, get filled by hand or from a CSV.
You need a HubSpot service key stored as HUBSPOT_ACCESS_TOKEN in .env, with crm.lists.read and crm.lists.write scopes. Python 3.10+ and uv are required too. Two steps come first: the ICP tier property must exist (run /create-icp-tiers) and lifecycle stages must be cleaned up (run /fix-lifecycle-stages). A token missing those scopes will fail on the first API call.
Before creating anything, the skill looks for overlapping lists and tells you to merge or rename instead of duplicating. Afterwards it checks member counts, flags contacts sitting in mutually exclusive lists, and suggests a naming scheme such as [ICP] - Tier 1. Deleting a list leaves the contacts untouched, but check whether any workflow or email still points at it.
What it helps with
- create core customer, partner and employee lists in HubSpot
- sort contacts into ICP tiers for prioritisation
- keep unsubscribed and non-marketing contacts out of sends
- set up industry and engagement-based lists
- spot duplicates and overlaps among existing lists
Example prompts for the agent
- Create HubSpot segment lists for customers, partners, employees and ICP tiers
- Build an active list for the Manufacturing industry and check the member count
- Check whether any contact lands in both the customer and competitor lists
How to install create-segment-lists
1Skills CLI (Vercel)
npx skills add TomGranot/hubspot-admin-skills --skill create-segment-lists -a claude-code2Manually: put the files in place
~/.claude/skills/create-segment-lists/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/create-segment-lists/
1Skills CLI (Vercel)
npx skills add TomGranot/hubspot-admin-skills --skill create-segment-lists -a codex2Manually: put the files in place
.agents/skills/create-segment-lists/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add TomGranot/hubspot-admin-skills --skill create-segment-lists -a cursor2Manually: put the files in place
.cursor/skills/create-segment-lists/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install TomGranot/hubspot-admin-skills create-segment-lists2Manually: put the files in place
.github/skills/create-segment-lists/SKILL.md1Skills CLI (Vercel)
npx skills add TomGranot/hubspot-admin-skills --skill create-segment-lists -a gemini-cli2Platform CLI
gemini skills install https://github.com/TomGranot/hubspot-admin-skills --path skills/create-segment-listsManually: put the files in place
.devin/skills/create-segment-lists/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add TomGranot/hubspot-admin-skills --skill create-segment-lists -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about create-segment-lists
How do I install create-segment-lists in Claude Code?
Run npx skills add TomGranot/hubspot-admin-skills --skill create-segment-lists -a claude-code. The skill lands in ~/.claude/skills/create-segment-lists/SKILL.md.
What does create-segment-lists do?
It creates active and static HubSpot lists for customers, partners, competitors, employees, ICP tiers, industries and engagement groups. Those lists then feed email sends, ad audiences and workflow enrollment triggers.
What do I need before running it?
A HubSpot key in .env as HUBSPOT_ACCESS_TOKEN with crm.lists.read and crm.lists.write scopes, Python 3.10+ with uv, the ICP tier property already created, and lifecycle stages cleaned up.
Source text
SKILL.md · MIT
---
name: create-segment-lists
description: "Create business segment lists in HubSpot for customers, partners, competitors, employees, ICP tiers, and industries. Enables segment-based targeting, suppression, and analytics."
license: MIT
metadata:
author: tomgranot
version: "1.1"
category: ongoing-maintenance
---
# Create Segment Lists
Build a library of segment lists that enable targeted marketing, accurate reporting, and proper suppression. These lists form the foundation of segment-based operations.
## Prerequisites
- A HubSpot service key (`HUBSPOT_ACCESS_TOKEN` in `.env`; an existing legacy private app token also works) with `crm.lists.read` and `crm.lists.write` scopes
- Python 3.10+ with [`uv`](https://github.com/astral-sh/uv)
- ICP tier property created (run `/create-icp-tiers` first)
- Lifecycle stages cleaned up (run `/fix-lifecycle-stages` first)
## Interview: Gather Requirements
Before executing, collect the following information from the user:
**Q1: What are your key customer segments?**
- Examples: Industry verticals (Manufacturing, Professional Services, Retail, Education, Logistics), company size tiers (Enterprise, Mid-Market, SMB), geographic regions (North America, EMEA, APAC)
- Default: Core business segments (Customers, Partners, Competitors, Internal) plus ICP tiers and engagement-based segments
**Q2: What engagement criteria define "active" for your business?**
- Examples: Email open or click in last 90 days, website visit in last 60 days, form submission in last 30 days, meeting booked in last 90 days
- Default: Any email engagement (open or click) within the last 90 days
## Recommended Segments
### Core Business Segments
| List Name | Type | Criteria |
|-----------|------|----------|
| All Customers | Active | Lifecycle stage = Customer |
| All Partners | Active | Contact type = Partner (or custom property) |
| Competitors | Static | Manually curated from known competitor domains |
| Internal Employees | Active | Email domain matches company domain |
| Suppressed Contacts | Active | Marketing status = non-marketing OR globally unsubscribed |
### ICP-Based Segments
| List Name | Type | Criteria |
|-----------|------|----------|
| ICP Tier 1 | Active | ICP tier property = Tier 1 |
| ICP Tier 2 | Active | ICP tier property = Tier 2 |
| ICP Tier 3 | Active | ICP tier property = Tier 3 |
| Non-ICP | Active | ICP tier property = Non-ICP or unknown |
### Industry Segments
| List Name | Type | Criteria |
|-----------|------|----------|
| [Industry Name] | Active | Industry = [value] |
| (Create one per target industry) | | |
### Engagement Segments
| List Name | Type | Criteria |
|-----------|------|----------|
| Highly Engaged (90 days) | Active | Email open or click in last 90 days |
| Disengaged (6+ months) | Active | No email engagement in 180+ days |
| Never Engaged | Active | No email opens ever AND created 30+ days ago |
## Step-by-Step Instructions
### Stage 1: Plan
1. Run the requirements interview above and decide which segments are relevant to the business.
2. Check for existing lists that overlap — merge or rename rather than creating duplicates.
### Stage 2: Before
1. Confirm the properties these lists depend on are populated (ICP tier, lifecycle stage, industry).
2. Inventory existing lists (`POST /crm/v3/lists/search`) and record the baseline count.
### Stage 3: Execute — Create Lists
Use the Lists API (v3) to create active (smart) lists:
```python
import os, requests
from dotenv import load_dotenv
load_dotenv()
TOKEN = os.environ["HUBSPOT_ACCESS_TOKEN"]
BASE = "https://api.hubapi.com"
HEADERS = {"Authorization": f"Bearer {TOKEN}", "Content-Type": "application/json"}
# Example: Create "All Customers" list
resp = requests.post(f"{BASE}/crm/v3/lists", headers=HEADERS, json={
"name": "All Customers",
"objectTypeId": "0-1", # contacts
"processingType": "DYNAMIC",
"filterBranch": {
"filterBranchType": "OR",
"filterBranches": [{
"filterBranchType": "AND",
"filterBranches": [],
"filters": [{
"filterType": "PROPERTY",
"property": "lifecyclestage",
"operation": {
"operationType": "ENUMERATION",
"operator": "IS_ANY_OF",
"values": ["customer"],
},
}],
}],
"filters": [],
},
})
resp.raise_for_status()
```
Create each list, verify member count, and document the list ID.
For static lists (Competitors), create the list and manually add contacts or import from a CSV.
### Stage 4: After
1. Check member counts for each list — do they match expectations?
2. Verify no contacts appear in mutually exclusive lists (e.g., both Customer and Competitor).
3. Confirm lists are visible to the appropriate teams.
## Rollback
- Lists can be deleted via the API or UI.
- Deleting a list does not affect the contacts in it — only the list definition is removed.
- Check if any workflows or emails reference the list before deleting.
## Tips
- Use a consistent naming convention: `[Category] - Segment Name` (e.g., `[ICP] - Tier 1`, `[Industry] - Manufacturing`).
- Review segment membership quarterly — segments should grow or shrink in expected ways.
- Use these lists as building blocks for email sends, ad audiences, and workflow enrollment triggers.
© tomgranot · MIT · TomGranot/hubspot-admin-skills