Agent skill

Omnistudio Datapacks Deploy

Salesforce Industries DataPack deployment automation using Vlocity Build.

Apache-2.0Auto-check passedDevOps & Cloud

Install Omnistudio Datapacks Deploy

skills CLI

$ npx skills add forcedotcom/sf-skills --skill omnistudio-datapacks-deploy -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills omnistudio-datapacks-deploy --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omnistudio-datapacks-deploy .claude/skills/omnistudio-datapacks-deploy && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "omnistudio-datapacks-deploy" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/omnistudio-datapacks-deploy into .claude/skills/omnistudio-datapacks-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omnistudio-datapacks-deploy", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/forcedotcom/sf-skills/tree/main/skills/omnistudio-datapacks-deploy

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add forcedotcom/sf-skills --skill omnistudio-datapacks-deploy -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills omnistudio-datapacks-deploy --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/omnistudio-datapacks-deploy .agents/skills/omnistudio-datapacks-deploy && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "omnistudio-datapacks-deploy" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/omnistudio-datapacks-deploy into .agents/skills/omnistudio-datapacks-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omnistudio-datapacks-deploy", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add forcedotcom/sf-skills --skill omnistudio-datapacks-deploy -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills omnistudio-datapacks-deploy --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/omnistudio-datapacks-deploy .cursor/skills/omnistudio-datapacks-deploy && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "omnistudio-datapacks-deploy" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/omnistudio-datapacks-deploy into .cursor/skills/omnistudio-datapacks-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omnistudio-datapacks-deploy", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/forcedotcom/sf-skills.git --path skills/omnistudio-datapacks-deploy

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add forcedotcom/sf-skills --skill omnistudio-datapacks-deploy -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills omnistudio-datapacks-deploy --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/omnistudio-datapacks-deploy .gemini/skills/omnistudio-datapacks-deploy && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "omnistudio-datapacks-deploy" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/omnistudio-datapacks-deploy into .gemini/skills/omnistudio-datapacks-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omnistudio-datapacks-deploy", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install forcedotcom/sf-skills omnistudio-datapacks-deploy

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add forcedotcom/sf-skills --skill omnistudio-datapacks-deploy -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/omnistudio-datapacks-deploy .github/skills/omnistudio-datapacks-deploy && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "omnistudio-datapacks-deploy" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/omnistudio-datapacks-deploy into .github/skills/omnistudio-datapacks-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omnistudio-datapacks-deploy", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add forcedotcom/sf-skills --skill omnistudio-datapacks-deploy -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills omnistudio-datapacks-deploy --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/omnistudio-datapacks-deploy .opencode/skills/omnistudio-datapacks-deploy && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "omnistudio-datapacks-deploy" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/omnistudio-datapacks-deploy into .opencode/skills/omnistudio-datapacks-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omnistudio-datapacks-deploy", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: omnistudio-datapacks-deploy
GitHub stars: 1.1k
Token cost: ~2k tokens
SKILL.md length: 545 words
Files: 8 (incl. references)
Skills in repo: 251
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Salesforce Industries DataPack deployment automation using Vlocity Build.

Works in 6 steps: Ensure tool readiness → Validate project data locally → Export from source (when needed) → …
Validates OmniStudio/Vlocity DataPacks with vlocity commands (packDeploy/packRetry/packExport/packGetDiffs)
SKILL.md covers Scope, Critical Operating Rules, Required Context to Gather First and Recommended Workflow, plus 5 more sections
Calls sf and npm

What it does

