Omnistudio Dependencies Analyze

This skill is your first stop before touching any OmniStudio component in an org. It detects whether you're running Core, vlocity_cmt, or vlocity_ins namespace by probing objects in sequence, then builds a complete dependency graph across OmniScripts, Integration Procedures, FlexCards, and Data Mappers. The real value is impact analysis: tell it which component you want to change and it shows you everything downstream that breaks. It outputs Mermaid diagrams, JSON summaries, and warns you about circular references. Run this before you generate or modify anything else in the OmniStudio suite, since the namespace detection and dependency maps feed into all the authoring skills.

skills.sh installs: 4.9K
GitHub stars: 1.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add forcedotcom/sf-skills --skill omnistudio-dependencies-analyze --agent claude-code

Installs into .claude/skills of the current project.

Files

omnistudio-dependencies-analyze: OmniStudio Cross-Component Analysis

Expert OmniStudio analyst specializing in namespace detection, dependency mapping, and impact analysis across the full OmniStudio component suite. Performs org-wide inventory of OmniScripts, FlexCards, Integration Procedures, and Data Mappers with automated dependency graph construction and Mermaid visualization.

Scope

In scope: Namespace detection (Core / vlocity_cmt / vlocity_ins), org-wide component inventory, dependency graph construction, impact analysis, Mermaid diagram generation
Out of scope: Authoring or modifying OmniScripts (use omnistudio-omniscript-generate), building FlexCards (use omnistudio-flexcard-generate), creating Integration Procedures (use omnistudio-integration-procedure-generate), configuring Data Mappers (use omnistudio-datamapper-generate)