lsc-mobile-validation
Skill10 starsChanged 29 days agoApache-2.0View on GitHub
Validates Life Sciences Cloud (LSC) Mobile app configuration to prevent issues. Use when user is preparing for mobile deployment, troubleshooting mobile sync issues, or asking about DB Schema / mobile cache configuration.
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-home-page-configurationSkill
- lsc-implementation-reviewSkill
- lsc-implementationSkill
- lsc-integration-patternsSkill
- lsc-intelligent-contentSkill
- lsc-key-account-managementSkill
- lsc-lists-filtersSkill
- lsc-mobile-app-settingsSkill
- 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
6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Very specific: line 15
IMPORTANT: When validating mobile configuration, use the audit_mobile_config tool to run automated checks.
- Distinctive: line 28
If validation reveals missing features or misconfiguration:
- Very specific: line 36
If the user reports a specific error message, use diagnose_lsc_issue.
- Distinctive: line 111
When validating mobile configuration:
- Distinctive: line 151
Fix: Ensure Status is Active/Published and IntegrationStatus is Ok
- Distinctive: line 169
Fix: Ensure required schemas are assigned to the profile
≈ “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
For mobile validation rules and guidance, call search_lsc_knowledge({ query: "mobile validation configuration" }) to get sourced documentation.
LSC Mobile Configuration Validator
You help validate LSC mobile app configuration to prevent sync and functionality issues.
Automated Validation
IMPORTANT: When validating mobile configuration, use the audit_mobile_config tool to run automated checks. This tool validates against known common issues and provides specific resolution steps.
Quick Validation Groups
| Scenario | Command |
| User can't log in | audit_mobile_config({ group: 'mobile-login-check' }) |
| Before go-live | audit_mobile_config({ group: 'pre-deployment' }) |
| Sync not working | audit_mobile_config({ group: 'sync-troubleshooting' }) |
| Full health check | audit_mobile_config({ group: 'full-mobile-audit' }) |
Check Trigger Handlers & Admin Console Settings
If validation reveals missing features or misconfiguration:
list_trigger_handlers()— Check if required trigger handlers are enabledtoggle_trigger_handler({ handlerName: "...", active: true })— Enable/disable a handlerlist_admin_settings({ category: "..." })— View Admin Console settings for a categoryupdate_admin_setting({ recordId: "...", fields: { IsActive: true } })— Update a setting
Diagnosing Specific Errors
If the user reports a specific error message, use diagnose_lsc_issue. It finds matching known causes and validation rules and checks the org for them:
diagnose_lsc_issue({ symptom: 'Device sync transaction record was not found' })Mobile Cache Status
USE THE check_mobile_cache_status TOOL to check cache status. Do NOT write SOQL queries manually.
check_mobile_cache_status()Objects that DO NOT EXIST (never query these):
MobileMetadataCache__c,MobileApplicationDetail,lsc4ce__MobileMetadataCache__c- NONE OF THESE EXIST
The correct object is LifeSciMobileMetadataRecord but the tool handles this for you.
Key Fields (for reference)
| Field | Description |
Name | Name of the DB Schema record |
ProfileId | Profile this schema is assigned to |
Status | Active, Inactive, New, Published, Processing, etc. |
IntegrationStatus | Error, New, Ok, Pending |
IntegrationErrorCode | Error code if sync failed |
IntegrationErrorMessage | Error details if sync failed |
Admin Console Location
Admin Console > Mobile > Object Metadata Cache Configuration
This is where admins create and manage DB Schema records through the UI.
Tip: For managing individual DbSchema records (create, update, delete, SOQL filters), see the
lsc-db-schemaskill.
Required DB Schema Records by Feature
Each LSC feature requires specific DB Schema records to be active for mobile:
Field Email
- Email template records
- Email fragment records
- Consent/subscription records
Next Best Action (NBA)
- NBA configuration records
- Action records
Next Best Customer (NBC)
- NBC settings records
- Provider/Account related records
Lists & Filters
- Actionable list records
App Alerts/Notifications
- Alert configuration records
Visit Management
- Visit records
- Product discussion records
- Sample records (if sampling enabled)
Sample Management
- Sample limit records
- Sample inventory records
- Sample transaction records
Validation Workflow
When validating mobile configuration:
- Check setup status:
Use check_lsc_setup to verify org connection - Query all mobile metadata records:
SELECT Id, Name, Status, IntegrationStatus, IntegrationErrorCode, IntegrationErrorMessage FROM LifeSciMobileMetadataRecord ORDER BY Name - Identify issues:
- Records with
IntegrationStatus = 'Error' - Records with
Status != 'Active'andStatus != 'Published' - Missing records for enabled features
- Records with
- Check profile assignments:
SELECT Id, Name, Profile.Name, Status FROM LifeSciMobileMetadataRecord WHERE ProfileId != null - Report findings:
- List all configured schemas
- Flag any errors or inactive records
- Identify potentially missing schemas based on enabled features
Common Mobile Issues
Data Not Appearing on Mobile
Query to run:
SELECT Id, Name, Status, IntegrationStatus
FROM LifeSciMobileMetadataRecord
WHERE Name LIKE '%<feature>%'Fix: Ensure Status is Active/Published and IntegrationStatus is Ok
Mobile Sync Failures
Query to run:
SELECT Id, Name, IntegrationErrorCode, IntegrationErrorMessage
FROM LifeSciMobileMetadataRecord
WHERE IntegrationStatus = 'Error'Fix: Review error messages and correct configuration
Feature Not Working for Specific Profile
Query to run:
SELECT Id, Name, Profile.Name, Status
FROM LifeSciMobileMetadataRecord
WHERE Profile.Name = '<profile_name>'Fix: Ensure required schemas are assigned to the profile
Mobile Sync Objects
For deeper sync troubleshooting, also query:
| Object | Purpose |
DeviceSyncSummary | Summary of synced data per device |
DeviceSyncTransaction | Individual sync transactions |
DeviceSyncTransactionLog | Sync logs with details |
DeviceSyncTransactionRecord | Individual synced records |
Example - Recent sync errors:
SELECT Id, Name, Status, ErrorDescription
FROM BatchJob
WHERE Status = 'Failed' OR Status = 'CompletedWithFailures'
ORDER BY StartTime DESC
LIMIT 10Does 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.

