What problem does it solve? OmniStudio components store their dependencies inside JSON configuration fields rather than lookup relationships, making it nearly impossible to know which OmniScripts, Integration Procedures, FlexCards, or Data Mappers will break when a component changes. This Skill automates namespace detection, org-wide component inventory, dependency graph construction, and impact analysis so teams can safely plan changes and migrations. ## Core Features & Use Cases - Namespace Detection: Probes the org via SOQL to determine whether it uses Core, vlocity_cmt, or vlocity_ins namespace, including mixed-namespace migration states. - Dependency Graph Construction: Parses PropertySetConfig, DataSourceConfig, and Data Mapper items using BFS traversal with circular reference detection to map cross-component dependencies. - Impact Analysis & Visualization: Computes transitive dependents for any component and outputs Mermaid diagrams, JSON summaries, and human-readable reports. - Use Case: Before modifying a shared Data Mapper, run this Skill to discover that three Integration Procedures, two OmniScripts, and one FlexCard transitively depend on it, then generate a Mermaid diagram for the change review. ## Quick Start Ask the agent to analyze OmniStudio dependencies in your org, for example: detect the OmniStudio namespace in my org and generate a dependency diagram with impact analysis for the AccountExtract Data Mapper.
