lsc-home-page-configuration
Skill10 starsChanged 29 days agoApache-2.0View on GitHub
Guides Life Sciences Cloud (LSC) Home Page configuration for web and mobile apps. Use when user asks about home page setup, widgets, announcements, quick actions, Lightning App Builder configuration for LSC, Agentforce Welcome Center utterances/prompts, or configuring recommended utterances on the mobile home page.
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-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-territory-alignmentSkill
- lsc-troubleshootSkill
- lsc-user-managementSkill
- lsc-visit-managementSkill
- salesforce-querySkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 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.
3
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 Home Page 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 61
DO NOT: use run_soql for Admin Console settings — use list_admin_settings
- Very specific: line 62
DO NOT: use run_soql for mobile cache — use check_mobile_cache_status()
- Distinctive: line 67
When the user asks about updating Agentforce Welcome Center utterances programmatically, follow this workflow:
- Very specific: line 80
Read /tmp/flexipage-retrieve/force-app/main/default/flexipages/<PageDeveloperName>.flexipage-meta.xml.
- Distinctive: line 83
Use the Edit tool to modify utterance values in the XML file.
- Distinctive: line 93
IMPORTANT: Always retrieve first to get the current state.
≈ “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 Home Page Questions
Always call MCP tools to get sourced documentation. Do not answer from general knowledge alone.
| User asks about... | Call this tool |
| Home page concepts, components, best practices | get_lsc_module_docs({ module: "home-page" }) |
| Specific topic (announcements, NBC widget, etc.) | search_lsc_knowledge({ query: "<topic>" }) |
| Validate home page configuration | audit_mobile_config({ group: "home-page-check" }) |
| Admin Console home page settings | list_admin_settings({ category: "HomePage" }) |
| Trigger handler status | list_trigger_handlers() |
| Mobile cache status | check_mobile_cache_status() |
| Home page FlexiPages | run_soql({ query: "SELECT Id, MasterLabel, PageType FROM FlexiPage WHERE PageType = 'HomePage'" }) |
Configuration Mode
When the user asks about configuring Home Page features, ask them which mode they prefer:
- Show me the documentation — call
get_lsc_module_docs({ module: "home-page" })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
audit_mobile_config({ group: "home-page-check" })
list_trigger_handlers()
list_admin_settings({ category: "HomePage" })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: "...", active: true })
update_admin_setting({ recordId: "...", fields: { ... } })
create_admin_setting({ category: "HomePage", developerName: "...", label: "..." })Step 5: Verify
Re-run audit_mobile_config({ group: "home-page-check" }) to confirm everything is configured correctly.
Tool Usage Rules
Tool Restrictions
- DO NOT use
run_soqlfor Admin Console settings — uselist_admin_settings - DO NOT use
run_soqlfor mobile cache — usecheck_mobile_cache_status() - DO NOT suggest OmniStudio/FlexCard/OmniScript for mobile — NOT available on LSC Mobile iPad app
Programmatic Utterance Management (Agentforce Welcome Center)
When the user asks about updating Agentforce Welcome Center utterances programmatically, follow this workflow:
Step 1: Find the home page name
run_soql({ query: "SELECT Id, DeveloperName, MasterLabel FROM FlexiPage WHERE PageType = 'HomePage' ORDER BY LastModifiedDate DESC" })Step 2: Retrieve the FlexiPage metadata
sf project retrieve start --metadata FlexiPage:<PageDeveloperName> --output-dir /tmp/flexipage-retrieve --target-org <orgAlias>Step 3: Read the retrieved XML
Read /tmp/flexipage-retrieve/force-app/main/default/flexipages/<PageDeveloperName>.flexipage-meta.xml. Look for the Agentforce Welcome Center <componentInstances> block. Utterances are stored as utterance1 through utterance5 properties.
Step 4: Edit the utterances
Use the Edit tool to modify utterance values in the XML file.
Step 5: Deploy the updated FlexiPage
sf project deploy start --source-dir /tmp/flexipage-retrieve --target-org <orgAlias>Step 6: Confirm
Tell the user the utterances have been updated and they should see changes on mobile after refreshing.
IMPORTANT: Always retrieve first to get the current state. Never construct FlexiPage XML from scratch.
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.

