Sf Industry Commoncore Omnistudio Analyze
Map OmniStudio dependencies and impact before changing OmniScripts, Integration Procedures, FlexCards, or Data Mappers on Salesforce Industries.
Overview
Sf-industry-commoncore-omnistudio-analyze is an agent skill most often used in Build (also Ship, Operate) that models OmniStudio cross-component dependencies and impact for OmniScript, IP, FlexCard, and Data Mapper chang
Install
npx skills add https://github.com/jaganpro/sf-skills --skill sf-industry-commoncore-omnistudio-analyzeWhat is this skill?
- Dependency graph patterns for OmniScript, Integration Procedure, FlexCard, and Data Mapper components
- Impact analysis methodology informed by community OmniStudio MCP analyzers
- Core namespace objects: OmniProcess, OmniUiCard, OmniDataTransform, OmniProcessElement
- Uses IsIntegrationProcedure on OmniProcess to separate OmniScripts from Integration Procedures
- Supports namespace migration context (Vlocity to Core) when tracing references
- Centers on four OmniStudio component families: OmniScript, Integration Procedure, FlexCard, and Data Mapper
- References four Core namespace object types: OmniProcess, OmniUiCard, OmniDataTransform, OmniProcessElement
Adoption & trust: 877 installs on skills.sh; 418 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need to change an OmniStudio component but cannot see which OmniScripts, IPs, FlexCards, or Data Mappers will break downstream.
Who is it for?
Indie consultants or small teams maintaining Salesforce Industries orgs with OmniStudio and agent-driven change lists.
Skip if: Greenfield apps with no Salesforce/OmniStudio footprint or teams only doing unrelated Apex-only backends.
When should I use this skill?
Before modifying, deleting, or migrating OmniStudio components when dependency and impact visibility is required.
What do I get? / Deliverables
You get a structured dependency and impact view so edits, migrations, and deployments target the right related Core namespace objects first.
- Dependency graph or traversal narrative across related OmniStudio assets
- Impact summary for proposed metadata or Definition JSON edits
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Build is the canonical shelf because analysis happens while composing or refactoring OmniStudio configuration that ships as part of the product. Integrations reflects cross-component links among OmniProcess, cards, transforms, and elements—not a single UI screen or generic CRUD feature.
Where it fits
Trace FlexCard child cards and data sources before repointing an Integration Procedure input.
Run an impact pass on OmniDataTransform edits included in a release branch.
Identify upstream OmniScript steps tied to a failing card after a namespace migration.
How it compares
Structured OmniStudio dependency analysis skill—not a generic CRM admin cheat sheet or a hosted MCP server by itself.
Common Questions / FAQ
Who is sf-industry-commoncore-omnistudio-analyze for?
It is for builders on Salesforce Industries who configure OmniStudio and need dependency-aware analysis before modifying scripts, cards, or transforms.
When should I use sf-industry-commoncore-omnistudio-analyze?
Use it in Build when refactoring OmniStudio packages, in Ship before promoting metadata, and in Operate when diagnosing production breakage after a card or IP change.
Is sf-industry-commoncore-omnistudio-analyze safe to install?
It describes analysis methodology; confirm org access policies and review the Security Audits panel on this Prism page before connecting agents to production Salesforce.
SKILL.md
READMESKILL.md - Sf Industry Commoncore Omnistudio Analyze
# Credits & Acknowledgments This skill was built upon the collective knowledge of the Salesforce OmniStudio community. We gratefully acknowledge the following tools, teams, and resources whose work informed and shaped this skill. --- ## Tools & Projects ### sf-explorer/omnistudio-mcp-server **Community OmniStudio dependency analyzer** Key contributions: - Dependency graph construction patterns for OmniStudio components - Cross-component traversal algorithms - Impact analysis methodology for OmniScript, IP, FlexCard, and Data Mapper changes ### @salesforce/omnistudio-mcp (Official) **Salesforce official FlexCard MCP server** Key contributions: - FlexCard Definition JSON schema reference - Data source type definitions and parsing patterns - Child card and action configuration structures --- ## Salesforce Teams ### Salesforce Industries Engineering **OmniStudio platform development team** Key contributions: - Core namespace object model (OmniProcess, OmniUiCard, OmniDataTransform, OmniProcessElement) - PropertySetConfig and Definition JSON schema design - Namespace migration architecture (Vlocity → Core) - `IsIntegrationProcedure` boolean discriminator on `OmniProcess` for distinguishing OmniScripts from Integration Procedures --- ## Official Salesforce Resources ### OmniStudio Documentation - **OmniStudio Developer Guide**: https://developer.salesforce.com/docs/atlas.en-us.omnistudio.meta/omnistudio/ - **Industries Data Model Reference**: https://developer.salesforce.com/docs/atlas.en-us.industries_reference.meta/industries_reference/ - **OmniStudio Standard Objects**: https://developer.salesforce.com/docs/atlas.en-us.object_reference.meta/object_reference/sforce_api_objects_omniprocess.htm ### Trailhead Content - **OmniStudio Trailhead Module**: https://trailhead.salesforce.com/content/learn/modules/omnistudio-components - **Build OmniScripts Trail**: https://trailhead.salesforce.com/content/learn/trails/build-omnistudio-omniscripts - **Build Integration Procedures Trail**: https://trailhead.salesforce.com/content/learn/modules/omnistudio-integration-procedures - **Build FlexCards Trail**: https://trailhead.salesforce.com/content/learn/modules/omnistudio-flexcards --- ## Community Resources ### Salesforce Stack Exchange **[salesforce.stackexchange.com](https://salesforce.stackexchange.com/)** - OmniStudio namespace detection discussions - PropertySetConfig parsing techniques - Cross-component dependency questions and solutions ### Salesforce Ben **[salesforceben.com](https://www.salesforceben.com/)** - OmniStudio architecture overviews - Migration guides for Vlocity to Core namespace --- ## Key Concepts Credited ### Namespace Detection via SOQL Probing The pattern of probing `SELECT COUNT() FROM OmniProcess` (and Vlocity equivalents) to detect the installed namespace is a community-established practice for OmniStudio tooling. ### BFS Dependency Traversal The breadth-first search algorithm for dependency graph construction follows standard graph traversal patterns adapted for OmniStudio's JSON-embedded reference model. ### Mermaid Visualization for Dependencies The use of Mermaid diagrams for OmniStudio dependency visualization follows patterns from the sf-diagram-mermaid skill and the broader documentation-as-code community. --- ## Contributor ### David Ryan (weytani) **Primary Contributor** — [GitHub](https://github.com/weytani) - Namespace mapping research and validation - Dependency extraction algorithm design - Cross-skill orchestration pattern (sf-industry-commoncore-omnistudio-analyze → sf-industry-commoncore-datamapper → sf-industry-commoncore-integration-procedure → sf-industry-commoncore-omniscript → sf-industry-commoncore-flexcard) --- ## Special Thanks To the Salesforce Industries engineering team for the Core namespace migration that unified OmniStudio's object model, and to the OmniStudio community for sharing namespace detection patterns and dependency analysis techniques that made th