Agent skill · forcedotcom
life-sciences-territory-configure
Use this skill to create and activate a Territory Type, Territory Model, and Territories for Life Sciences Cloud. Trigger when the user says 'set up territories', 'create territory model', 'configure territory hierarchy for Life Sciences', 'territory setup for LSC', or 'create territories for Life Sciences Cloud'. Creates a Geographical territory type, an LSC Territory Model, and a 3-level territory hierarchy (Region, District, Territory). Confirms names with the user, shows a preview, then deploys and activates the model. DO NOT TRIGGER when: user wants to validate prerequisites, assign users to territories, create territory assignment rules, or run the full end-to-end Life Sciences Cloud setup / orchestration (that is the `life-sciences-fieldsalesrep-coordinate` orchestrator's job — this skill runs only as a standalone territory setup).
What it needs
About 6k tokens when loaded.
What this skill does
Life Sciences Territory Setup Creates and activates a Territory Type, Territory Model, and a 3-level Territory hierarchy for Life Sciences Cloud using the sf CLI. Scope In scope: Creating territory type, territory model, and territories; activating the territory model Out of scope: Assigning users to territories, creating territory assignment rules, validating prerequisites Off-topic requests If the user asks for something unrelated to this skill (either at the start or mid-execution), do not attempt it. Tell the user you did not understand the request, then show what you can help with: setting up Life Sciences Cloud territories (this skill), and — if relevant — point them to life-sciences-prerequisites-validate for prerequisite checks or life-sciences-fieldsalesrep-coordinate for the full end-to-end setup. Then stop and wait. --- Required Inputs Gather before proceeding: Target org: The org alias or username to deploy to (from sf config get target-org or user-specified) --- Workflow Phase 1 — Present Default Names and Get Confirmation 1. Show the user the default names that will be used for the territory components. Read references/territory-metadata.md for the exact XML templates and default names. Present the names in a table: 2. Ask the user if they are fine with these names or want to change any of them. Ask for each component individually: "Are you fine with the Territory Type name 'Geographical' or would you like to change it?" "Are you fine with the Territory Model name 'LSC Territory Model' or would you like to change it?" "Are you fine with the Region territory name 'RD - West 20D' or would you like to change it?" "Are you fine with the District territory name 'DM - San Francisco 20D02' or would you like to change it?" "Are you fine with the Territory name 'TM - SPC - San Francisco North 20D02T11' or would you like to change it?" 3. If the user wants to change a name, ask them for the new name they'd like to use. Record the updated name. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/life-sciences-territory-configure