技能库
智客分类:运维与云
omnistudio-datapacks-deploy
Omnistudio Datapacks Deploy
销售力量工业 DataPack 使用 Vlocity Build 进行部署自动化. TRIGGER 当:用户部署或验证OmniStudio/Vlocity DataPack并带有活性指令(packDeploy/packRetry/packExport/packGetDiffs),设置DataPack CI/CD管道,或出错DataPack迁移错误. 在以下情况下不要TRIGGER:使用 Sf 项目部署(使用平台-元数据-部署),编写 OmniStudio 文物(使用 omnistudio- *- 构建),或写 Apex/LWC 业务逻辑(使用平台- apex- generate/ experience-lwc-generate).
SKILL.md / Agent 安装方式 SKILL.md 原文
4676 安装量
官方网址:skills.sh
技能介绍
先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。
做什么
销售力量工业 DataPack 使用 Vlocity Build 进行部署自动化. TRIGGER 当:用户部署或验证OmniStudio/Vlocity DataPack并带有活性指令(packDeploy/packRetry/packExport/packGetDiffs),设置DataPack CI/CD管道,或出错DataPack迁移错误. 在以下情况下不要TRIGGER:使用 Sf 项目部署(使用平台-元数据-部署),编写 OmniStudio 文物(使用 omnistudio- *- 构建),或写 Apex/LWC 业务逻辑(使用平台- apex- generate/ experience-lwc-generate).
何时用
官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。
代理如何加载
按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:omnistudio-datapacks-deploy: Vlocity Build DataPack Deployment、Scope、Critical Operating Rules、Required Context to Gather First、Recommended Workflow、1. Ensure tool readiness。 其中含规范建议的小节:分步指令。
文件分析
文件分析:除 SKILL.md 外,正文引用了 references/job-file-template.md、references/troubleshooting-matrix.md,属于带资源的技能包,这些文件按需再读。
官方 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).
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
来源分类:skills.sh agent-skill
来源与网址
nameomnistudio-datapacks-deploy
descriptionSalesforce 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).
发现技能 客户端向 Agent 提供名称与描述目录。
匹配与调用 用户指定或任务匹配后,载入 SKILL.md 指令。
按需加载 按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 2 references/job-file-template.mdreferences/troubleshooting-matrix.md以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。
具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗
先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。
该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。
交给 Agent 安装
复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。
把 Agent Skill「omnistudio-datapacks-deploy」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-e3ec365964bb51ab-%E9%83%A8%E7%BD%B2%E6%95%B0%E6%8D%AE%E5%8C%85.html
请存为 .cursor/skills/omnistudio-datapacks-deploy/SKILL.md 或 .claude/skills/omnistudio-datapacks-deploy/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/forcedotcom/sf-skills 取完整目录,不要只建一个 SKILL.md。
复制安装提示词 GitHub 完整包 ↗
终端安装 · Skills CLI
需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。
npx skills add 'https://github.com/forcedotcom/sf-skills' --list
复制查看命令
目标客户端
安装时交互选择 Codex Claude Code Cursor
安装范围
当前项目 我的所有项目
npx skills add 'https://github.com/forcedotcom/sf-skills' --skill 'omnistudio-datapacks-deploy' 复制安装命令
CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。
SKILL.md 原文 可复制,不会改动源文件
复制 SKILL.md
恢复原文
阅读排版
---
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:
cliTools:
- tool: ["npm"]
semver: ">=9.0.0"
- tool: ["npx"]
semver: ">=9.0.0"
- tool: ["sf"]
semver: ">=2.0.0"
- tool: ["vlocity"]
semver: ">=1.16.0"
relatedSkills:
- "experience-lwc-generate"
- "omnistudio-epc-catalog-generate"
- "omnistudio-flexcard-generate"
- "omnistudio-integration-procedure-generate"
- "omnistudio-omniscript-generate"
- "platform-apex-generate"
- "platform-apex-logs-debug"
- "platform-metadata-deploy"
version: "1.0"
domains: ["OmniStudio"]
---
# 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](../platform-metadata-deploy/SKILL.md)
- building OmniScripts, FlexCards, IPs, or Data Mappers -> `omnistudio-*-build`
- designing Product2 EPC bundles -> [omnistudio-epc-catalog-generate](../omnistudio-epc-catalog-generate/SKILL.md)
- writing Apex/LWC code -> [platform-apex-generate](../platform-apex-generate/SKILL.md), [experience-lwc-generate](../experience-lwc-generate/SKILL.md)
---
## Critical Operating Rules
- Use **Vlocity Build (`vlocity`)** commands for DataPacks, not `sf project deploy`.
- Prefer Salesforce CLI auth integration (`-sfdx.username `) 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 --json
test -f .yaml
```
---
## Recommended Workflow
### 1. Ensure tool readiness
```bash
npm install --global vlocity
vlocity help
```
### 2. Validate project data locally
```bash
vlocity -sfdx.username -job .yaml validateLocalData
```
Use `--fixLocalGlobalKeys` only when explicitly requested and after explaining impact.
### 3. Export from source (when needed)
```bash
vlocity -sfdx.username -job .yaml packExport
vlocity -sfdx.username -job .yaml packRetry
```
### 4. Deploy to target
```bash
vlocity -sfdx.username -job .yaml packDeploy
vlocity -sfdx.username -job .yaml packRetry
```
### 5. Continue interrupted jobs
```bash
vlocity -sfdx.username -job .yaml packContinue
```
### 6. Verify post-deploy parity
```bash
vlocity -sfdx.username -job .yaml packGetDiffs
```
Job-file starter: [references/job-file-template.md](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](references/troubleshooting-matrix.md)
---
## CI/CD Guidance
Default pipeline shape:
1. authenticate orgs (`sf org login ...`)
2. validate local DataPack integrity (`validateLocalData`)
3. export changed scope (`packExport` or manifest-driven export)
4. deploy (`packDeploy`)
5. retry loop (`packRetry`) until stable
6. compare (`packGetDiffs`) and publish deployment report
For incremental deploy optimization, use job-file options such as:
- `gitCheck: true`
- `gitCheckKey: `
- `manifest` for deterministic scope control
---
## Cross-Skill Integration
| Need | Delegate to | Reason |
|---|---|---|
| metadata deploy outside DataPacks | [platform-metadata-deploy](../platform-metadata-deploy/SKILL.md) | Metadata API workflows |
| OmniStudio component authoring | `omnistudio-*-build` | build artifacts before deploy |
| EPC product and offer payload authoring | [omnistudio-epc-catalog-generate](../omnistudio-epc-catalog-generate/SKILL.md) | Product2/DataPack model quality |
| Apex trigger/log error diagnosis | [platform-apex-logs-debug](../platform-apex-logs-debug/SKILL.md), [platform-apex-generate](../platform-apex-generate/SKILL.md) | automation-side root-cause fixes |
---
## Output Expectations
After completing a DataPack operation, deliver a completion block:
```text
DataPack goal:
Source org:
Target org:
Scope:
Result:
Key findings:
Next step:
```
---
## 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 |
相关技能
运维与云
用于容器管理,图像操作,调试的基本道克命令和工作流程.
运维与云
从开放的代理技能生态系统中发现并安装技能. 使用时:(1)用户问"我如何做X",X可能拥有现有技能,(2)用户说"为X找到技能"或"是否为X有技能",(3)用户问"你能否做X",X是专门能力,(4)用户想扩展代理能力,(5)用户想搜索工具,模板,或工作流程,(6)用户提到他们希望…
运维与云
构建,部署,评价,优化,微调,管理微软创始代理,模型,资源最终结束. 用法:铸造、azd ai代理、azd 提供/部署、托管代理脚手架/开发/运行/部署/拖放、即时代理创建、创建代理、更新代理、添加代理工具、援引代理、代理.yaml、评估代理、批量活化、连续活化、持续监测、代理C…
运维与云
执行已有.azure/部署计划.md和基础设施文件的ALREADY-PREPARED应用程序的Azure部署。 当用户向 CREATE 请求新应用程序时, 请不要使用此技能 。 这种技能运行了 azd上行, azd 部署, trarraform 应用, 和 az 部署命令带有内置…