Sf Vlocity Build Deploy

Shreyas built this to automate the gnarly parts of moving OmniStudio and Vlocity DataPacks between orgs using the Vlocity Build CLI. It handles the full workflow: export with packExport, deploy with packDeploy, retry loops when dependencies fail, and diff checks to verify what actually landed. The troubleshooting matrix is legitimately useful because DataPack errors are cryptic, things like duplicate GlobalKeys or missing matching keys that break silently. If you're doing Industries work and need repeatable deployments or CI/CD for FlexCards, OmniScripts, and Integration Procedures, this gives you the runbook. Standard metadata deploys still go through sf-deploy, this is purely for the DataPack toolchain.

skills.sh installs: 814
GitHub stars: 422
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add jaganpro/sf-skills --skill sf-vlocity-build-deploy --agent claude-code

Installs into .claude/skills of the current project.

Files

sf-vlocity-build-deploy: Vlocity Build DataPack Deployment

Use this skill when the user needs Vlocity DataPack deployment orchestration: export/deploy workflow, manifest-driven deploys, failure triage, and CI/CD sequencing for OmniStudio/Industries DataPacks.

When This Skill Owns the Task

Use sf-vlocity-build-deploy when work involves:

vlocity packDeploy, packRetry, packContinue, packExport, packGetDiffs, validateLocalData
DataPack job-file design (projectPath, expansionPath, manifest, queries)
org-to-org DataPack migration and retry loops
troubleshooting DataPack dependency, matching-key, and GlobalKey issues

Delegate elsewhere when the user is:

deploying standard metadata with sf project deploy -> sf-deploy
building OmniScripts, FlexCards, IPs, or Data Mappers -> sf-industry-commoncore-*
designing Product2 EPC bundles -> sf-industry-cme-epc-model
writing Apex/LWC code -> sf-apex, sf-lwc