@salesforce/afv-skills 1.22.0 → 1.24.0

package/skills/deploying-omnistudio-datapacks/examples/business-internet-plus-bundle/TRANSCRIPT.md

@@ -1,124 +0,0 @@
-# Validation Transcript: Business Internet Plus Bundle Deployment
-
-This transcript captures the skills used and the planning/execution process to validate deployment readiness for the `business-internet-plus-bundle` sample.
-
----
-
-## Task Summary
-
-Validate deployment for the `Business Internet Plus` bundle and document the process in a new `examples` folder under `deploying-omnistudio-datapacks`.
-
----
-
-## Skills Used
-
-### 1) `deploying-omnistudio-datapacks` (Primary)
-
-**Why used:** The task is Vlocity Build deployment validation for DataPacks (`validateLocalData`, deployment preflight, and scope verification).
-
-**Applied from skill guidance:**
-
-- Validate-first workflow (`validateLocalData` before deploy).
-- Required context checks (tooling readiness, org auth, deterministic scope).
-- Job-file driven validation with explicit manifest targeting.
-
-### 2) `deploying-metadata` (Supporting)
-
-**Why used:** Deployment preflight practices overlap with org readiness checks.
-
-**Applied from skill guidance:**
-
-- Confirm CLI and org context before execution.
-- Capture result and safe next action in a completion block.
-
-### 3) `modeling-omnistudio-epc-catalog` (Supporting)
-
-**Why used:** The target bundle payload was generated as an EPC Product2 offer bundle sample, so EPC-specific structure and guardrails were validated before deployment checks.
-
-**Applied from skill guidance:**
-
-- Confirm offer markers (`SpecificationType=Offer`, `SpecificationSubType=Bundle`).
-- Confirm root PCI + child PCI composition.
-- Confirm companion bundle artifacts and GlobalKey consistency.
-
----
-
-## Planning Process (Executed)
-
-1. Locate the `business-internet-plus-bundle` payload and confirm all companion JSON artifacts exist.
-2. Run preflight checks for deployment tooling:
-   - `vlocity` CLI availability.
-   - Salesforce org auth context for target alias.
-3. Run file-level integrity checks:
-   - JSON parse for all bundle artifacts.
-   - Product2 + PCI + attribute consistency checks.
-4. Create a deterministic Vlocity Build job file in this example folder for reproducible validation.
-5. Execute `validateLocalData` against the bundle scope and record outcome.
-6. Summarize result, findings, and safe next actions.
-
----
-
-## Execution Log
-
-### A) Bundle discovery
-
-- Located bundle payload at:
-  - `skills/modeling-omnistudio-epc-catalog/examples/business-internet-plus-bundle`
-- Confirmed 11 companion JSON files exist (`DataPack`, `AttributeAssignments`, `ProductChildItems`, pricing files, orchestration/decomposition files, overrides, and parent keys).
-
-### B) Tooling and org preflight
-
-- `vlocity` global binary check: **not installed globally** (`command not found`).
-- `npx vlocity` check: **available** (`Vlocity Build v1.17.21`).
-- `sf org list --json`: org context available; target alias `sample-uat` is connected.
-
-### C) File-level integrity validation
-
-Local JSON validation checks passed:
-
-- Missing files: `0`
-- JSON parse errors: `0`
-- Product identity checks: name and product code match expected values.
-- Offer checks: `SpecificationType=Offer` and `SpecificationSubType=Bundle`.
-- Composition checks: `1` root PCI and `3` child PCI records.
-- Attribute checks: `3` attribute assignment records.
-- Key integrity checks: PCI parent references match Product2 GlobalKey.
-
-### D) Vlocity validateLocalData execution
-
-Job file used:
-
-- `skills/deploying-omnistudio-datapacks/examples/business-internet-plus-bundle/deploy-business-internet-plus-bundle.yaml`
-
-Command:
-
-```bash
-npx --yes vlocity -sfdx.username sample-uat -job "skills/deploying-omnistudio-datapacks/examples/business-internet-plus-bundle/deploy-business-internet-plus-bundle.yaml" validateLocalData
-```
-
-Result:
-
-- `ValidateLocalData success: 0 Completed`
-
-Interpretation:
-
-- Validation command executed successfully.
-- `0 Completed` indicates no DataPack records were processed for this scope layout.
-- This is consistent with the sample payload being stored as a documentation/example artifact rather than a standard `vlocity/` expansion deployment path.
-
----
-
-## Validation Outcome
-
-```text
-DataPack goal: validate deployment readiness
-Source org: N/A
-Target org: sample-uat
-Scope: deploy-business-internet-plus-bundle.yaml + Product2/9f1d3c4a-8e5b-4d71-9a2d-f6b719a90101
-Result: partial
-Key findings:
-- Bundle JSON payload is internally consistent and structurally valid.
-- Vlocity validateLocalData ran successfully but processed 0 DataPacks in current example-folder scope.
-Next step:
-- Stage the bundle into a standard Vlocity expansion path (for example under `vlocity/Product2/<global-key>/`) and rerun `validateLocalData`, then `packDeploy` and `packGetDiffs`.
-```

