forcedotcom/sf-skills

life-sciences-prerequisites-validate

Validate Life Sciences Cloud for Customer Engagement org prerequisites.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/forcedotcom/sf-skills --skill life-sciences-prerequisites-validate

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

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.
  1. 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. Checks 1–3 (and the managed-package gate) are in references/checks-user-and-package.md; Checks 4–12 are in references/checks-org-settings.md.

STOP-GATE (report completeness). Every check MUST produce a row in the final report — a check that errors (e.g. Multi-Currency returns HTTP 400 INVALID_TYPE, or an object isn't deployed) is a FAIL row, never a skipped/omitted row or a reason to abort the run. The report's row count MUST equal the full scored-check count (12 categories, Check 1 – Check 12). The one intended early exit is the managed-package gate (the un-numbered lsc4ce package check, step 4 below) — that legitimately stops the run with the "BLOCKED" message. In every other case, a query error is the FAIL signal: record it and continue. Do NOT let a single 4xx or unexpected-shape response silently drop a row or halt the sweep — a short report reads as "fewer things to fix" when the truth is "we didn't check."
  1. Check 1 — user profile and permission sets — read references/checks-user-and-package.md section "User Profile and Permission Sets" for the exact queries and validation logic.
  1. Managed-package gate (un-numbered hard stop) — read references/checks-user-and-package.md section "Managed Package Check". If the lsc4ce package is not installed, display the failure message and stop — do not proceed with remaining checks.
  1. Check 2 — Life Sciences CE settings — read references/checks-user-and-package.md section "Life Sciences Customer Engagement Setup" for the exact queries.
  1. Check 3 — Surveys enabled — read references/checks-user-and-package.md section "Surveys".
  1. Check 4 — OWD sharing settings — read references/checks-org-settings.md section "OWD Sharing" for the exact objects and expected values.
  1. Check 5 — Inventory Count — read references/checks-org-settings.md section "Inventory Count".
  1. Check 6 — Sales Account Plans — read references/checks-org-settings.md section "Sales Account Plans".
  1. Check 7 — Care Plans — read references/checks-org-settings.md section "Care Plans".
  1. Check 8 — Chatter Settings — read references/checks-org-settings.md section "Chatter Settings".
  1. Check 9 — Data Protection and Privacy — read references/checks-org-settings.md section "Data Protection and Privacy".
  1. Check 10 — Multiple Currencies — read references/checks-org-settings.md section "Multiple Currencies".
  1. Check 11 — State and Country/Territory Picklists — read references/checks-org-settings.md section "State and Country/Territory Picklists".
  1. Check 12 — Person Accounts — read references/checks-org-settings.md section "Person Accounts".

Phase 3 — Report

  1. Generate consolidated report — present results in a table:
markdown
| # | Prerequisite                              | Status | Remediation (if failed/warning)  |
|---|-------------------------------------------|--------|----------------------------------|
| 1 | System Administrator + Permission Sets    | PASS/FAIL | <steps if failed>            |
| 2 | Life Sciences CE Enabled                  | PASS/FAIL | <steps if failed>            |
| ...                                                                                       |

Status values are PASS, FAIL, or WARNING. Most checks are PASS/FAIL. The OWD Sharing check (Check 4) is WARNING-level: when its values differ from the expected ones, report WARNING (with the recommended value in the remediation column), never FAIL — see references/checks-org-settings.md for the exact rule.

Include a summary line: X of 12 prerequisites passed. Y require action (Z warnings).

If all pass, confirm the org is ready for Life Sciences Cloud deployment.


Rules / Constraints

ConstraintRationale
Run all checks even if early ones failAdmin needs the full picture to remediate in one pass
Use sf CLI with --target-org for every queryEnsures correct org context even with multiple orgs authenticated
Never modify org settingsThis skill validates only — it does not enable or configure anything
Report exact Setup navigation pathsAdmins need to know where to click in Setup UI

Gotchas

IssueResolution
Some settings are not queryable via Metadata APIUse Tooling API or org settings queries where Metadata API lacks coverage
Person Accounts cannot be disabled once enabledOnly check if enabled; no rollback possible
Multiple Currencies cannot be disabled once activatedOnly check if activated; warn that this is irreversible if recommending enablement
State/Country Picklists enabling is irreversibleInclude this warning in remediation steps

Output Expectations

Deliverables:

  • A formatted table showing pass/fail status for all 12 prerequisite categories
  • Remediation steps (Setup navigation paths and actions) for each failed check
  • Summary count of passed vs. failed checks

Reference File Index

FileWhen to read
references/checks-user-and-package.mdDuring Phase 2 (checks 3–6) — exact sf CLI commands, expected values, and remediation for the user profile/permission-set, managed-package, Life Sciences CE feature, and survey checks
references/checks-org-settings.mdDuring Phase 2 (checks 7–15) — exact sf CLI commands, expected values, and remediation for the OWD sharing, inventory, account plans, care plans, chatter, data protection, currencies, picklists, and person-accounts checks

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
forcedotcom
コミュニティ

design-systems-slds-apply

Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons. Use when building any UI that needs SLDS, choosing between Lightning Base Components and SLDS Blueprints, applying styling hooks for theming, using utility classes for layout and spacing, or selecting icons. Triggers include \"build a modal\", \"create a form\", \"data table\", \"SLDS styling\", \"style with hooks\", \"add an icon\".

1時間の導入数
1
GitHub Stars
1172
更新日
11月13日
forcedotcom
コミュニティ

dx-code-analyzer-run

Run Salesforce Code Analyzer to scan code for security, performance, best practice, and code style violations. Supports all engines (PMD, ESLint, CPD, RetireJS, Flow, SFGE, ApexGuru), targets (files, folders, git diff), categories, and severities. Also handles post-scan exploration: filtering results by engine/severity/category/file, and explaining what rules mean. TRIGGER when: user says 'scan my code', 'check security issues', 'run PMD/ESLint', 'find duplicates', 'analyze Flows', 'check vulner

1時間の導入数
1
GitHub Stars
1172
更新日
11月13日
forcedotcom
コミュニティ

experience-lwc-accessibility-jest-run

Use ALWAYS when running Sa11y accessibility Jest tests for an LWC — locally before pushing, producing the command(s), running one file vs a suite, selecting tests by naming convention, saving Sa11y-rendered HTML, or reproducing a Sa11y/A11yBug failure. Covers core (Bazel; bazel test // : ) and standalone npx jest (.accessibility.test.js, @sa11y/jest). REQUIRED for a run-plan.md, a failing a11y test's exit code, or SA11Y/A11yBug/core-Bazel test paths. DO NOT TRIGGER for functional Jest tests, a11

1時間の導入数
1
GitHub Stars
1172
更新日
11月13日
forcedotcom
コミュニティ

experience-lwc-generate

Lightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc//.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use platform-apex-generate), Aura components, or Visualforce.

1時間の導入数
1
GitHub Stars
1172
更新日
11月13日