Sf Industry Commoncore Omniscript
Generate Salesforce Industry Cloud OmniScript OmniProcess JSON for steps, text blocks, and process shells without hand-copying PropertySetConfig boilerplate.
Overview
sf-industry-commoncore-omniscript is an agent skill for the Build phase that emits Salesforce OmniScript OmniProcess JSON templates for steps, text blocks, and process definitions.
Install
npx skills add https://github.com/jaganpro/sf-skills --skill sf-industry-commoncore-omniscriptWhat is this skill?
- JSON templates for OmniProcess Step elements with SequenceNumber, Level, and PropertySetConfig
- Text Block element payloads with HTML content and parent step linkage
- OmniProcess shell pattern with Type, SubType, LWC runtime flags, and auto-save settings
- Placeholder tokens ({{ParentProcessId}}, {{StepName}}) for agent-driven batch assembly
Adoption & trust: 881 installs on skills.sh; 418 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are building Industry Cloud OmniScripts and keep retyping verbose, escaped PropertySetConfig JSON for every step and element.
Who is it for?
Solo consultants or indie admins extending Salesforce Industry guided flows who want agent-assisted OmniScript metadata drafts.
Skip if: Teams without a Salesforce org, builders who only need Lightning Web Components outside OmniStudio, or anyone expecting turnkey activation without org-specific review.
When should I use this skill?
Authoring or extending Salesforce OmniScript OmniProcess elements and need canonical JSON shapes for Step, Text Block, or process roots.
What do I get? / Deliverables
You get consistent, placeholder-driven OmniProcess element JSON ready to paste or deploy into your OmniStudio implementation workflow.
- OmniProcess Step JSON with PropertySetConfig
- Text Block element JSON linked to a parent step
- OmniProcess shell JSON with Type, SubType, and runtime flags
Recommended Skills
Journey fit
OmniScript authoring is integration work done while wiring guided flows on Salesforce Industry implementations. OmniStudio/OmniScript exports are platform integration artifacts, not generic frontend UI code.
How it compares
Template JSON fragments for OmniStudio metadata—not a generic REST API integration skill or an MCP server.
Common Questions / FAQ
Who is sf-industry-commoncore-omniscript for?
Salesforce implementers, solo builders, and small teams shipping Industry Cloud or Vlocity-style OmniScripts who want structured JSON scaffolds from their coding agent.
When should I use sf-industry-commoncore-omniscript?
Use it during Build integrations when authoring new OmniProcess steps, text blocks, or shell records; also when refactoring sequences or standardizing PropertySetConfig across a family of flows.
Is sf-industry-commoncore-omniscript safe to install?
Treat it like any third-party skill: review the Security Audits panel on this Prism page and validate generated JSON in a sandbox before activating processes in production.
SKILL.md
READMESKILL.md - Sf Industry Commoncore Omniscript
{ "OmniProcessId": "{{ParentProcessId}}", "Name": "{{StepName}}", "Type": "Step", "Description": "{{Description}}", "IsActive": true, "Level": 0, "SequenceNumber": {{SequenceNumber}}, "PropertySetConfig": "{\"label\":\"{{StepLabel}}\",\"chartLabel\":\"\",\"errorMessage\":{\"custom\":[],\"default\":null},\"instructionKey\":\"\",\"knowledgeOptions\":{\"dataCategoryCriteria\":\"\",\"keyword\":\"\",\"publishStatus\":\"Online\",\"typeFilter\":\"\"},\"conditionType\":\"Hide if True\",\"show\":null,\"HTMLTemplateId\":\"\",\"remoteClass\":\"\",\"remoteMethod\":\"\",\"remoteOptions\":{},\"remoteTimeout\":30000,\"validationRequired\":\"Submit\"}" } { "OmniProcessId": "{{ParentProcessId}}", "Name": "{{ElementName}}", "Type": "Text Block", "Description": "{{Description}}", "IsActive": true, "Level": 1, "SequenceNumber": {{SequenceNumber}}, "ParentElementId": "{{ParentStepId}}", "PropertySetConfig": "{\"HTMLTemplateId\":\"\",\"dataJSON\":false,\"hide\":false,\"label\":\"{{Label}}\",\"readOnly\":false,\"show\":null,\"textBlock\":\"{{HTMLContent}}\"}" } { "Name": "{{Type}}_{{SubType}}", "Type": "{{Type}}", "SubType": "{{SubType}}", "Language": "English", "VersionNumber": 1, "IsActive": false, "IsIntegrationProcedure": false, "Description": "{{Description}}", "PropertySetConfig": "{\"persistentComponent\":true,\"trackingCustomData\":{},\"enableLWCRuntime\":true,\"autoSaveOnStepNext\":false,\"autoFocus\":false,\"showConfirmation\":true,\"allowCancel\":true,\"cancelRedirectPageName\":\"\",\"cancelRedirectTemplateUrl\":\"\",\"cancelSource\":\"\",\"consoleTabLabel\":\"\",\"elementTypeToHTMLTemplateList\":[],\"knowledgeArticleTypeQueryFieldsMap\":{},\"lpiLayout\":\"\",\"message\":{},\"pubsub\":false,\"rtpSeed\":false,\"seedDataJSON\":{},\"sessionTimeout\":120,\"ssm\":false,\"timeTracking\":false}", "WebComponentKey": "{{Type}}/{{SubType}}/English/1" } # Credits & Acknowledgments This skill was built upon the collective wisdom of the Salesforce OmniStudio community. We gratefully acknowledge the following authors and resources whose ideas, patterns, and best practices have shaped this skill. --- ## Authors & Contributors ### David Ryan (weytani) **Primary Contributor** — [GitHub](https://github.com/weytani) Key contributions: - OmniScript skill design and structure - Element type reference documentation - Scoring framework and validation patterns - Cross-skill integration with OmniStudio pipeline --- ## Official Salesforce Resources ### Salesforce OmniStudio Documentation **[help.salesforce.com](https://help.salesforce.com/s/articleView?id=sf.os_omniscripts.htm)** Key contributions: - OmniScript element type specifications - PropertySetConfig schema and configuration - OmniProcess and OmniProcessElement data model - Deployment and versioning guidance ### Salesforce OmniStudio Developer Guide **[developer.salesforce.com](https://developer.salesforce.com/docs/atlas.en-us.omnistudio.meta/omnistudio/)** Key contributions: - OmniScript architecture and data flow patterns - Integration Procedure and DataRaptor integration patterns - Merge field syntax and data JSON structure - Custom LWC integration with OmniScripts ### Trailhead OmniStudio Modules **[trailhead.salesforce.com](https://trailhead.salesforce.com/en/content/learn/trails/build-guided-experiences-with-omnistudio)** Key contributions: - OmniScript design best practices - Step-by-step guided experience patterns - Element selection guidance - Testing and deployment workflows --- ## Community Resources ### UnofficialSF Team **[UnofficialSF.com](https://unofficialsf.com/)** Key contributions: - OmniStudio community patterns and examples - Advanced element configuration techniques - Performance optimization strategies ### Salesforce Ben **[salesforceben.com](https://www.salesforceben.com/)** Key contributions: - OmniStudio overview and comparison articles - OmniScript vs Screen Flow decision guidance - Industry Cloud Omni