agentsclimarketplace

Territory segmentation

Skill spiralcrew-ou/profilespider-agent-skills/territory-segmentation

24 free SKILL.md skills for Claude Code & compatible agents: qualify leads, research companies, clean lists.

Install
npx -y skills add spiralcrew-ou/profilespider-agent-skills --skill territory-segmentation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.9 KB, as published. Nobody here has run it

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

  1. Apply named-account ownership before geographic rules.
  2. Use only supplied location/account data.
  3. Flag records that cannot be resolved.
  4. Record the basis and any tie-breaks.
  5. Be consistent across records.

Process

  1. Parse territory and ownership rules.
  2. Apply named-account ownership.
  3. Assign remaining records geographically.
  4. Flag unresolved locations.
  5. 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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.