Omnistudio Datapacks Deploy is an agent skill from forcedotcom/sf-skills. Salesforce 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 platform-metadata-deploy), authoring OmniStudio artifacts (use omnistudio--build), or writing Apex/LWC business logic (use…

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 11 other files, including reference files (for example `README.md`, `examples/business-internet-plus-bundle-deploy/TRANSCRIPT.md` and `examples/business-internet-plus-bundle-deploy/deploy-business-internet-plus-bundle.yaml`).

It sits in DevOps & Cloud, covering Deployment, CRM management and CI/CD. It works with Salesforce. The repository describes itself as: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.

When your agent uses it

Validates OmniStudio/Vlocity DataPacks with vlocity commands (packDeploy/packRetry/packExport/packGetDiffs)
Sets up DataPack CI/CD pipelines
Troubleshoots DataPack migration errors
: deploying Salesforce metadata with sf project deploy (use platform-metadata-deploy)

Example prompts

“/omnistudio-datapacks-deploy”

Requirements

Node.js

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Ensure tool readiness
Validate project data locally
Export from source (when needed)
Deploy to target
Continue interrupted jobs
Verify post-deploy parity

What it can do on your machine

Read from SKILL.md and the folder at commit e5164d9. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- sf
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Omnistudio Datapacks Deploy loads about 2k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 143 tokens; SKILL.md has 545 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~143
When it runs · the whole SKILL.md, loaded when a task matches: ~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from forcedotcom/sf-skills at commit e5164d9, republished under its Apache-2.0 licence (© forcedotcom). 545 words, ~1,962 tokens.

Download SKILL.mdSave it as .claude/skills/omnistudio-datapacks-deploy/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.

name: omnistudio-datapacks-deploy
description: Salesforce 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 platform-metadata-deploy), authoring OmniStudio artifacts (use omnistudio-*-build), or writing Apex/LWC business logic (use platform-apex-generate/experience-lwc-generate).
metadata.version: 1.0
metadata.domains: OmniStudio
metadata.relatedSkills: experience-lwc-generate, omnistudio-epc-catalog-generate, omnistudio-flexcard-generate, omnistudio-integration-procedure-generate…

omnistudio-datapacks-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.

Scope

Use omnistudio-datapacks-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 -> platform-metadata-deploy
building OmniScripts, FlexCards, IPs, or Data Mappers -> omnistudio-*-build
designing Product2 EPC bundles -> omnistudio-epc-catalog-generate
writing Apex/LWC code -> platform-apex-generate, experience-lwc-generate

Critical Operating Rules

Use Vlocity Build (vlocity) commands for DataPacks, not sf project deploy.
Prefer Salesforce CLI auth integration (-sfdx.username <alias>) over username/password files when available.
Always run a pre-deploy quality gate before full deploy:
1. validateLocalData
2. optional packGetDiffs
3. then packDeploy
Use packRetry repeatedly when error counts are dropping; stop when retries no longer improve results.
Keep matching-key strategy and GlobalKey integrity consistent across source and target orgs.

Required Context to Gather First

Ask for or infer:

source org and target org aliases
job file path and DataPack project path
deployment scope (full project, manifest subset, or specific -key)
whether this is export, deploy, retry, continue, or diff-only
namespace model (%vlocity_namespace%, vlocity_cmt, or core)
known constraints (new sandbox bootstrap, trigger behavior, matching key customizations)

Preflight checks:

bash

vlocity help
sf org list
sf org display --target-org <alias> --json
test -f <job-file>.yaml

Recommended Workflow

1. Ensure tool readiness

bash

npm install --global vlocity
vlocity help

2. Validate project data locally

bash

vlocity -sfdx.username <source-alias> -job <job-file>.yaml validateLocalData

Use --fixLocalGlobalKeys only when explicitly requested and after explaining impact.

3. Export from source (when needed)

bash

vlocity -sfdx.username <source-alias> -job <job-file>.yaml packExport
vlocity -sfdx.username <source-alias> -job <job-file>.yaml packRetry

4. Deploy to target

bash

vlocity -sfdx.username <target-alias> -job <job-file>.yaml packDeploy
vlocity -sfdx.username <target-alias> -job <job-file>.yaml packRetry

5. Continue interrupted jobs

bash

vlocity -sfdx.username <target-alias> -job <job-file>.yaml packContinue

6. Verify post-deploy parity

bash

vlocity -sfdx.username <target-alias> -job <job-file>.yaml packGetDiffs

Job-file starter: references/job-file-template.md

Gotchas

Error / symptom	Likely cause	Default fix direction
`No match found for ...`	missing dependency in target org	include missing DataPack key and redeploy
`Duplicate Results found for ... GlobalKey`	duplicate records in target	clean duplicates and re-run deploy
`Multiple Imported Records ... same Salesforce Record`	source duplicate matching-key records	remove duplicates in source and re-export
`No Configuration Found`	outdated DataPack settings	run `packUpdateSettings` or enable `autoUpdateSettings`
`Some records were not processed`	settings mismatch / partial dependency state	refresh settings both orgs, then retry
SASS / template compile failures	missing referenced UI template assets	export/deploy referenced template dependencies first

Detailed matrix: references/troubleshooting-matrix.md

