omnistudio-dependencies-analyze

Map OmniStudio component dependencies and generate Mermaid diagrams.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sf, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of analyzing and assessing dependencies within OmniStudio components, providing a comprehensive view of namespace detection, dependency mapping, and impact analysis across OmniScripts, FlexCards, Integration Procedures, and Data Mappers.

Core Features & Use Cases

  • Namespace Detection: Automatically identifies the active namespace (Core, vlocity_cmt, vlocity_ins) in the organization.
  • Dependency Mapping: Builds a directed graph of dependencies between OmniStudio components.
  • Impact Analysis: Determines which components are affected by changes in other components.
  • Visualization: Generates Mermaid diagrams for visual representation of dependencies.
  • Inventory: Provides a comprehensive inventory of all OmniStudio components in the organization.
  • Use Case: When a change is made to an OmniScript or FlexCard, use this Skill to quickly identify which other components are affected and what the impact will be.

Quick Start

Analyze the dependencies of the OmniScript 'createOrder' using the skill 'omnistudio-dependencies-analyze'.

Frequently Asked Questions about omnistudio-dependencies-analyze

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

FAQPage Schema
How do I map OmniStudio dependencies and assess the impact of component changes?

OmniStudio dependency mapping identifies and builds a directed graph of dependencies between components, while impact analysis determines which OmniScripts, FlexCards, or Integration Procedures are affected by a specific change.

What is the best way to visualize FlexCard and OmniScript dependencies in Salesforce?

Visualizing FlexCard and OmniScript dependencies is done by generating Mermaid diagrams, which provide a visual representation of the directed dependency graph and component relationships within the OmniStudio suite.

Does OmniStudio dependency analysis support vlocity_cmt and vlocity_ins namespaces?

Yes, namespace detection supports Core, vlocity_cmt, and vlocity_ins, automatically identifying the active namespace in the organization before retrieving component metadata using SoQL and the Salesforce API.

Do I need the Salesforce CLI to retrieve OmniStudio component inventory and metadata?

Yes, the Salesforce CLI (sf) is required to retrieve OmniStudio component metadata, generate the comprehensive component inventory, and execute the SoQL queries needed for dependency mapping.

How do I find which OmniStudio components are affected when modifying an Integration Procedure?

Finding affected OmniStudio components involves running an impact analysis that maps the directed dependency graph, showing exactly which Integration Procedures, Data Mappers, or FlexCards reference the modified component.

Can I generate a full inventory of all OmniStudio components across an organization?

Yes, you can generate a comprehensive inventory of all OmniStudio components in the organization, including OmniScripts, FlexCards, Integration Procedures, and Data Mappers, using SoQL and the Salesforce API.