package/skills/deploying-omnistudio-datapacks/examples/business-internet-plus-bundle/deploy-business-internet-plus-bundle.yaml

@@ -1,11 +0,0 @@
-projectPath: ../../../../
-expansionPath: skills/modeling-omnistudio-epc-catalog/examples/business-internet-plus-bundle
-
-# Deterministic scope for this validation example.
-manifest:
-  - Product2/9f1d3c4a-8e5b-4d71-9a2d-f6b719a90101
-
-autoUpdateSettings: true
-defaultMaxParallel: 1
-supportHeadersOnly: true
-gitCheck: false

package/skills/deploying-omnistudio-datapacks/examples/business-internet-plus-bundle-deploy/TRANSCRIPT.md

@@ -1,142 +0,0 @@
-# Deployment Transcript: Business Internet Plus Bundle
-
-This transcript captures the skills used plus the planning and execution process for deploying `business-internet-plus-bundle` with Vlocity Build.
-
----
-
-## Task Summary
-
-Deploy the `Business Internet Plus` Product2 bundle DataPack and document the end-to-end process in `deploying-omnistudio-datapacks/examples`.
-
----
-
-## Skills Used
-
-### 1) `deploying-omnistudio-datapacks` (Primary)
-
-**Why used:** The task is DataPack deployment orchestration with Vlocity Build commands (`validateLocalData`, `packDeploy`, `packRetry`) and failure triage.
-
-**Applied guidance:**
-
-- Validate-first execution (`validateLocalData` before deployment).
-- Deterministic job file (`projectPath`, `expansionPath`, `manifest`) for reproducible scope.
-- Retry loop and failure interpretation.
-
-### 2) `modeling-omnistudio-epc-catalog` (Supporting)
-
-**Why used:** The deployment target is an EPC Product2 offer bundle sample with Product Child Item dependencies and companion artifacts.
-
-**Applied guidance:**
-
-- Confirmed Product2 offer markers and companion file consistency.
-- Preserved `%vlocity_namespace%` placeholders and stable GlobalKey references.
-
-### 3) `deploying-metadata` (Supporting preflight pattern)
-
-**Why used:** Reused deployment preflight discipline for target org/tooling readiness and concise completion reporting.
-
----
-
-## Planning Process (Executed)
-
-1. Confirm where the source bundle artifacts were authored.
-2. Stage those artifacts into a standard Vlocity expansion path under `vlocity/Product2/<global-key>/`.
-3. Build a deterministic deploy job file in this example folder.
-4. Run pre-deploy validation (`validateLocalData`).
-5. Run actual deployment (`packDeploy`).
-6. Run retry (`packRetry`) to confirm whether the failure is transient or dependency-blocking.
-7. Capture findings and next safe action.
-
----
-
-## Execution Details
-
-### A) Staging for deploy
-
-Source payload location:
-
-- `skills/modeling-omnistudio-epc-catalog/examples/business-internet-plus-bundle`
-
-Deploy staging location:
-
-- `vlocity/Product2/9f1d3c4a-8e5b-4d71-9a2d-f6b719a90101`
-
-Staged files include:
-
-- `Business-Internet-Plus_DataPack.json`
-- `Business-Internet-Plus_AttributeAssignments.json`
-- `Business-Internet-Plus_ProductChildItems.json`
-- `Business-Internet-Plus_PricebookEntries.json`
-- `Business-Internet-Plus_PriceListEntries.json`
-- `Business-Internet-Plus_ObjectFieldAttributes.json`
-- `Business-Internet-Plus_OrchestrationScenarios.json`
-- `Business-Internet-Plus_DecompositionRelationships.json`
-- `Business-Internet-Plus_CompiledAttributeOverrides.json`
-- `Business-Internet-Plus_OverrideDefinitions.json`
-- `Business-Internet-Plus_ParentKeys.json`
-
-### B) Job file used
-
-- `skills/deploying-omnistudio-datapacks/examples/business-internet-plus-bundle-deploy/deploy-business-internet-plus-bundle.yaml`
-
-Key settings:
-
-- `projectPath: .`
-- `expansionPath: vlocity`
-- `manifest: Product2/9f1d3c4a-8e5b-4d71-9a2d-f6b719a90101`
-
-### C) Commands executed
-
-```bash
-npx --yes vlocity -sfdx.username sample-uat -job "skills/deploying-omnistudio-datapacks/examples/business-internet-plus-bundle-deploy/deploy-business-internet-plus-bundle.yaml" validateLocalData
-
-npx --yes vlocity -sfdx.username sample-uat -job "skills/deploying-omnistudio-datapacks/examples/business-internet-plus-bundle-deploy/deploy-business-internet-plus-bundle.yaml" packDeploy
-
-npx --yes vlocity -sfdx.username sample-uat -job "skills/deploying-omnistudio-datapacks/examples/business-internet-plus-bundle-deploy/deploy-business-internet-plus-bundle.yaml" packRetry
-```
-
-### D) Command outcomes
-
-`validateLocalData`:
-
-- Success (`1 Completed`)
-
-`packDeploy`:
-
-- Auto-settings migration phase completed successfully.
-- Bundle deploy failed with dependency error:
-  - `This DataPack has a reference to another object which was not found -- Product2/21e9dce1-4f89-4f99-a7b2-9cb5d6332101`
-
-`packRetry`:
-
-- Failed with the same missing reference error.
-
----
-
-## Root Cause
-
-The bundle references child Product2 DataPacks that are not currently present in local expansion scope and/or target org at deploy time.
-
-Missing child Product2 keys confirmed absent from local `vlocity/Product2`:
-
-- `21e9dce1-4f89-4f99-a7b2-9cb5d6332101` (Managed Router)
-- `43f2fd94-6114-449b-a1b4-b8dd7238b202` (Internet Security Suite)
-- `64a06b24-1135-4f2e-95a1-3a5f5822c303` (Static IP Add-On)
-
----
-
-## Completion Block
-
-```text
-DataPack goal: deploy
-Source org: N/A (local staged payload)
-Target org: sample-uat
-Scope: Product2/9f1d3c4a-8e5b-4d71-9a2d-f6b719a90101
-Result: failed (dependency missing)
-Key findings:
-- validateLocalData passed (1 completed)
-- packDeploy failed: missing referenced child Product2
-- packRetry failed with same error
-Next step:
-- Stage/deploy the three child Product2 DataPacks first (or include them in manifest), then rerun packDeploy and packRetry.
-```