Show full SKILL.md (185 more words)Show less

CI/CD Guidance

Default pipeline shape:

authenticate orgs (sf org login ...)
validate local DataPack integrity (validateLocalData)
export changed scope (packExport or manifest-driven export)
deploy (packDeploy)
retry loop (packRetry) until stable
compare (packGetDiffs) and publish deployment report

For incremental deploy optimization, use job-file options such as:

gitCheck: true
gitCheckKey: <folder>
manifest for deterministic scope control

Cross-Skill Integration

Need	Delegate to	Reason
metadata deploy outside DataPacks	platform-metadata-deploy	Metadata API workflows
OmniStudio component authoring	`omnistudio-*-build`	build artifacts before deploy
EPC product and offer payload authoring	omnistudio-epc-catalog-generate	Product2/DataPack model quality
Apex trigger/log error diagnosis	platform-apex-logs-debug, platform-apex-generate	automation-side root-cause fixes

Output Expectations

After completing a DataPack operation, deliver a completion block:

text

DataPack goal: <export / deploy / retry / diff / ci-cd>
Source org: <alias or N/A>
Target org: <alias or N/A>
Scope: <job file + manifest/key/full>
Result: <passed / failed / partial>
Key findings: <errors, dependencies, retries, diffs>
Next step: <safe follow-up action>

Reference File Index

File	When to read
`references/job-file-template.md`	Before advising on job file structure — load as baseline configuration reference
`references/troubleshooting-matrix.md`	When user reports deploy failures — load to diagnose DataPack errors and apply fix directions
`examples/business-internet-plus-bundle/TRANSCRIPT.md`	Example of validation planning and execution for a Product2 bundle
`examples/business-internet-plus-bundle/deploy-business-internet-plus-bundle.yaml`	Example job file for scope-limited `validateLocalData` run
`examples/business-internet-plus-bundle-deploy/TRANSCRIPT.md`	Example of full deploy cycle including `packDeploy` and `packRetry` outcomes
`examples/business-internet-plus-bundle-deploy/deploy-business-internet-plus-bundle.yaml`	Example job file for staged deployment with manifest targeting

Files

SKILL.md and 7 other files (references) in skills/omnistudio-datapacks-deploy of forcedotcom/sf-skills.

SKILL.md
README.md
examples/business-internet-plus-bundle-deploy/TRANSCRIPT.md
examples/business-internet-plus-bundle-deploy/deploy-business-internet-plus-bundle.yaml
examples/business-internet-plus-bundle/TRANSCRIPT.md
examples/business-internet-plus-bundle/deploy-business-internet-plus-bundle.yaml
references/job-file-template.md
references/troubleshooting-matrix.md

Open the folder on GitHubat commit e5164d9

Compare with similar skills

Omnistudio Datapacks Deploy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Omnistudio Datapacks Deploy compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Omnistudio Datapacks Deploy this skillforcedotcom/sf-skills	1.1k	—	~2k	Automated safety check: Pass	Apache-2.0	yesterday
Sf DeployJaganpro/sf-skills	424	—	~2k	Automated safety check: Pass	MIT	5 mo ago
Sf Vlocity Build DeployJaganpro/sf-skills	424	—	~1.7k	Automated safety check: Pass	MIT	5 mo ago
Salesforce DeveloperJeffallan/claude-skills	12k	—	~1.9k	Automated safety check: Pass	MIT	5 days ago
Sf DataJaganpro/sf-skills	424	—	~2.1k	Automated safety check: Pass	MIT	5 mo ago
Web Console Local Tracesforcedotcom/salesforcedx-vscode	1k	—	~796	Automated safety check: Pass	BSD-3-Clause	today

Similar skills

