sf-vlocity-build-deploy

Automates OmniStudio DataPack export, validation, deployment, and retry workflows using Vlocity Build.

1|Updated May 7, 2026
One-click install
npx skills add https://github.com/amanpraaj/sf-skill-hub --skill sf-vlocity-build-deploy-amanpraaj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sf-vlocity-build-deploy
Source: https://github.com/amanpraaj/sf-skill-hub/tree/main/skills/salesforce/sf-vlocity-build-deploy
Command: npx skills add https://github.com/amanpraaj/sf-skill-hub --skill sf-vlocity-build-deploy-amanpraaj

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Deploying Salesforce Industries (OmniStudio/Vlocity) DataPacks across orgs is error-prone: missing dependencies, duplicate GlobalKeys, and interrupted jobs cause failed migrations. This Skill provides a deterministic Vlocity Build workflow with validation gates, retry loops, and failure triage so DataPack deployments become predictable and auditable. ## Core Features & Use Cases - Full DataPack Lifecycle: Orchestrates packExport, packDeploy, packRetry, packContinue, packGetDiffs, and validateLocalData commands with correct ordering. - Job File Design: Builds deterministic job files with projectPath, expansionPath, manifest, and queries for scoped, reproducible deployments. - Failure Triage: Maps common errors (missing dependencies, duplicate GlobalKeys, stale settings) to concrete fix directions via a troubleshooting matrix. - Use Case: Deploy an EPC Product2 bundle to a UAT org: validate local data, run packDeploy, retry transient failures, then run packGetDiffs to confirm parity. ## Quick Start Ask the agent to deploy your OmniStudio DataPacks to a target org using Vlocity Build with a manifest-scoped job file, including validation first and retry guidance for any failures.

Frequently Asked Questions about sf-vlocity-build-deploy

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

FAQPage Schema
How do I deploy Vlocity DataPacks to a Salesforce org?▼

Run vlocity packDeploy with a job file and SFDX org alias: vlocity -sfdx.username <target> -job <job>.yaml packDeploy. Validate first with validateLocalData, then use packRetry for remaining failures and packGetDiffs to confirm parity.

How do I fix 'No match found' errors during DataPack deployment?▼

This error means a referenced dependency DataPack is missing from the target org or local expansion path. Identify the missing key from the error message, deploy that dependency first (or add it to the manifest), then rerun packDeploy and packRetry.

What is the difference between packRetry and packContinue in Vlocity Build?▼

packRetry re-attempts DataPacks that failed in the previous run, and should be repeated while error counts decrease. packContinue resumes an interrupted job from where it stopped rather than reprocessing failures.

When should I use Vlocity Build instead of sf project deploy?▼

Use Vlocity Build for OmniStudio/Industries DataPacks such as OmniScripts, FlexCards, Integration Procedures, DataRaptors, and Product2 EPC data. Use sf project deploy for standard Salesforce metadata like Apex classes, LWCs, and custom objects.

Why does DataPack deployment fail with duplicate GlobalKey errors?▼

Duplicate GlobalKey errors occur when the target org contains multiple records sharing the same GlobalKey value. Query the target org to find and remove the duplicates, then rerun the deployment and packRetry.