package/skills/deploying-omnistudio-datapacks/examples/business-internet-plus-bundle-deploy/deploy-business-internet-plus-bundle.yaml

@@ -1,10 +0,0 @@
-projectPath: .
-expansionPath: vlocity
-
-manifest:
-  - Product2/9f1d3c4a-8e5b-4d71-9a2d-f6b719a90101
-
-autoUpdateSettings: true
-defaultMaxParallel: 1
-supportHeadersOnly: true
-gitCheck: false

package/skills/deploying-omnistudio-datapacks/references/job-file-template.md

@@ -1,42 +0,0 @@
-# Vlocity Build Job File Template
-
-Use this as a baseline and keep only settings you need to override.
-
-```yaml
-projectPath: .
-expansionPath: vlocity
-
-# Optional: narrow export scope
-queries:
-  - OmniScript
-  - IntegrationProcedure
-  - DataRaptor
-  - FlexCard
-
-# Optional: deterministic targeted scope
-# manifest:
-#   - Product2/<global-key>
-#   - OmniScript/<type>_<subtype>_<language>
-
-# Optional runtime controls
-autoUpdateSettings: true
-defaultMaxParallel: 1
-supportHeadersOnly: true
-gitCheck: false
-```
-
-## Common command patterns
-
-```bash
-# Export
-vlocity -sfdx.username <source> -job <job>.yaml packExport
-
-# Deploy
-vlocity -sfdx.username <target> -job <job>.yaml packDeploy
-
-# Retry
-vlocity -sfdx.username <target> -job <job>.yaml packRetry
-
-# Continue interrupted
-vlocity -sfdx.username <target> -job <job>.yaml packContinue
-```

