Platform Metadata Deploy
forcedotcom/sf-skills
Salesforce DevOps automation using sf CLI v2. An agent skill from forcedotcom/sf-skills.
Salesforce Industries DataPack deployment automation using Vlocity Build.
$ npx skills add Jaganpro/sf-skills --skill sf-vlocity-build-deploy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Jaganpro/sf-skills sf-vlocity-build-deploy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sf-vlocity-build-deploy .claude/skills/sf-vlocity-build-deploy && rm -rf skills-srcUse ~/.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/
Install the "sf-vlocity-build-deploy" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-vlocity-build-deploy into .claude/skills/sf-vlocity-build-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-vlocity-build-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 install https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-vlocity-build-deployType 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.
$ npx skills add Jaganpro/sf-skills --skill sf-vlocity-build-deploy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Jaganpro/sf-skills sf-vlocity-build-deploy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sf-vlocity-build-deploy .agents/skills/sf-vlocity-build-deploy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sf-vlocity-build-deploy" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-vlocity-build-deploy into .agents/skills/sf-vlocity-build-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-vlocity-build-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.
$ npx skills add Jaganpro/sf-skills --skill sf-vlocity-build-deploy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Jaganpro/sf-skills sf-vlocity-build-deploy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sf-vlocity-build-deploy .cursor/skills/sf-vlocity-build-deploy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sf-vlocity-build-deploy" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-vlocity-build-deploy into .cursor/skills/sf-vlocity-build-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-vlocity-build-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 https://github.com/Jaganpro/sf-skills.git --path skills/sf-vlocity-build-deploy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Jaganpro/sf-skills --skill sf-vlocity-build-deploy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Jaganpro/sf-skills sf-vlocity-build-deploy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sf-vlocity-build-deploy .gemini/skills/sf-vlocity-build-deploy && rm -rf skills-srcUse ~/.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/
Install the "sf-vlocity-build-deploy" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-vlocity-build-deploy into .gemini/skills/sf-vlocity-build-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-vlocity-build-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.
$ gh skill install Jaganpro/sf-skills sf-vlocity-build-deployInstalls 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).
$ npx skills add Jaganpro/sf-skills --skill sf-vlocity-build-deploy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sf-vlocity-build-deploy .github/skills/sf-vlocity-build-deploy && rm -rf skills-srcUse ~/.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/
Install the "sf-vlocity-build-deploy" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-vlocity-build-deploy into .github/skills/sf-vlocity-build-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-vlocity-build-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.
$ npx skills add Jaganpro/sf-skills --skill sf-vlocity-build-deploy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Jaganpro/sf-skills sf-vlocity-build-deploy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sf-vlocity-build-deploy .opencode/skills/sf-vlocity-build-deploy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sf-vlocity-build-deploy" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-vlocity-build-deploy into .opencode/skills/sf-vlocity-build-deploy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-vlocity-build-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.
sf-vlocity-build-deploySalesforce Industries DataPack deployment automation using Vlocity Build.
Sf Vlocity Build Deploy is an agent skill from Jaganpro/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 sf-deploy), authoring OmniStudio artifacts (use sf-industry-commoncore-), or writing Apex/LWC business logic (use sf-apex/sf-lwc).
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including reference files (for example `CREDITS.md`, `README.md` and `examples/business-internet-plus-bundle-deploy/TRANSCRIPT.md`).
It sits in DevOps & Cloud, covering Deployment, CRM management and CI/CD. It works with Salesforce. The repository describes itself as: [ARCHIVED — migrated to forcedotcom/afv-library] Salesforce Skills for Agentic Coding Tools — Apex, Flow, LWC, SOQL, Agentforce, Data Cloud, OmniStudio. Read-only archive; active… The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 53c9956. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
sfnpmFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Sf Vlocity Build Deploy loads about 1.7k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 131 tokens; SKILL.md has 482 words of instructions outside code blocks.
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.
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.
The full file from Jaganpro/sf-skills at commit 53c9956, republished under its MIT licence (© Jaganpro). 482 words, ~1,677 tokens.
.claude/skills/sf-vlocity-build-deploy/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.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.
Use sf-vlocity-build-deploy when work involves:
vlocity packDeploy, packRetry, packContinue, packExport, packGetDiffs, validateLocalDataprojectPath, expansionPath, manifest, queries)Delegate elsewhere when the user is:
sf project deploy -> sf-deploysf-industry-commoncore-*vlocity) commands for DataPacks, not sf project deploy.-sfdx.username <alias>) over username/password files when available.validateLocalDatapackGetDiffspackDeploypackRetry repeatedly when error counts are dropping; stop when retries no longer improve results.Ask for or infer:
-key)%vlocity_namespace%, vlocity_cmt, or core)Preflight checks:
vlocity help
sf org list
sf org display --target-org <alias> --json
test -f <job-file>.yamlnpm install --global vlocity
vlocity helpvlocity -sfdx.username <source-alias> -job <job-file>.yaml validateLocalDataUse --fixLocalGlobalKeys only when explicitly requested and after explaining impact.
vlocity -sfdx.username <source-alias> -job <job-file>.yaml packExport
vlocity -sfdx.username <source-alias> -job <job-file>.yaml packRetryvlocity -sfdx.username <target-alias> -job <job-file>.yaml packDeploy
vlocity -sfdx.username <target-alias> -job <job-file>.yaml packRetryvlocity -sfdx.username <target-alias> -job <job-file>.yaml packContinuevlocity -sfdx.username <target-alias> -job <job-file>.yaml packGetDiffsJob-file starter: references/job-file-template.md
| 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
Default pipeline shape:
sf org login ...)validateLocalData)packExport or manifest-driven export)packDeploy)packRetry) until stablepackGetDiffs) and publish deployment reportFor incremental deploy optimization, use job-file options such as:
gitCheck: truegitCheckKey: <folder>manifest for deterministic scope control| Need | Delegate to | Reason |
|---|---|---|
| metadata deploy outside DataPacks | sf-deploy | Metadata API workflows |
| OmniStudio component authoring | sf-industry-commoncore-* | build artifacts before deploy |
| EPC product and offer payload authoring | sf-industry-cme-epc-model | Product2/DataPack model quality |
| Apex trigger/log error diagnosis | sf-debug, sf-apex | automation-side root-cause fixes |
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>© Jaganpro, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 9 other files (references) in skills/sf-vlocity-build-deploy of Jaganpro/sf-skills.
Open the folder on GitHubat commit 53c9956
Sf Vlocity Build 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sf Vlocity Build Deploy this skillJaganpro/sf-skills | 424 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Platform Metadata Deployforcedotcom/sf-skills | 1.1k | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Omnistudio Datapacks Deployforcedotcom/sf-skills | 1.1k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Consumer Goods Accruals Datakit Deployforcedotcom/sf-skills | 1.1k | — | ~4.8k | Automated safety check: Pass | Apache-2.0 | |
| Dx Code Analyzer Configureforcedotcom/sf-skills | 1.1k | — | ~5.6k | Automated safety check: Pass | Apache-2.0 | |
| Dx Devops Pipeline Manageforcedotcom/sf-skills | 1.1k | — | ~4.9k | Automated safety check: Pass | Apache-2.0 |
forcedotcom/sf-skills
Salesforce DevOps automation using sf CLI v2. An agent skill from forcedotcom/sf-skills.
forcedotcom/sf-skills
Salesforce Industries DataPack deployment automation using Vlocity Build.
forcedotcom/sf-skills
A skill your agent uses to deploy the TPM Liability Accruals data kit end to end to a Salesforce org.
forcedotcom/sf-skills
Set up, configure, and troubleshoot Salesforce Code Analyzer for any project.
forcedotcom/sf-skills
A skill your agent uses to manage the full lifecycle of a DevOps Center pipeline — list all pipelines, get a single pipeline's details, create a new pipeline linked to a Git repository, add or…
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.
Jaganpro/sf-skills
Agentforce session tracing extraction and analysis. An agent skill from Jaganpro/sf-skills.
Jaganpro/sf-skills
Agent Script DSL for deterministic Agentforce agents. An agent skill from Jaganpro/sf-skills.
Jaganpro/sf-skills
Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows.
Jaganpro/sf-skills
Salesforce architecture diagrams using Mermaid with ASCII fallback.
Jaganpro/sf-skills
AI-powered image generation for Salesforce visuals via Nano Banana Pro.
Jaganpro/sf-skills
Creates and validates Salesforce Flows with 110-point scoring.
Works with
Categories
Salesforce Industries DataPack deployment automation using Vlocity Build. Sf Vlocity Build Deploy is an agent skill from Jaganpro/sf-skills. Salesforce Industries DataPack deployment automation using Vlocity Build.
Sf Vlocity Build 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 sf-deploy).
Run `npx skills add Jaganpro/sf-skills --skill sf-vlocity-build-deploy -a claude-code`. Or copy the skill folder (skills/sf-vlocity-build-deploy in Jaganpro/sf-skills) into .claude/skills/sf-vlocity-build-deploy in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Jaganpro/sf-skills --skill sf-vlocity-build-deploy -a codex`. Or copy the skill folder (skills/sf-vlocity-build-deploy in Jaganpro/sf-skills) into .agents/skills/sf-vlocity-build-deploy in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jaganpro/sf-skills --skill sf-vlocity-build-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/sf-vlocity-build-deploy, .gemini/skills/sf-vlocity-build-deploy, .github/skills/sf-vlocity-build-deploy and .opencode/skills/sf-vlocity-build-deploy in your project.
Going by SKILL.md and its folder, Sf Vlocity Build Deploy needs the command-line tools its instructions call (sf and npm). Our summary lists: Node.js.
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
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.
Sf Vlocity Build Deploy is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.7k tokens (SKILL.md is roughly 6.7k 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.
Skills that share tags, products or a category with Sf Vlocity Build Deploy: Platform Metadata Deploy (forcedotcom/sf-skills, 1.1k stars), Omnistudio Datapacks Deploy (forcedotcom/sf-skills, 1.1k stars), Consumer Goods Accruals Datakit Deploy (forcedotcom/sf-skills, 1.1k stars) and Dx Code Analyzer Configure (forcedotcom/sf-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Jaganpro (a GitHub user) maintains it in Jaganpro/sf-skills, which has 424 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on April 27, 2026.
Source: Jaganpro/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.