territory-segmentation
Skill9 starsChanged 5 months agoMITView on GitHub
Divides records into geographic or account-ownership territories. Use when the user provides records with location or account data and wants consistent territory assignments with unresolved locations flagged.
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-list-segmentationSkill
- 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
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 49
Use only supplied location/account data.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Territory Segmentation
Purpose
Divide records into geographic or account-ownership territories with allocation notes.
When to use this skill
- Splitting a list across a sales team
- Applying geographic territory rules consistently
- Handling named-account ownership
- Auditing how accounts were allocated
When not to use this skill
- Records have no location or account-owner data
- You need balanced quota modeling (this assigns, not balances quotas)
- Ownership rules are undefined
Required inputs
- Records with location or account data
- Territory rules
Optional inputs
- Named-account ownership map
- Tie-break rules
- Region definitions
Rules
- Apply named-account ownership before geographic rules.
- Use only supplied location/account data.
- Flag records that cannot be resolved.
- Record the basis and any tie-breaks.
- Be consistent across records.
Process
- Parse territory and ownership rules.
- Apply named-account ownership.
- Assign remaining records geographically.
- Flag unresolved locations.
- Record allocation notes.
Output format
Return one assignment per record with the following fields:
- assigned_territory
- geographic_basis
- account_grouping
- unresolved_locations
- allocation_notes
Validation
- Confirm named accounts override geography.
- Confirm unresolved records are flagged, not guessed.
- Confirm the basis is recorded per record.
Limitations
- Assignment quality depends on location accuracy.
- It allocates by rules; it does not balance workloads.
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.