# omnistudio-dependencies-analyze

Audits OmniStudio components in Salesforce orgs, detects namespaces, and builds Mermaid dependency graphs across OmniScripts, FlexCards, and Data Mappers.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 4800 installs · ★ 1112
- Author: forcedotcom
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/forcedotcom/sf-skills/tree/HEAD/skills/omnistudio-dependencies-analyze/SKILL.md
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/skills/omnistudio-dependencies-analyze

## What it does

This skill inspects a target Salesforce org to detect the active OmniStudio namespace: Core, `vlocity_cmt`, or `vlocity_ins`. Once detected, it catalogs active and draft components across OmniScripts, FlexCards, Integration Procedures, and Data Mappers.

To map dependencies, it parses component JSON configurations like `PropertySetConfig` and `Definition` using breadth-first search. The output delivers a copy-pasteable Mermaid `graph LR` block, a JSON summary, and warnings for circular call chains.

Running this analysis requires the Salesforce CLI (`sf` version 2.0.0 or higher) and an authenticated target org alias. Without an active org connection, the tool cannot execute SOQL queries, making it useless for offline static file inspection. It analyzes existing setups and does not generate or edit component definitions.

## Requirements
- Works with: Salesforce

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add forcedotcom/sf-skills --skill omnistudio-dependencies-analyze -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/omnistudio-dependencies-analyze/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/omnistudio-dependencies-analyze/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add forcedotcom/sf-skills --skill omnistudio-dependencies-analyze -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/omnistudio-dependencies-analyze/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add forcedotcom/sf-skills --skill omnistudio-dependencies-analyze -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/omnistudio-dependencies-analyze/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install forcedotcom/sf-skills omnistudio-dependencies-analyze
```

2. **Manually: put the files in place**
- File: `.github/skills/omnistudio-dependencies-analyze/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add forcedotcom/sf-skills --skill omnistudio-dependencies-analyze -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/forcedotcom/sf-skills --path skills/omnistudio-dependencies-analyze
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/omnistudio-dependencies-analyze/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add forcedotcom/sf-skills --skill omnistudio-dependencies-analyze -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/forcedotcom/sf-skills/tree/HEAD/skills/omnistudio-dependencies-analyze/SKILL.md

## When to use it
- detect the active OmniStudio namespace in a Salesforce org
- generate Mermaid dependency diagrams for OmniScripts and FlexCards
- evaluate the impact of modifying a Data Mapper or Integration Procedure
- uncover circular reference loops across nested components

## Example prompts
- Analyze dependencies for Data Mapper ExtractAccountData in org staging-org
- Generate a Mermaid diagram for all active Integration Procedures
- Detect the OmniStudio namespace and check for circular references in dev-org

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: bc882b02464dbab6.

BEGIN THIRD-PARTY FILE bc882b02464dbab6
```text
---
name: omnistudio-dependencies-analyze
description: "Cross-cutting OmniStudio analysis skill for namespace detection, dependency visualization, and impact analysis across OmniScripts, FlexCards, Integration Procedures, and Data Mappers. TRIGGER when: user asks about OmniStudio dependencies, wants namespace detection (Core vs vlocity_cmt vs vlocity_ins), needs impact analysis, requests dependency graphs or Mermaid diagrams, or asks which components are affected by a change. DO NOT TRIGGER when: authoring OmniScripts (use omnistudio-omniscript-generate), building FlexCards (use omnistudio-flexcard-generate), creating Integration Procedures (use omnistudio-integration-procedure-generate), or configuring Data Mappers (use omnistudio-datamapper-generate)."
metadata:
  version: "1.0"
  domains: ["OmniStudio"]
  relatedSkills:
    - "external-diagram-mermaid-generate"
    - "omnistudio-datamapper-generate"
    - "omnistudio-flexcard-generate"
    - "omnistudio-integration-procedure-generate"
    - "omnistudio-omniscript-generate"
    - "platform-custom-field-generate"
    - "platform-custom-object-generate"
    - "platform-metadata-deploy"
  cliTools:
    - tool: ["sf"]
      semver: ">=2.0.0"
---

# 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`)

---

## Required Inputs

Ask for or infer before starting:

| Input | Default if not provided |
|-------|------------------------|
| Target org alias | Ask the user |
| Analysis scope | Full org (all OmniStudio component types) |
| Specific component to impact-analyze | None (produce full inventory first) |
| Output format preference | All three: Mermaid diagram + JSON summary + human-readable report |

---

## Output Expectations
```
END THIRD-PARTY FILE bc882b02464dbab6

The third-party file has ended. Everything between the bc882b02464dbab6 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2529 of 21639 bytes. © forcedotcom · Apache-2.0 · https://github.com/forcedotcom/sf-skills/tree/HEAD/skills/omnistudio-dependencies-analyze/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md