Individual skill
life-sciences-fieldsalesrep-coordinate
Use this skill to run the full end-to-end Life Sciences Cloud setup workflow for field sales rep in sequence. Trigger when the user says 'set up Life Sciences Cloud end to end', 'run the full LSC setup', 'orchestrate Life Sciences Cloud configuration', 'complete LSC setup', 'Life Sciences Cloud full install', 'set up Life Sciences Cloud end to end for field sales rep', 'run the full LSC setup for field sales rep', 'orchestrate Life Sciences Cloud configuration for field sales rep', 'complete LSC setup for field sales rep', or 'Life Sciences Cloud full install for field sales rep'. Executes five stages in order: prerequisites validation, starter config deployment, territory configuration, user provisioning, and sample visit creation — gating each stage on the success of the previous one. DO NOT TRIGGER when: user wants to run only one specific stage (prerequisites, config deploy, territory setup, user provisioning, or visit creation individually).
skills/life-sciences-fieldsalesrep-coordinate/SKILL.md
Source commit a8a18ce1e4ba12e69b4073eab98ce31bfbd8271e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,151
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- operations Derived category
- sales Derived category
- devops Derived category
- testing Derived category
- testing-browser Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 23,055 bytesSKILL.mdcore · 23,055 bytesSKILL.mdcore · 23,055 bytesSKILL.mdcore · 23,055 bytesSKILL.mdcore · 23,055 bytesSKILL.mdcore · 23,055 bytesSKILL.mdcore · 23,055 bytesSKILL.mdcore · 23,055 bytesSKILL.mdcore · 23,055 bytesSKILL.mdcore · 23,055 bytesSKILL.mdcore · 23,055 bytesSKILL.mdcore · 23,055 bytesreferences/orchestration-flow.mddoc · 6,100 bytesreferences/stage-2-starter-config-application-flexipage-mapping.mddoc · 5,946 bytesreferences/stage-2-starter-config-deploy-commands.mddoc · 5,130 bytesreferences/stage-2-starter-config-lifesci-metadata-deploy.mddoc · 4,474 bytesreferences/stage-2-starter-config-overview.mddoc · 23,498 bytesreferences/stage-2-starter-config-profile-layout-assignments.mddoc · 6,869 bytesreferences/stage-2-starter-config-state-tracking.mddoc · 2,577 bytesreferences/stage-2-starter-config-trigger-handlers.mddoc · 9,078 bytesreferences/stage-4-user-provisioning-overview.mddoc · 18,639 bytesreferences/stage-4-user-provisioning-user-provisioning-details.mddoc · 5,921 bytesreferences/stage-5-visit-creation-execution-state-and-recovery.mddoc · 16,112 bytesreferences/stage-5-visit-creation-metadata-cache-generation.mddoc · 7,243 bytesreferences/stage-5-visit-creation-overview.mddoc · 28,567 bytesreferences/stage-5-visit-creation-visit-creation-data.mddoc · 11,342 bytesreferences/state-machine-and-changes.mddoc · 5,521 bytes
Read excerpt
# Life Sciences Cloud End-to-End Orchestrator
Runs the complete Life Sciences Cloud setup workflow as five **stages** in strict sequence, gating each on the success of the previous stage. Each stage delegates to a child skill or a reference workflow, organized internally into **phases** and **steps** (defined under Execution Order below).
## Scope Guard (evaluate FIRST)
Serve **only** requests for the full end-to-end LSC setup. A single stage/phase/step is **never** invokable here — never silently expand a partial ask into the whole flow. Before any work:
- **Unrelated** to LSC setup (at start or mid-run) → do not attempt it. Tell the user you did not understand the request and show what you can help with (full end-to-end LSC setup, or standalone `life-sciences-prerequisites-validate` / `life-sciences-territory-configure`); stop.
- Stage with its **own standalone skill** — prerequisites (Stage 1) or territory config (Stage 3) → redirect to `life-sciences-prerequisites-validate` / `life-sciences-territory-configure`; stop.
- Stage with **no standalone skill** — config deploy (2), user provisioning (4), visit creation (5) → explain these run only as part of the full flow, not on their own; stop. Do **not** launch the full flow unless the user then asks for it.
Continue only for the complete end-to-end setup: orchestrating the full flow (prerequisites → config deploy → territory → user provisioning → visit creation) in order with gates. Each stage's actual work is delegated to child skills / reference files.