Inputs
Provide these when prompted. The skill asks for anything missing before it runs.
Required
- Records with location or account data
- Territory rules
Optional
- Named-account ownership map
- Tie-break rules
- Region definitions
Agent Skill
Territory Segmentation
Divide records into geographic or account-ownership territories with allocation notes.
Version 1.0 Updated June 2026 SKILL.md MIT 6 min read
Overview
What this skill does
Splitting accounts into fair territories by hand is fiddly and error-prone, especially when locations are messy or rules combine geography with named accounts.
This skill assigns each record to a territory using your geographic or account-ownership rules, explains the basis, flags locations it could not resolve, and notes allocation decisions so the split is auditable.
When to use it
Best used for
- Splitting a list across a sales team
- Applying geographic territory rules consistently
- Handling named-account ownership
- Auditing how accounts were allocated
Know the limits
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
Outputs
One assignment per record with a consistent, inspectable schema.
assigned_territoryThe territory each record belongs to.
geographic_basisThe location signal used.
account_groupingNamed-account ownership applied.
unresolved_locationsRecords that could not be placed.
allocation_notesDecisions and tie-breaks.
Example
Example
A record assigned to a territory.
Input
Rules: West = CA/OR/WA. Named account "Acme" -> rep Dana.
Record: Lumen Robotics, Austin TX.Output
assigned_territory: South (TX)
geographic_basis: HQ state = TX
account_grouping: none (not a named account)
unresolved_locations: none
allocation_notes: Assigned by HQ state per geographic ruleThe Texas HQ maps cleanly to the South territory; named-account rules did not apply, and the basis is recorded for audit.
Setup
How to use the skill
General steps first, then notes for specific clients where verified.
- 1Download the file using the button below, or copy the Markdown.
- 2Place it in a directory named after the skill (e.g. skill-name/).
- 3Make sure the filename stays exactly SKILL.md.
- 4Add any references or assets included with the package.
- 5Load the skill into a compatible agent and provide the required inputs.
Claude Code
- 1Create a folder for the skill and save SKILL.md inside it.
- 2Place the folder where your project's skills are discovered.
- 3Reference the skill when you want it applied to your data.
Other compatible clients
- 1Confirm the client supports the open Agent Skills format.
- 2Load the SKILL.md file as instructed by that client.
- 3If skills are not auto-loaded, paste the Markdown as instructions.
Source
Full SKILL.md source
Read the rendered skill or copy the complete Markdown. The download is generated from this exact source.
Version 1.0 SKILL.md ~2 KB MIT
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.
Before you rely on it
Safety and limitations
- Assignment quality depends on location accuracy.
- It allocates by rules; it does not balance workloads.
- Review the output before acting on it.
- Do not upload confidential datasets to an external model without authorization.
- Outputs depend on the model and the source data and are not guaranteed to be accurate.
History
Changelog
- v1.0June 2026
- Initial release.
Questions
Agent Skill FAQ
What location data does it need?
Any consistent geographic signal — country, region, state, or city. With sparse or mixed location data it flags the records it cannot place rather than assigning them blindly.
Can it balance territories evenly?
It assigns by your rules and reports sizes; even-balancing across reps is a separate decision you can make from the counts.
Do I need ProfileSpider to use this skill?
No. The skill works on any compatible data. ProfileSpider is one convenient way to produce that structured input.
Does running this skill send data to ProfileSpider?
No. Downloading or copying the file does not send any data to ProfileSpider. What happens afterward depends on the AI service you load it into.
Are Agent Skills the same as prompts?
No. A skill is a structured, reusable package — task, inputs, rules, process, and output format — so the workflow runs consistently and can be shared, versioned, and edited.