package/skills/deploying-omnistudio-datapacks/references/troubleshooting-matrix.md

@@ -1,24 +0,0 @@
-# Vlocity Build Troubleshooting Matrix
-
-| Symptom | Quick checks | Typical fix |
-|---|---|---|
-| `No match found for ...` | Is referenced key present in exported folder and target org? | Deploy missing dependency first, then `packRetry` |
-| `Duplicate Results found for ... GlobalKey` | Query target org for duplicate GlobalKey values | Remove duplicates in target, rerun deploy |
-| `Multiple Imported Records ... same Salesforce Record` | Check source for duplicate matching-key combinations | Clean source data, re-export, then redeploy |
-| `No Configuration Found` | Was `packUpdateSettings` run recently? | Run `packUpdateSettings` (or keep `autoUpdateSettings: true`) |
-| `Some records were not processed` | Compare settings and package versions across orgs | Refresh settings in both orgs, then `packRetry` |
-| SASS/template compile errors | Are referenced UI templates exported? | Export missing templates by key and redeploy |
-
-## Retry strategy
-
-1. Run `packRetry`.
-2. Check if error count decreases.
-3. Repeat until error count plateaus.
-4. Fix root data/config issue before further retries.
-
-## Data hygiene checks
-
-```bash
-vlocity -sfdx.username <org> -job <job>.yaml validateLocalData
-vlocity -sfdx.username <org> -job <job>.yaml packGetDiffs
-```

package/skills/deploying-ui-bundle/SKILL.md

