Analyzing Omnistudio Dependencies

This is the skill you call before touching any OmniStudio component when you need to understand what depends on what. It detects which namespace your org uses (Core, vlocity_cmt, or vlocity_ins), builds a directed dependency graph across OmniScripts, Integration Procedures, FlexCards, and Data Mappers, then spits out Mermaid diagrams and impact analysis. The workflow is smart: it probes for namespaces in order, queries component metadata with the right field names, and parses PropertySetConfig JSON to trace embedded calls. Most useful when someone asks "what breaks if I change this IP?" or when you're documenting a complex OmniStudio implementation and need to see the full web of dependencies.