agentleFS
SalesforceLabsSalesforceLabs/afls-for-claude/skills/lsc-territory-alignment/SKILL.md

lsc-territory-alignment

Skill10 starsChanged 29 days agoApache-2.0View on GitHub

Guides Life Sciences Cloud (LSC) Territory Alignment configuration and administration. Use when user asks about territory setup, account-to-territory assignments, zip code alignment, brick code alignment, affiliation alignment rules, territory batch jobs, ObjectTerritory2Association, TerrProvAffilAssignRule, or ProviderAcctTerritoryInfo objects.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always call MCP tools to get sourced documentation: Do not answer from general knowledge alone.

    line 8
  2. Distinctive:

    When the user asks about configuring or enabling Territory Alignment features, ask them which mode they prefer:

    line 24
  3. Distinctive:

    Default to guided setup when connected to an org, or documentation mode if no org is connected.

    line 29
  4. Very specific:

    DO NOT: use run_soql for Admin Console settings — use list_admin_settings / check_territory_config

    line 74
  5. Distinctive:

    When the user asks about creating affiliation alignment rules, follow this procedural workflow:

    line 78
  6. Very specific:

    Verify affiliation role picklist values match between TerrProvAffilAssignRule.AffiliationRole and ProviderAffiliation.Role

    line 79
  7. Distinctive:

    If mismatched, guide user to Setup > Object Manager > TerrProvAffilAssignRule > Fields > AffiliationRole to add missing values

    line 80
  8. Distinctive:

    Create rules in Admin Console > Territories > Affiliation Rules

    line 81
  9. Very specific:

    After creating rules, run the parent alignment jobs (Account/Zip/Brick) — affiliation alignment runs automatically after those complete

    line 83
  10. Very specific:

    If sharing isn't propagating to territory users, confirm the model's State is Active before investigating rules or LSC4CEAutoShare.

    line 90

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

How to Answer Territory Alignment Questions

Always call MCP tools to get sourced documentation. Do not answer from general knowledge alone.

User asks about...Call this tool
Territory concepts, alignment types, best practicesget_lsc_module_docs({ module: "territory-alignment" })
Specific topic (geo rules, affiliation rules, batch jobs, etc.)search_lsc_knowledge({ query: "<topic>" })
Current org territory configurationcheck_territory_config()
Admin Console territory settingslist_admin_settings({ category: "Territory" })
Trigger handler statuslist_trigger_handlers()
Object fields and relationshipsdescribe_sobject({ sobject: "Territory2" }) or describe_sobject({ sobject: "ObjectTerritory2Association" })
Territory data in the orgrun_soql({ query: "SELECT ... FROM Territory2 ..." })

Configuration Mode

When the user asks about configuring or enabling Territory Alignment features, ask them which mode they prefer:

  1. Show me the documentation — call get_lsc_module_docs({ module: "territory-alignment" }) and present the relevant sections
  2. Walk me through it — configure it directly in their org step-by-step (guided setup below)

Default to guided setup when connected to an org, or documentation mode if no org is connected.

Guided Setup Workflow

Step 1: Check Current State

check_territory_config()
list_trigger_handlers()
list_admin_settings({ category: "Territory" })

Step 2: Report Findings

Present a summary table of what's configured vs what's missing/disabled.

Step 3: Propose Changes

For each issue found, propose the fix and wait for user confirmation.

Step 4: Apply Changes (with user confirmation)

toggle_trigger_handler({ handlerName: "TerritoryAlignmentHandler", active: true })
update_admin_setting({ recordId: "...", fields: { ... } })
create_admin_setting({ category: "Territory", developerName: "...", label: "..." })

Step 5: Verify

Re-run check_territory_config() to confirm everything is configured correctly.


Tool Usage Rules

Correct Object Names

CorrectWrong (NEVER use)
ObjectTerritory2AssociationAccountTerritory__c, TerritoryAssignment__c
Territory2—
Territory2Type—
Territory2Model—
ProviderAcctTerritoryInfoTerritoryInfo__c, AccountTerritoryInfo__c
TerrProvAffilAssignRuleAffiliationAlignmentRule__c
TerrGeoAssignmentRuleZipTerritory__c, GeoAlignment__c
ProviderAffiliationProviderAffiliation__c
ContactPointAddressContactPointAddress__c

Tool Restrictions

  • DO NOT use run_soql for Admin Console settings — use list_admin_settings / check_territory_config
  • DO NOT suggest OmniStudio/FlexCard/OmniScript for mobile — NOT available on LSC Mobile iPad app

Affiliation Alignment Rules Setup

When the user asks about creating affiliation alignment rules, follow this procedural workflow:

  1. Verify affiliation role picklist values match between TerrProvAffilAssignRule.AffiliationRole and ProviderAffiliation.Role
  2. If mismatched, guide user to Setup > Object Manager > TerrProvAffilAssignRule > Fields > AffiliationRole to add missing values
  3. Create rules in Admin Console > Territories > Affiliation Rules
  4. Rules apply to the selected territory and all child territories by default (can be unchecked)
  5. After creating rules, run the parent alignment jobs (Account/Zip/Brick) — affiliation alignment runs automatically after those complete

Activate the Territory Model Before Enabling Sharing Handlers

Territory-scoped sharing depends on an active territory model. The sharing-handler setup checks Territory2Model.State == 'Active' and aborts with an explicit error if the model is still in Planning or Inactive. Always activate the model first, then enable the sharing handlers.

SELECT Id, DeveloperName, State FROM Territory2Model

If sharing isn't propagating to territory users, confirm the model's State is Active before investigating rules or LSC4CEAutoShare.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.