@@ -1,79 +0,0 @@
----
-name: deploying-ui-bundle
-description: "MUST activate when the project contains a uiBundles/*/src/ directory or sfdx-project.json and the task involves deploying, pushing to an org, or post-deploy setup. Use this skill when deploying a UI bundle app to a Salesforce org. Covers the full deployment sequence: org authentication, pre-deploy build, metadata deployment, permission set assignment, data import, GraphQL schema fetch, and codegen. Activate when files like *.uibundle-meta.xml or sfdx-project.json exist and the user mentions deploying, pushing, org setup, or post-deploy tasks."
-metadata:
-  version: "1.0"
----
-
-# Deploying a UI Bundle
-
-The order of operations is critical when deploying to a Salesforce org. This sequence reflects the canonical flow.
-
-## Step 1: Org Authentication
-
-Check if the org is connected. If not, authenticate. All subsequent steps require an authenticated org.
-
-## Step 2: Pre-deploy UI Bundle Build
-
-Install dependencies and build the UI bundle to produce `dist/`. Required before deploying UI bundle entities.
-
-Run when: deploying UI bundles and `dist/` is missing or source has changed.
-
-## Step 3: Deploy Metadata
-
-Check for a manifest (`manifest/package.xml` or `package.xml`) first. If present, deploy using the manifest. If not, deploy all metadata from the project.
-
-Deploys objects, layouts, permission sets, Apex classes, UI bundles, and all other metadata. Must complete before schema fetch — the schema reflects org state.
-
-## Step 4: Post-deploy Configuration
-
-Deploying does not mean assigning. After deployment:
-
-- **Permission sets / groups** — assign to users so they have access to custom objects and fields. Required for GraphQL introspection to return the correct schema.
-- **Profiles** — ensure users have the correct profile.
-- **Other config** — named credentials, connected apps, custom settings, flow activation.
-
-Proactive behavior: after a successful deploy, discover permission sets in `force-app/main/default/permissionsets/` and assign each one (or ask the user).
-
-## Step 5: Data Import (optional)
-
-Only if `data/data-plan.json` exists. Delete runs in reverse plan order (children before parents). Import uses Anonymous Apex with duplicate rule save enabled.
-
-Always ask the user before importing or cleaning data.
-
-## Step 6: GraphQL Schema and Codegen
-
-1. Set default org
-2. Fetch schema (GraphQL introspection) — writes `schema.graphql` at project root
-3. Generate types (codegen reads schema locally)
-
-Run when: schema missing, or metadata/permissions changed since last fetch.
-
-## Step 7: Final UI Bundle Build
-
-Build the UI bundle if not already done in Step 2.
-
-## Summary: Interaction Order
-
-1. Check/authenticate org
-2. Build UI bundle (if deploying UI bundles)
-3. Deploy metadata
-4. Assign permissions and configure
-5. Import data (if data plan exists, with user confirmation)
-6. Fetch GraphQL schema and run codegen
-7. Build UI bundle (if needed)
-
-## Critical Rules
-
-- Deploy metadata **before** fetching schema — custom objects/fields appear only after deployment
-- Assign permissions **before** schema fetch — the user may lack FLS for custom fields
-- Re-run schema fetch and codegen **after every metadata deployment** that changes objects, fields, or permissions
-- Never skip permission set assignment or data import silently — either run them or ask the user
-
-## Post-deploy Checklist
-
-After every successful metadata deploy:
-
-1. Discover and assign permission sets (or ask the user)
-2. If `data/data-plan.json` exists, ask the user about data import
-3. Re-run schema fetch and codegen from the UI bundle directory

package/skills/developing-agentforce/README.md

