omnistudio-omniscript-generate

Creates and validates Salesforce OmniStudio OmniScripts with 120-point scoring across six categories.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/padjei/SF_Build --skill omnistudio-omniscript-generate-padjei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omnistudio-omniscript-generate
Source: https://github.com/padjei/SF_Build/tree/main/.claude/skills/omnistudio-omniscript-generate
Command: npx skills add https://github.com/padjei/SF_Build --skill omnistudio-omniscript-generate-padjei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Building OmniStudio OmniScripts requires deep knowledge of element types, PropertySetConfig JSON, dependency ordering with Integration Procedures and DataRaptors, and version management. This Skill guides the full lifecycle from requirements through deployment, preventing common failures like circular embedding, broken references, and missing error handling. ## Core Features & Use Cases - OmniScript Generation: Builds OmniProcess and OmniProcessElement records from requirements using the correct Type/SubType/Language triplet, element hierarchy (Level/Order), and PropertySetConfig JSON for 30+ element types. - 120-Point Validation Scoring: Scores OmniScripts across Design & Structure, Data Integration, Error Handling, Performance, User Experience, and Security, with deploy/review/block thresholds. - Dependency Orchestration: Enforces the correct build order (DataRaptors and Integration Procedures before OmniScripts, FlexCards after) and checks for duplicate Type/SubType/Language before creation. - Use Case: A developer needs a multi-step service request intake form that prefills account data via a DataRaptor, validates eligibility through an Integration Procedure, and submits to create a Case. The Skill designs the steps, wires the actions, validates the result, and deploys it. ## Quick Start Ask the assistant to create an OmniScript with Type ServiceRequest, SubType NewCase, and Language English that collects contact details and submits a case to the target org.

Frequently Asked Questions about omnistudio-omniscript-generate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create an OmniScript in Salesforce OmniStudio?▼

Gather the Type, SubType, Language, purpose, and data sources first, then build the OmniProcess record with OmniProcessElement children for each Step and element. This Skill generates the records via REST API templates, validates them with a 120-point score, and deploys with activation verification.

What is the difference between an OmniScript and a FlexCard?▼

OmniScripts are multi-step interactive processes that collect input and orchestrate server-side logic, similar to Screen Flows. FlexCards are display-focused components that present data and can launch OmniScripts. Build FlexCards with the omnistudio-flexcard-generate skill instead.

Can OmniScripts call Integration Procedures and DataRaptors?▼

Yes, OmniScripts use Integration Procedure Action and DataRaptor Extract/Load Action elements to call server-side logic. Build those dependencies first, then wire them into the OmniScript using inputMap and outputMap configuration in PropertySetConfig.

Why is my OmniScript not rendering after deployment?▼

The most common causes are an inactive OmniProcess record or a broken element hierarchy. Verify IsActive is true on the OmniProcess and that all Steps are Level 0 with child elements correctly parented via ParentElementId.

What are the limitations of embedding OmniScripts?▼

Embedding more than two levels deep causes maintenance and performance problems, and circular embedding creates infinite rendering loops. Pass data via prefillJSON mapping and prefer Navigate Action linking when processes do not share a data context.