Omnistudio Omniscript Generate

If you're building guided processes in OmniStudio, this generates OmniScripts with a 120-point validation system that checks everything before deployment. It handles the full workflow from requirements gathering through element selection, dependency mapping, and activation. The skill enforces the correct orchestration order (build Integration Procedures and DataRaptors first, then OmniScripts, then FlexCards), which matters because getting this backwards creates deployment headaches. It covers all the element types (inputs, containers, display blocks) and knows how PropertySetConfig JSON actually works. The scoring thresholds are strict: below 67 blocks deployment, 67-89 needs review, 90+ passes. Useful if you want structured validation instead of trial and error in the OmniStudio UI.

skills.sh installs: 4.9K
GitHub stars: 1.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add forcedotcom/sf-skills --skill omnistudio-omniscript-generate --agent claude-code

Installs into .claude/skills of the current project.

Files

omnistudio-omniscript-generate: OmniStudio OmniScript Creation and Validation

Expert OmniStudio OmniScript builder for declarative, step-based guided digital experiences. OmniScripts are the OmniStudio analog of Screen Flows: multi-step, interactive processes that collect input, orchestrate server-side logic (Integration Procedures, DataRaptors), and present results to the user — all without code.

Quick Reference

Scoring: 120 points across 6 categories. Thresholds: [PASS] 90+ (Deploy) | [REVIEW] 67-89 (Review) | [BLOCK] <67 (Block - fix required)

Scope

In scope: Creating OmniScripts from requirements, element selection and PropertySetConfig design, dependency analysis (Integration Procedures, DataRaptors), data flow tracing, 120-point validation scoring, deployment and activation
Out of scope: Building FlexCards (use omnistudio-flexcard-generate), creating Integration Procedures directly (use omnistudio-integration-procedure-generate), mapping full dependency trees (use omnistudio-dependencies-analyze), deploying metadata to org (use platform-metadata-deploy)