@@ -1,112 +0,0 @@
-# Agentforce Development Skill
-
-A Claude Code skill for building, modifying, debugging, and deploying Agentforce agents using Agent Script — Salesforce's scripting language for next-generation AI agents on the Atlas Reasoning Engine.
-
-## What This Skill Does
-
-Agent Script was introduced in 2025 with zero training data in any AI model. This skill bridges that gap by providing structured reference material, design patterns, CLI workflows, and debugging guidance so that AI coding assistants can work with Agent Script accurately.
-
-The skill covers the full Agent Script lifecycle:
-
-| Domain | What It Handles |
-|--------|----------------|
-| Create an Agent | Agent Spec design, environment validation, bundle generation, code authoring |
-| Modify an Agent | Subagent/action changes, instruction refinement, flow control updates |
-| Create or Modify Backing Logic | Invocable Apex stubs, Flow wrappers, Prompt Templates |
-| Deploy and Publish | Source deploy, agent activation, publishing to channels |
-| Diagnose Compilation Errors | Compiler error interpretation, syntax fixes, metadata resolution |
-| Diagnose Behavioral Issues | Trace-based debugging, subagent routing, action I/O analysis |
-| Diagnose Production Issues | Runtime failures, reserved keyword conflicts, deployment gotchas |
-| Test an Agent | Utterance-based validation, preview with live actions, trace analysis |
-| Generate Diagrams | Subagent map visualizations, agent architecture diagrams |
-
-## Skill Structure
-
-```
-developing-agentforce/
-├── SKILL.md                    # Router — maps user intent to task domains and reference files
-├── references/                 # Domain knowledge (14 files)
-│   ├── agent-script-core-language.md
-│   ├── agent-design-and-spec-creation.md
-│   ├── agent-validation-and-debugging.md
-│   ├── salesforce-cli-for-agents.md
-│   ├── agent-metadata-and-lifecycle.md
-│   ├── agent-access-guide.md
-│   ├── agent-user-setup.md
-│   ├── actions-reference.md
-│   ├── action-prompt-templates.md
-│   ├── agent-subagent-map-diagrams.md
-│   ├── minimal-examples.md
-│   ├── known-issues.md
-│   ├── production-gotchas.md
-│   └── version-history.md
-├── assets/                     # Templates, examples, and starter agents
-│   ├── agent-spec-template.md
-│   ├── invocable-apex-template.cls
-│   ├── bundle-meta.xml
-│   ├── patterns/               # Reusable Agent Script patterns
-│   ├── agents/                 # Annotated example agents
-│   ├── apex/                   # Apex backing logic examples
-│   ├── components/             # LWC components for agent channels
-│   ├── metadata/               # Metadata templates
-│   └── *.agent                 # Starter agent templates
-└── staging/                    # Unmerged reference material awaiting review
-```
-
-## How It Works
-
-SKILL.md acts as a router. It detects user intent from task descriptions, maps to a task domain, and instructs the AI assistant to read the relevant reference files before starting work. Reference files are loaded on demand — the assistant only reads what the current task requires.
-
-Three rules apply across all domains:
-
-1. **Always `--json`** on every `sf` CLI command
-2. **Diagnose before you fix** — preview with live actions and read traces before modifying code
-3. **Spec approval is a hard gate** — never proceed past Agent Spec creation without user approval
-
-## Prerequisites
-
-- Salesforce org with Agentforce license
-- API version 66.0+ (Spring '26)
-- Einstein Agent User (for service agents)
-- Salesforce CLI v2.x (`sf` command)
-- Claude Code (or compatible AI coding agent)
-
-## Installation
-
-Copy the `developing-agentforce` folder into your project's `.claude/skills/` directory:
-
-```
-your-project/
-└── .claude/
-    └── skills/
-        └── developing-agentforce/
-            ├── SKILL.md
-            ├── references/
-            └── assets/
-```
-
-Restart Claude Code after installation.
-
-## Version
-
-Current version: **0.4.9** (2026-03-20). See [references/version-history.md](references/version-history.md) for the full changelog.
-
-## Credits
-
-This skill integrates knowledge from the following sources:
-
-**Jag Valaiyapathy** ([sf-skills](https://github.com/Jaganpro/sf-skills), MIT License)
-— Known issues catalog, production gotchas, agent access and permissions guide, and deployment patterns. Integrated starting in v0.4.2.
-
-**Hua Xu** (Salesforce APAC FDE team)
-— Open-gate routing pattern from Kogan agent deployment.
-
-**Salesforce DevRel** ([agent-script-recipes](https://github.com/trailheadapps/agent-script-recipes))
-— Canonical Agent Script examples used as grounding material.
-
-**Dylan Zeigler, AI Platform** (llm-utils)
-— Agent Script playground used as reference source.
-
-## License
-
-Apache-2.0