agentleFS
SalesforceLabsSalesforceLabs/afls-for-claude/skills/lsc-account-management/SKILL.md

lsc-account-management

Skill10 starsChanged 29 days agoApache-2.0View on GitHub

Guides Life Sciences Cloud (LSC) Account Management configuration for web and mobile apps. Use when user asks about provider card, addresses, affiliations, ratings, account search, search before create (SBC), data change requests (DCR), business licenses, multi-object component, ARC graph, ContactPointAddress, HealthcareProvider, ProviderAffiliation, Admin Console account settings, or a web HCO picker that returns no organizations.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    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 an Account Management feature, ask them which mode they prefer:

    line 27
  3. Distinctive:

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

    line 32
  4. Very specific:

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

    line 78
  5. Very specific:

    DO NOT: use run_soql for mobile cache — use check_mobile_cache_status()

    line 79

≈ “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 Account Management Questions

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

User asks about...Call this tool
Account concepts, sub-features, best practicesget_lsc_module_docs({ module: "account-management" })
Specific topic (DCR, affiliations, SBC, etc.)search_lsc_knowledge({ query: "<topic>" })
Web HCO picker returns no organizationssearch_lsc_knowledge({ query: "AccountPickerService HealthcareProvider LIMIT 20 IsPersonAccount" }) then follow HCO picker page below. Query the first 20 primary providers by name before any metadata override.
Current org account configurationcheck_account_config()
Admin Console account settingslist_admin_settings({ category: "AccountManagement" })
Trigger handler statuslist_trigger_handlers()
Object fields and relationshipsdescribe_sobject({ sobject: "Account" }) or describe_sobject({ sobject: "HealthcareProvider" })
Mobile cache statuscheck_mobile_cache_status()
Account data in the orgrun_soql({ query: "SELECT ... FROM Account ..." })
Validation / auditaudit_mobile_config({ group: "account-config-check" })

Configuration Mode

When the user asks about configuring or enabling an Account Management feature, ask them which mode they prefer:

  1. Show me the documentation — call get_lsc_module_docs({ module: "account-management" }) 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_account_config()
list_trigger_handlers()
list_admin_settings({ category: "AccountManagement" })

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: "DCRHandler", active: true })
toggle_trigger_handler({ handlerName: "HardAffiliationHandler", active: true })
toggle_trigger_handler({ handlerName: "AffiliationReciprocalHandler", active: true })
update_admin_setting({ recordId: "...", fields: { ... } })

Step 5: Verify

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


Tool Usage Rules

Correct Object Names

CorrectWrong (NEVER use)
AccountAccount__c
HealthcareProviderHealthcareProvider__c, HealthcareProvider__mdt
ContactPointAddressContactPointAddress__c, AccountAddress__c
BusinessLicenseBusinessLicense__c, AccountLicense__c
ProviderAffiliationProviderAffiliation__c, AccountAffiliation__c
ProviderAcctTerritoryInfo—
ProviderAcctProductInfoProviderAcctProductInfo__c
LifeSciDataChgDefMngFldLifeSciDataChgDefMngFld__c, ManagedField__c
UserAdditionalInfo—

Tool Restrictions

  • DO NOT use run_soql for Admin Console settings — use list_admin_settings / check_account_config
  • DO NOT use run_soql for mobile cache — use check_mobile_cache_status()
  • DO NOT suggest OmniStudio/FlexCard/OmniScript for mobile — NOT available on LSC Mobile iPad app

HCO picker page

Load knowledge/modules/visit-management/support-engineering-visit-hco-picker-page.md. Query HealthcareProvider with IsPrimaryProvider = true, ordered by Account.Name, LIMIT 20. The reply must say AccountPickerService paginates before Account.IsPersonAccount = false, so a page of person accounts is dropped and the web HCO picker returns 0 organizations. Cite that page and an HCO that exists past it. Do not call this a Profile or User LifeSciMetadata override.

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.