Skip to content
Agentmart
Submit a tool

lsc-demo-data-loading

Guides loading demo data into Life Sciences Cloud (LSC) orgs.

Skill by SalesforceLabs

IndexedApache-2.0★ 7
Write a review

Chalk Labs

Need help deploying lsc-demo-data-loading?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

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.

We use your email only for this newsletter. Privacy

About

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.

Use cases: testing, data

No 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

Signals

Stars
7
Forks
2
Open issues
0
Last commit (this folder)
Oct 13, 2026 (17 days ago)
Last release
Oct 22, 2026 (8 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from SalesforceLabs

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get lsc-demo-data-loading running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying lsc-demo-data-loading?

CallGet help
Cite this page

lsc-demo-data-loading skill. Agent Mart. https://agentmart.dev/skills/salesforcelabs-lsc-demo-data-loading (last updated 2026-10-24)