C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Validate Life Sciences Cloud for Customer Engagement org prerequisites.
Install Life Sciences Prerequisites Validate
$ npx skills add forcedotcom/sf-skills --skill life-sciences-prerequisites-validate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install forcedotcom/sf-skills life-sciences-prerequisites-validate --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/life-sciences-prerequisites-validate .claude/skills/life-sciences-prerequisites-validate && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "life-sciences-prerequisites-validate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/life-sciences-prerequisites-validate into .claude/skills/life-sciences-prerequisites-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "life-sciences-prerequisites-validate", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/forcedotcom/sf-skills/tree/main/skills/life-sciences-prerequisites-validateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add forcedotcom/sf-skills --skill life-sciences-prerequisites-validate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install forcedotcom/sf-skills life-sciences-prerequisites-validate --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/life-sciences-prerequisites-validate .agents/skills/life-sciences-prerequisites-validate && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "life-sciences-prerequisites-validate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/life-sciences-prerequisites-validate into .agents/skills/life-sciences-prerequisites-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "life-sciences-prerequisites-validate", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add forcedotcom/sf-skills --skill life-sciences-prerequisites-validate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install forcedotcom/sf-skills life-sciences-prerequisites-validate --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/life-sciences-prerequisites-validate .cursor/skills/life-sciences-prerequisites-validate && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "life-sciences-prerequisites-validate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/life-sciences-prerequisites-validate into .cursor/skills/life-sciences-prerequisites-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "life-sciences-prerequisites-validate", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/forcedotcom/sf-skills.git --path skills/life-sciences-prerequisites-validate--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add forcedotcom/sf-skills --skill life-sciences-prerequisites-validate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install forcedotcom/sf-skills life-sciences-prerequisites-validate --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/life-sciences-prerequisites-validate .gemini/skills/life-sciences-prerequisites-validate && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "life-sciences-prerequisites-validate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/life-sciences-prerequisites-validate into .gemini/skills/life-sciences-prerequisites-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "life-sciences-prerequisites-validate", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install forcedotcom/sf-skills life-sciences-prerequisites-validateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add forcedotcom/sf-skills --skill life-sciences-prerequisites-validate -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/life-sciences-prerequisites-validate .github/skills/life-sciences-prerequisites-validate && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "life-sciences-prerequisites-validate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/life-sciences-prerequisites-validate into .github/skills/life-sciences-prerequisites-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "life-sciences-prerequisites-validate", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add forcedotcom/sf-skills --skill life-sciences-prerequisites-validate -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install forcedotcom/sf-skills life-sciences-prerequisites-validate --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/life-sciences-prerequisites-validate .opencode/skills/life-sciences-prerequisites-validate && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "life-sciences-prerequisites-validate" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/life-sciences-prerequisites-validate into .opencode/skills/life-sciences-prerequisites-validate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "life-sciences-prerequisites-validate", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
life-sciences-prerequisites-validate- GitHub stars
- 1.1k
- Token cost
- ~2.2k tokens
- SKILL.md length
- 939 words
- Files
- 3 (incl. references)
- Skills in repo
- 248
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Validate Life Sciences Cloud for Customer Engagement org prerequisites.
- Works in 3 steps: Validate Environment → Run All Prerequisite Checks → Report
- An admin needs to verify that all required settings
- SKILL.md covers Scope, Required Inputs, Workflow and Rules / Constraints, plus 3 more sections
- Calls sf
What it does
Life Sciences Prerequisites Validate is an agent skill from forcedotcom/sf-skills. 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…
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/checks-org-settings.md` and `references/checks-user-and-package.md`).
It sits in Legal & Compliance, covering Privacy and GDPR. It works with Salesforce. The repository describes itself as: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.
When your agent uses it
- An admin needs to verify that all required settings
- OWD sharing rules
- Feature toggles are correctly configured before deploying Life Sciences Cloud
- : user says check prerequisites
Example prompts
- “check prerequisites”
- “verify org setup for Life Sciences”
- “LSC readiness check”
- “/life-sciences-prerequisites-validate”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 3c15867. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
sf
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Life Sciences Prerequisites Validate loads about 2.2k tokens when it runs, and up to ~5.7k if it reads all its reference files. Until then it costs about 257 tokens; SKILL.md has 939 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from forcedotcom/sf-skills at commit 3c15867, republished under its Apache-2.0 licence (© forcedotcom). 939 words, ~2,232 tokens.
Download SKILL.mdSave it as
.claude/skills/life-sciences-prerequisites-validate/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- life-sciences-prerequisites-validate
- description
- 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).
- metadata.version
- 1.0
- metadata.minApiVersion
- 65.0
- metadata.domains
- Life Sciences
- metadata.relatedSkills
- life-sciences-fieldsalesrep-coordinate, life-sciences-territory-configure
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-orgor 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
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.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-numberedlsc4cepackage 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."
Check 1 — user profile and permission sets — read
references/checks-user-and-package.mdsection "User Profile and Permission Sets" for the exact queries and validation logic.Managed-package gate (un-numbered hard stop) — read
references/checks-user-and-package.mdsection "Managed Package Check". If thelsc4cepackage is not installed, display the failure message and stop — do not proceed with remaining checks.Check 2 — Life Sciences CE settings — read
references/checks-user-and-package.mdsection "Life Sciences Customer Engagement Setup" for the exact queries.Check 3 — Surveys enabled — read
references/checks-user-and-package.mdsection "Surveys".Check 4 — OWD sharing settings — read
references/checks-org-settings.mdsection "OWD Sharing" for the exact objects and expected values.Check 5 — Inventory Count — read
references/checks-org-settings.mdsection "Inventory Count".Check 6 — Sales Account Plans — read
references/checks-org-settings.mdsection "Sales Account Plans".Check 7 — Care Plans — read
references/checks-org-settings.mdsection "Care Plans".Check 8 — Chatter Settings — read
references/checks-org-settings.mdsection "Chatter Settings".Check 9 — Data Protection and Privacy — read
references/checks-org-settings.mdsection "Data Protection and Privacy".Check 10 — Multiple Currencies — read
references/checks-org-settings.mdsection "Multiple Currencies".Check 11 — State and Country/Territory Picklists — read
references/checks-org-settings.mdsection "State and Country/Territory Picklists".Check 12 — Person Accounts — read
references/checks-org-settings.mdsection "Person Accounts".
Show full SKILL.md (316 more words)Show less
Phase 3 — Report
- Generate consolidated report — present results in a table:
| # | 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
| Constraint | Rationale |
|---|---|
| Run all checks even if early ones fail | Admin needs the full picture to remediate in one pass |
Use sf CLI with --target-org for every query | Ensures correct org context even with multiple orgs authenticated |
| Never modify org settings | This skill validates only — it does not enable or configure anything |
| Report exact Setup navigation paths | Admins need to know where to click in Setup UI |
Gotchas
| Issue | Resolution |
|---|---|
| Some settings are not queryable via Metadata API | Use Tooling API or org settings queries where Metadata API lacks coverage |
| Person Accounts cannot be disabled once enabled | Only check if enabled; no rollback possible |
| Multiple Currencies cannot be disabled once activated | Only check if activated; warn that this is irreversible if recommending enablement |
| State/Country Picklists enabling is irreversible | Include 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
| File | When to read |
|---|---|
references/checks-user-and-package.md | During 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.md | During 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 |
© forcedotcom, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in skills/life-sciences-prerequisites-validate of forcedotcom/sf-skills.
- SKILL.md
- references/checks-org-settings.md
- references/checks-user-and-package.md
Open the folder on GitHubat commit 3c15867
Compare with similar skills
Life Sciences Prerequisites Validate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Life Sciences Prerequisites Validate this skillforcedotcom/sf-skills | 1.1k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| C15tc15t/c15t | 1.9k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Korean Privacy Termskimlawtech/korean-privacy-terms | 586 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 939 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 939 | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
HIPAA Safe Harbor Coverage Audit
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
Korean Privacy Terms
kimlawtech/korean-privacy-terms
처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.
Gdpr Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert GDPR compliance assistant covering all four core workflows: (1) auditing code and systems for GDPR violations, (2) drafting GDPR-compliant documents such as privacy policies, Data Processing…
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
Pii Contract Analyze
gregmos/PII-Shield
Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.
More from forcedotcom/sf-skills
All 248 skills in this repoAgentforce Architecture Analyze
forcedotcom/sf-skills
Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins.
Agentforce D360 Analyze
forcedotcom/sf-skills
Data Cloud 360° view of a single Agentforce session. An agent skill from forcedotcom/sf-skills.
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
Automation Sandbox Post Copy Configure
forcedotcom/sf-skills
Apply a Salesforce sandbox post-copy automation JSON config against a target org.
Design Systems Slds Apply
forcedotcom/sf-skills
Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons.
Experience Lwc Generate
forcedotcom/sf-skills
Lightning Web Components with PICKLES methodology and 165-point scoring.
Related
Works with
Categories
Questions about Life Sciences Prerequisites Validate
What does Life Sciences Prerequisites Validate do?
Validate Life Sciences Cloud for Customer Engagement org prerequisites. Life Sciences Prerequisites Validate is an agent skill from forcedotcom/sf-skills. Validate Life Sciences Cloud for Customer Engagement org prerequisites.
When should I use Life Sciences Prerequisites Validate?
Life Sciences Prerequisites Validate fits situations like: an admin needs to verify that all required settings; OWD sharing rules; feature toggles are correctly configured before deploying Life Sciences Cloud; : user says check prerequisites.
How do I install Life Sciences Prerequisites Validate in Claude Code?
Run `npx skills add forcedotcom/sf-skills --skill life-sciences-prerequisites-validate -a claude-code`. Or copy the skill folder (skills/life-sciences-prerequisites-validate in forcedotcom/sf-skills) into .claude/skills/life-sciences-prerequisites-validate in your project. Claude Code loads it when a task matches its description.
How do I install Life Sciences Prerequisites Validate in Codex?
Run `npx skills add forcedotcom/sf-skills --skill life-sciences-prerequisites-validate -a codex`. Or copy the skill folder (skills/life-sciences-prerequisites-validate in forcedotcom/sf-skills) into .agents/skills/life-sciences-prerequisites-validate in your project. Codex loads it when a task matches its description.
Can I use Life Sciences Prerequisites Validate in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add forcedotcom/sf-skills --skill life-sciences-prerequisites-validate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/life-sciences-prerequisites-validate, .gemini/skills/life-sciences-prerequisites-validate, .github/skills/life-sciences-prerequisites-validate and .opencode/skills/life-sciences-prerequisites-validate in your project.
What does Life Sciences Prerequisites Validate need to run?
Going by SKILL.md and its folder, Life Sciences Prerequisites Validate needs the command-line tools its instructions call (sf).
Does Life Sciences Prerequisites Validate access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Life Sciences Prerequisites Validate safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Life Sciences Prerequisites Validate use?
Life Sciences Prerequisites Validate is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Life Sciences Prerequisites Validate use?
About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.5k tokens, read only when the agent opens those files.
What are the alternatives to Life Sciences Prerequisites Validate?
Skills that share tags, products or a category with Life Sciences Prerequisites Validate: C15t (c15t/c15t, 1.9k stars), HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Korean Privacy Terms (kimlawtech/korean-privacy-terms, 586 stars) and Gdpr Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 939 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Life Sciences Prerequisites Validate?
forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,058 GitHub stars. The repository holds 248 skills in this directory. The repository was last updated on October 3, 2026.
Source: forcedotcom/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.