Agent skill · forcedotcom
life-sciences-prerequisites-validate
Validate Life Sciences Cloud for Customer Engagement org prerequisites. Use when an admin needs to verify that all required settings, permissions, OWD sharing rules, and feature toggles are correctly configured before deploying Life Sciences Cloud. Checks user profile, permission sets, Life Sciences CE settings, surveys, OWD, inventory, account plans, care plans, Chatter, data protection, multi-currency, state/country picklists, and person accounts. Reports pass/fail for each check with remediation steps. TRIGGER when: user says 'check prerequisites', 'verify org setup for Life Sciences', 'LSC readiness check', 'pre-requisites for Life Sciences Cloud', 'validate org for LSC'. DO NOT TRIGGER when: user wants to automatically enable or configure these settings, or when the user asks for the full end-to-end Life Sciences Cloud setup / orchestration (that is the `life-sciences-fieldsalesrep-coordinate` orchestrator's job — this skill runs only as a standalone prerequisites check).
What it needs
About 5k tokens when loaded.
What this skill does
Life Sciences Cloud Prerequisites Validation Validates that a Salesforce org meets all prerequisites for Life Sciences Cloud for Customer Engagement. Runs checks via the sf CLI against the currently authenticated org and produces a consolidated pass/fail report with remediation steps for any failures. Scope In scope: Validating org settings, user permissions, OWD sharing, and feature toggles required for Life Sciences Cloud CE Out of scope: Automatically enabling or configuring settings that fail validation Off-topic requests If the user asks for something unrelated to this skill (either at the start or mid-execution), do not attempt it. Tell the user you did not understand the request, then show what you can help with: validating Life Sciences Cloud org prerequisites (this skill), and — if relevant — point them to life-sciences-territory-configure for territory setup or life-sciences-fieldsalesrep-coordinate for the full end-to-end setup. Then stop and wait. --- Required Inputs Gather before proceeding: Target org: The org alias or username to validate (from sf config get target-org or user-specified) Confirmation: The logged-in user must be the admin whose profile and permission sets are being validated --- Workflow All checks run sequentially. Collect all results before presenting the final report. Phase 1 — Validate Environment 1. Confirm org connection — run sf org display --target-org <org> to verify the org is accessible. If it fails, stop and ask the user to authenticate. 2. Identify the logged-in user — extract the username from the org display output. Phase 2 — Run All Prerequisite Checks Run each check below. For each, record PASS or FAIL with the remediation steps. The checks use the canonical Check 1 – Check 12 numbering from the reference files and the final report; the managed-package check is an un-numbered hard-stop gate, not one of the 12 scored categories. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/life-sciences-prerequisites-validate