lsc-demo-data-loading
Guides loading demo data into Life Sciences Cloud (LSC) orgs.
Skill by SalesforceLabs
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/salesforcelabs-lsc-demo-data-loading
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: testing, data
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/lsc-demo-data-loading
What's inside
- Skill name
lsc-demo-data-loading- Description
- Guides loading demo data into Life Sciences Cloud (LSC) orgs. Covers territory hierarchies, accounts (HCO/HCP), healthcare providers, contact points, business licenses, territory assignments, PATI/PATS records, and therapy-area scenarios. Use when user asks about creating demo data, sample data, test data, or setting up an LSC demo org.
- License
- Apache-2.0
- Instructions
- 533 lines in SKILL.md · view on GitHub
Agent Skills spec issues
- body: 533 lines (spec recommends under 500)
Files (1)
- SKILL.md
SKILL.md (first lines)
## How to Answer Demo Data Loading Questions
**Always call MCP tools first to check org state before creating data.**
| User asks about... | Call this tool |
|---------------------|---------------|
| Territory setup status | `run_soql({ query: "SELECT Id, Name, State FROM Territory2Model LIMIT 5" })` |
| Existing accounts | `run_soql({ query: "SELECT COUNT(), IsPersonAccount FROM Account GROUP BY IsPersonAccount" })` |
| Existing HCPs | `run_soql({ query: "SELECT COUNT() FROM HealthcareProvider" })` |
| Object fields | `describe_sobject({ sobject: "Account" })` or any target object |
| Territory assignments | `run_soql({ query: "SELECT COUNT() FROM ObjectTerritory2Association" })` |
| Therapy-area scenarios, demo concepts, related guidance | `search_lsc_knowledge({ query: "..." })` (returns cited source content) |
---
## Data Loading Order
Data must be created in this order due to dependencies:
1. **Territory Hierarchy** (Territory2Model > Territory2Type > Territory2)
2. **Accounts** (HCO org accounts, then HCP PersonAccounts)
3. **Healthcare Providers** (HealthcareProvider linked to PersonAccounts)
4. **Provider Details** (NPI, Specialty, CareSpecialty, Affiliations)
5. **Territory Assignments** (ObjectTerritory2Association, ProviderAcctTerritoryInfo)
6. **Provider Account Territory Summaries** (PrvdAccountTerritorySummary)
7. **Contact Points** (Address, Email, Phone, Social)
8. **Business Licenses**
9. **Scenario Data** (therapy-area-specific layering)
---
## Territory Hierarchy
### Required Objects
| Object | Purpose |
|--------|---------|
| `Territory2Model` | Container for the entire hierarchy (one active model) |
| `Territory2Type` | Types of territories (Geographical, Medical, KAM) |
| `Territory2` | Individual territory nodes |
### Structure Pattern
```
GLOBAL (root)
├── US
│ ├── US_NE_Boston
│ ├── US_NE_Washington_DC
│ ├── US_MW_Chicago
│ └── US_W_San_Francisco
├── GB
│ ├── GB_London
│ ├── GB_Manchester
│ └── GB_Edinburgh
├── FR / DE / IT / ES / JP / KR / BR / MX / AR
│ └── (country sub-territories by city)
├── Medical
│ ├── MED_Oncology
│ ├── MED_Cardiology
│ ├── MED_Neurology
│ ├── MED_Immunology
│ └── MED_Primary_Care
└── KAM
├── KAM_Academic_Medical_Centers
├── KAM_Hospital_Systems
└── KAM_Payer_Insurance
```
### Key Gotchas
- **Territory2Model must be in Active state** for assignments to work. Use `State = 'Active'` or activate via Setup.
- **Territory names are DeveloperName-like** (underscores, no spaces) — use this for lookups, not `Name`.
- **ParentTerritory2Id** links child to parent — query by `DeveloperName` to find the parent.
---
## Account Creation
### Record Types
| Record Type DeveloperName | Use For |
|---------------------------|---------|
| `Health_Care_Organization` | Hospitals, clinics, payers, pharmacies |
| `Health_Care_Provider` | Doctors (PersonAccount) |
### HCO (Organization) Accounts
```apex
Account a = new Account();
a.RecordTypeId = hcoRtId;
a.Name = 'Massachusetts General Hospital';
a.Type = 'Hospital';
a.BillingStreet = '55 Fruit Street';
a.BillingCity = 'Boston';
a.BillingStateCode = 'MA';
a.BillingPostalCode = '02114';
a.BillingCountryCode = 'US';
a.Site = 'DEMO-TAG'; // tag for cleanup
```
### HCP (PersonAccount) Doctors
```apex
Account a = new Account();
a.RecordTypeId = hcpRtId;
a.Salutation = 'Dr.';
a.FirstName = 'Sarah';
a.LastName = 'Chen';
a.PersonEmail = 'sarah.chen@hospital.example.com';
a.Phone = '+1 617 726 2000';
a.BillingStreet = '55 Fruit Street';
a.BillingCity = 'Boston';
a.BillingStateCode = 'MA';
a.BillingPostalCode = '02114';
a.BillingCountryCode = 'US';
// CRITICAL: Also set PersonMailing fields for mobile app display
a.PersonMailingStreet = a.BillingStreet;
a.PersonMailingCity = a.BillingCity;
a.PersonMailingStateCode = a.BillingStateCode;From SalesforceLabs/lsc-for-claude, Apache-2.0.
More from SalesforceLabs/lsc-for-claude
- 0.624score
lsc-account-management
SalesforceLabs
Guides Life Sciences Cloud (LSC) Account Management configuration for web and mobile apps.
SkillAFreshness: A★ 7Claude Code +9 - 0.624score
lsc-activity-plan
SalesforceLabs
Guides Life Sciences Cloud (LSC) Activity Plan configuration for web and mobile apps.
SkillAFreshness: A★ 7Claude Code +9 - 0.624score
lsc-agentforce
SalesforceLabs
Guides Agentforce for Life Sciences Cloud (LSC) configuration (Winter '26 feature).
SkillAFreshness: A★ 7Claude Code +9 - 0.624score
lsc-app-alerts
SalesforceLabs
Guides Life Sciences Cloud (LSC) App Alerts and Notifications configuration for web and mobile apps.
SkillAFreshness: A★ 7Claude Code +9 - 0.624score
lsc-briefings
SalesforceLabs
Guides Briefings (Daily Podcasts) configuration and troubleshooting.
SkillAFreshness: A★ 7Claude Code +9 - 0.624score
lsc-calendar-tot-routine
SalesforceLabs
Guides Life Sciences Cloud (LSC) Calendar, Time Off Territory, Routine, and My Team configuration.
SkillAFreshness: A★ 7Claude Code +9 - 0.624score
lsc-config-migration
SalesforceLabs
Guides migrating Life Sciences Cloud (LSC) org configuration (Admin Console settings, DB Schema, trigger handlers, quick/custom actions) between orgs using…
SkillAFreshness: A★ 7Claude Code +9 - 0.624score
lsc-consent-management
SalesforceLabs
Guides Life Sciences Cloud (LSC) Consent Management configuration for web and mobile apps.
SkillAFreshness: A★ 7Claude Code +9 - 0.624score
lsc-custom-scripts
SalesforceLabs
Guides Life Sciences Cloud (LSC) Custom Script configuration for validation, checklists, and Visit Action Validation.
SkillAFreshness: A★ 7Claude Code +9 - 0.624score
lsc-data-model
SalesforceLabs
Expert knowledge of the Life Sciences Cloud (LSC) data model concepts.
SkillAFreshness: A★ 7Claude Code +9 - 0.624score
lsc-db-schema
SalesforceLabs
Manages Life Sciences Cloud (LSC) DB Schema records (mobile object metadata cache configuration).
SkillAFreshness: A★ 7Claude Code +9 - 0.624score
lsc-events-management
SalesforceLabs
Guides Life Sciences Cloud (LSC) Events Management configuration for web and mobile apps.
SkillAFreshness: A★ 7Claude Code +9
Signals
- Stars
- 7
- Forks
- 2
- Open issues
- 0
- Last commit (this folder)
- Oct 13, 2026 (15 days ago)
- Last release
- Oct 22, 2026 (6 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- Apache-2.0
- Repository
- github.com/SalesforceLabs/lsc-for-claude
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from SalesforceLabs
- 0.624score
lsc-activity-plan
SalesforceLabs
Guides Life Sciences Cloud (LSC) Activity Plan configuration for web and mobile apps.
SkillAFreshness: A★ 7Claude Code +9 - 0.624score
lsc-agentforce
SalesforceLabs
Guides Agentforce for Life Sciences Cloud (LSC) configuration (Winter '26 feature).
SkillAFreshness: A★ 7Claude Code +9 - 0.624score
lsc-app-alerts
SalesforceLabs
Guides Life Sciences Cloud (LSC) App Alerts and Notifications configuration for web and mobile apps.
SkillAFreshness: A★ 7Claude Code +9 - 0.624score
lsc-briefings
SalesforceLabs
Guides Briefings (Daily Podcasts) configuration and troubleshooting.
SkillAFreshness: A★ 7Claude Code +9 - 0.624score
lsc-calendar-tot-routine
SalesforceLabs
Guides Life Sciences Cloud (LSC) Calendar, Time Off Territory, Routine, and My Team configuration.
SkillAFreshness: A★ 7Claude Code +9 - 0.624score
lsc-config-migration
SalesforceLabs
Guides migrating Life Sciences Cloud (LSC) org configuration (Admin Console settings, DB Schema, trigger handlers, quick/custom actions) between orgs using…
SkillAFreshness: A★ 7Claude Code +9
Cite this page
lsc-demo-data-loading skill. Agent Mart. https://agentmart.dev/skills/salesforcelabs-lsc-demo-data-loading (last updated 2026-10-24)