Sf Deploy
Jaganpro/sf-skills
Salesforce DevOps automation using sf CLI v2. An agent skill from Jaganpro/sf-skills.
424 GitHub stars~2k tokensUpdated 5 mo ago
DevOps & CloudAuto-check passed
Sf Vlocity Build Deploy
Jaganpro/sf-skills
Salesforce Industries DataPack deployment automation using Vlocity Build.
424 GitHub stars~1.7k tokensUpdated 5 mo ago
DevOps & CloudAuto-check passed
Salesforce Developer
Jeffallan/claude-skills
Writes Apex, Lightning Web Components and SOQL for the Salesforce platform, with bulkified triggers, governor-limit checks, 90% test coverage and Salesforce DX deployment.
12k GitHub stars~1.9k tokensUpdated 5 days ago
DevelopmentAuto-check passed
Sf Data
Jaganpro/sf-skills
Salesforce data operations with 130-point scoring. An agent skill from Jaganpro/sf-skills.
424 GitHub stars~2.1k tokensUpdated 5 mo ago
Testing & QAAuto-check passed
Web Console Local Traces
forcedotcom/salesforcedx-vscode
Unblock hosted Web Console OTLP to localhost:4318. An agent skill from forcedotcom/salesforcedx-vscode.
1k GitHub stars~796 tokensUpdated today
DevOps & CloudAuto-check passed
Sf Industry Cme Epc Model
Jaganpro/sf-skills
Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation.
424 GitHub stars~4.3k tokensUpdated 5 mo ago
Sales & SupportAuto-check passed

Questions about Omnistudio Datapacks Deploy

What does Omnistudio Datapacks Deploy do?

Salesforce Industries DataPack deployment automation using Vlocity Build. Omnistudio Datapacks Deploy is an agent skill from forcedotcom/sf-skills. Salesforce Industries DataPack deployment automation using Vlocity Build.

When should I use Omnistudio Datapacks Deploy?

Omnistudio Datapacks Deploy fits situations like: validates OmniStudio/Vlocity DataPacks with vlocity commands (packDeploy/packRetry/packExport/packGetDiffs); sets up DataPack CI/CD pipelines; troubleshoots DataPack migration errors; : deploying Salesforce metadata with sf project deploy (use platform-metadata-deploy).

How do I install Omnistudio Datapacks Deploy in Claude Code?

Run `npx skills add forcedotcom/sf-skills --skill omnistudio-datapacks-deploy -a claude-code`. Or copy the skill folder (skills/omnistudio-datapacks-deploy in forcedotcom/sf-skills) into .claude/skills/omnistudio-datapacks-deploy in your project. Claude Code loads it when a task matches its description.

How do I install Omnistudio Datapacks Deploy in Codex?

Run `npx skills add forcedotcom/sf-skills --skill omnistudio-datapacks-deploy -a codex`. Or copy the skill folder (skills/omnistudio-datapacks-deploy in forcedotcom/sf-skills) into .agents/skills/omnistudio-datapacks-deploy in your project. Codex loads it when a task matches its description.

Can I use Omnistudio Datapacks Deploy in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add forcedotcom/sf-skills --skill omnistudio-datapacks-deploy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omnistudio-datapacks-deploy, .gemini/skills/omnistudio-datapacks-deploy, .github/skills/omnistudio-datapacks-deploy and .opencode/skills/omnistudio-datapacks-deploy in your project.

What does Omnistudio Datapacks Deploy need to run?

Going by SKILL.md and its folder, Omnistudio Datapacks Deploy needs the command-line tools its instructions call (sf and npm). Our summary lists: Node.js.

Does Omnistudio Datapacks Deploy access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Omnistudio Datapacks Deploy safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Omnistudio Datapacks Deploy use?

Omnistudio Datapacks Deploy is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Omnistudio Datapacks Deploy use?

About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 525 tokens, read only when the agent opens those files.

What are the alternatives to Omnistudio Datapacks Deploy?

Skills that share tags, products or a category with Omnistudio Datapacks Deploy: Sf Deploy (Jaganpro/sf-skills, 424 stars), Sf Vlocity Build Deploy (Jaganpro/sf-skills, 424 stars), Salesforce Developer (Jeffallan/claude-skills, 12k stars) and Sf Data (Jaganpro/sf-skills, 424 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Omnistudio Datapacks Deploy?

forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,060 GitHub stars. The repository holds 251 skills in this directory. The repository was last updated on October 7, 2026.

Source: forcedotcom/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Omnistudio Datapacks Deploy

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

omnistudio-datapacks-deploy: Vlocity Build DataPack Deployment

Scope

Critical Operating Rules

Required Context to Gather First

Recommended Workflow

1. Ensure tool readiness

2. Validate project data locally

3. Export from source (when needed)

4. Deploy to target

5. Continue interrupted jobs

6. Verify post-deploy parity

Gotchas

CI/CD Guidance

Cross-Skill Integration

Output Expectations

Reference File Index

Files

Compare with similar skills

Similar skills

More from forcedotcom/sf-skills

Related

Questions about Omnistudio Datapacks Deploy