Sf Vlocity Build Deploy
Skill Verified ActiveSalesforce Industries DataPack deployment automation using Vlocity Build. TRIGGER when: user deploys or validates OmniStudio/Vlocity DataPacks with vlocity commands (packDeploy/packRetry/packExport/packGetDiffs), sets up DataPack CI/CD pipelines, or troubleshoots DataPack migration errors. DO NOT TRIGGER when: deploying Salesforce metadata with sf project deploy (use sf-deploy), authoring OmniStudio artifacts (use sf-industry-commoncore-*), or writing Apex/LWC business logic (use sf-apex/sf-lwc).
Automate complex Salesforce Industries DataPack deployments and migrations, ensuring predictable workflows and efficient error resolution.
Features
- Vlocity DataPack export, deploy, retry, continue, and diff operations
- Job file configuration for scope definition (projectPath, manifest, queries)
- Pre-deployment validation with `validateLocalData`
- Troubleshooting common DataPack errors and dependency issues
- Guidance for CI/CD pipeline integration
Use Cases
- Deploying OmniStudio/Vlocity DataPacks between Salesforce orgs
- Setting up and managing DataPack CI/CD pipelines
- Troubleshooting DataPack migration or deployment errors
- Validating local DataPack integrity before deployment
Non-Goals
- Deploying standard Salesforce metadata using `sf project deploy`
- Authoring OmniStudio artifacts like FlexCards or Integration Procedures
- Writing Apex or LWC business logic
- Managing Product2 EPC bundles directly (delegates to related skills)
Documentation
- info:Configuration & parameter referenceWhile the SKILL.md outlines critical operating rules and context, specific details on default values or precedence orders for Vlocity CLI parameters are not explicitly documented.
Execution
- info:ValidationThe Vlocity CLI commands are used, but there is no explicit mention of using a schema validation library (like Zod or Pydantic) for input parameters or output parsing within the skill's code.
Installation
npx skills add jaganpro/sf-skillsRuns the Vercel skills CLI (skills.sh) via npx — needs Node.js locally and at least one installed skills-compatible agent (Claude Code, Cursor, Codex, …). Assumes the repo follows the agentskills.io format.
Quality Score
VerifiedSimilar Extensions
ClawSweeper Skill
100Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, commit-review reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions monitoring, permissions, gates, and manual backfills.
Azure Deploy
100Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
Sf Industry Commoncore Integration Procedure
99OmniStudio Integration Procedure creation and validation with 110-point scoring. Use when building server-side process orchestrations that combine Data Mapper actions, Apex Remote Actions, HTTP callouts, and conditional logic. TRIGGER when: user creates Integration Procedures, adds Data Mapper steps, configures Remote Actions, or reviews existing IP configurations. DO NOT TRIGGER when: building OmniScripts (use sf-industry-commoncore-omniscript), creating Data Mappers directly (use sf-industry-commoncore-datamapper), or analyzing cross-component dependencies (use sf-industry-commoncore-omnistudio-analyze).
Sf Industry Commoncore Omnistudio Analyze
98Cross-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, or requests dependency diagrams. DO NOT TRIGGER when: authoring OmniScripts (use sf-industry-commoncore-omniscript), building FlexCards (use sf-industry-commoncore-flexcard), creating Integration Procedures (use sf-industry-commoncore-integration-procedure), or configuring Data Mappers (use sf-industry-commoncore-datamapper).
Sf Industry Commoncore Flexcard
98OmniStudio FlexCard creation and validation with 130-point scoring. Use when building at-a-glance UI cards, configuring data source bindings to Integration Procedures, or reviewing existing FlexCard definitions for accessibility and performance. TRIGGER when: user creates FlexCards, configures data sources, designs card layouts, or asks about OmniUiCard metadata. DO NOT TRIGGER when: building OmniScripts (use sf-industry-commoncore-omniscript), creating Integration Procedures (use sf-industry-commoncore-integration-procedure), or analyzing dependencies (use sf-industry-commoncore-omnistudio-analyze).
Project Session Manager
100Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions