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.
In this repository39 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- roz-uiSkill
- lsc-account-managementSkill
- lsc-activity-planSkill
- lsc-agentforceSkill
- lsc-app-alertsSkill
- lsc-briefingsSkill
- lsc-calendar-tot-routineSkill
- lsc-config-migrationSkill
- lsc-consent-managementSkill
- lsc-custom-scriptsSkill
- lsc-data-migrationSkill
- lsc-data-modelSkill
- lsc-db-schemaSkill
- lsc-demo-data-loadingSkill
- lsc-events-managementSkill
- lsc-field-emailSkill
- lsc-health-checkSkill
- lsc-home-page-configurationSkill
- lsc-implementation-reviewSkill
- lsc-implementationSkill
- lsc-integration-patternsSkill
- lsc-intelligent-contentSkill
- lsc-key-account-managementSkill
- lsc-lists-filtersSkill
- lsc-mobile-app-settingsSkill
- lsc-mobile-validationSkill
- lsc-next-bestSkill
- lsc-performance-validationSkill
- lsc-product-managementSkill
- lsc-provider-engagement-complianceSkill
- lsc-quick-actions-configurationSkill
- lsc-reporting-analyticsSkill
- lsc-sample-managementSkill
- lsc-surveysSkill
- lsc-troubleshootSkill
- lsc-user-managementSkill
- lsc-visit-managementSkill
- salesforce-querySkill
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
- Distinctive: line 8
Always call MCP tools to get sourced documentation: Do not answer from general knowledge alone.
- Distinctive: line 24
When the user asks about configuring or enabling Territory Alignment features, ask them which mode they prefer:
- Distinctive: line 29
Default to guided setup when connected to an org, or documentation mode if no org is connected.
- Very specific: line 74
DO NOT: use run_soql for Admin Console settings — use list_admin_settings / check_territory_config
- Distinctive: line 78
When the user asks about creating affiliation alignment rules, follow this procedural workflow:
- Very specific: line 79
Verify affiliation role picklist values match between TerrProvAffilAssignRule.AffiliationRole and ProviderAffiliation.Role
- Distinctive: line 80
If mismatched, guide user to Setup > Object Manager > TerrProvAffilAssignRule > Fields > AffiliationRole to add missing values
- Distinctive: line 81
Create rules in Admin Console > Territories > Affiliation Rules
- Very specific: line 83
After creating rules, run the parent alignment jobs (Account/Zip/Brick) — affiliation alignment runs automatically after those complete
- Very specific: line 90
If sharing isn't propagating to territory users, confirm the model's State is Active before investigating rules or LSC4CEAutoShare.
≈ “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.
Files
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 practices | get_lsc_module_docs({ module: "territory-alignment" }) |
| Specific topic (geo rules, affiliation rules, batch jobs, etc.) | search_lsc_knowledge({ query: "<topic>" }) |
| Current org territory configuration | check_territory_config() |
| Admin Console territory settings | list_admin_settings({ category: "Territory" }) |
| Trigger handler status | list_trigger_handlers() |
| Object fields and relationships | describe_sobject({ sobject: "Territory2" }) or describe_sobject({ sobject: "ObjectTerritory2Association" }) |
| Territory data in the org | run_soql({ query: "SELECT ... FROM Territory2 ..." }) |
Configuration Mode
When the user asks about configuring or enabling Territory Alignment features, ask them which mode they prefer:
- Show me the documentation — call
get_lsc_module_docs({ module: "territory-alignment" })and present the relevant sections - 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
| Correct | Wrong (NEVER use) |
ObjectTerritory2Association | AccountTerritory__c, TerritoryAssignment__c |
Territory2 | — |
Territory2Type | — |
Territory2Model | — |
ProviderAcctTerritoryInfo | TerritoryInfo__c, AccountTerritoryInfo__c |
TerrProvAffilAssignRule | AffiliationAlignmentRule__c |
TerrGeoAssignmentRule | ZipTerritory__c, GeoAlignment__c |
ProviderAffiliation | ProviderAffiliation__c |
ContactPointAddress | ContactPointAddress__c |
Tool Restrictions
- DO NOT use
run_soqlfor Admin Console settings — uselist_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:
- Verify affiliation role picklist values match between
TerrProvAffilAssignRule.AffiliationRoleandProviderAffiliation.Role - If mismatched, guide user to Setup > Object Manager > TerrProvAffilAssignRule > Fields > AffiliationRole to add missing values
- Create rules in Admin Console > Territories > Affiliation Rules
- Rules apply to the selected territory and all child territories by default (can be unchecked)
- 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 Territory2ModelIf sharing isn't propagating to territory users, confirm the model's State is Active before investigating rules or LSC4CEAutoShare.
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.

