@salesforce/afv-skills 1.22.0 → 1.24.0

package/skills/analyzing-omnistudio-dependencies/references/namespace-guide.md

@@ -1,300 +0,0 @@
-<!-- Parent: analyzing-omnistudio-dependencies/SKILL.md -->
-
-# OmniStudio Namespace Reference Guide
-
-## Overview
-
-Salesforce OmniStudio exists under three distinct namespaces depending on the org's industry package and migration status. Every OmniStudio operation must target the correct namespace — queries, metadata retrieval, and deployment all use namespace-specific object and field API names.
-
-| Namespace | Package Context | Typical Orgs |
-|-----------|----------------|--------------|
-| **Core** (no prefix) | Industries / OmniStudio managed package migrated to Core | Orgs on API 234.0+ (Spring '22+) that have completed the Core migration |
-| **vlocity_cmt** | Vlocity Communications, Media & Energy | Telco, media, energy & utilities industry orgs |
-| **vlocity_ins** | Vlocity Insurance & Health | Insurance, health, and life sciences industry orgs |
-
----
-
-## Detection Algorithm
-
-### Step-by-Step Probing
-
-Run SOQL queries against each namespace's primary object. The first query that succeeds determines the namespace.
-
-```
-1. Probe Core:
-   SELECT COUNT() FROM OmniProcess
-   → Success? Namespace = Core. Stop.
-   → Failure (INVALID_TYPE)? Continue.
-
-2. Probe vlocity_cmt:
-   SELECT COUNT() FROM vlocity_cmt__OmniScript__c
-   → Success? Namespace = vlocity_cmt. Stop.
-   → Failure (INVALID_TYPE)? Continue.
-
-3. Probe vlocity_ins:
-   SELECT COUNT() FROM vlocity_ins__OmniScript__c
-   → Success? Namespace = vlocity_ins. Stop.
-   → Failure (INVALID_TYPE)? OmniStudio not installed.
-```
-
-### CLI Implementation
-
-```bash
-# Core probe
-sf data query --query "SELECT COUNT() FROM OmniProcess" --target-org myorg --json 2>/dev/null
-# Check: result.totalSize >= 0 means Core namespace
-
-# vlocity_cmt probe
-sf data query --query "SELECT COUNT() FROM vlocity_cmt__OmniScript__c" --target-org myorg --json 2>/dev/null
-
-# vlocity_ins probe
-sf data query --query "SELECT COUNT() FROM vlocity_ins__OmniScript__c" --target-org myorg --json 2>/dev/null
-```
-
-### Interpreting Results
-
-- **Exit code 0 + JSON with `totalSize`**: Namespace is present
-- **Exit code non-zero or `INVALID_TYPE` error**: Namespace not installed
-- **Exit code 0 + `totalSize: 0`**: Namespace exists but no components created yet (still valid)
-
----
-
-## Object Mapping
-
-### Primary Container Objects
-
-These objects store OmniScript, Integration Procedure, FlexCard, and Data Mapper definitions.
-
-| Concept | Core | vlocity_cmt | vlocity_ins |
-|---------|------|-------------|-------------|
-| OmniScript / Integration Procedure | `OmniProcess` | `vlocity_cmt__OmniScript__c` | `vlocity_ins__OmniScript__c` |
-| OmniScript / IP Elements | `OmniProcessElement` | `vlocity_cmt__Element__c` | `vlocity_ins__Element__c` |
-| FlexCard | `OmniUiCard` | `vlocity_cmt__VlocityUITemplate__c` | `vlocity_ins__VlocityUITemplate__c` |
-| Data Mapper (DataRaptor) | `OmniDataTransform` | `vlocity_cmt__DRBundle__c` | `vlocity_ins__DRBundle__c` |
-| Data Mapper Item | `OmniDataTransformItem` | `vlocity_cmt__DRMapItem__c` | `vlocity_ins__DRMapItem__c` |
-| Calculation Matrix | `CalculationMatrix` | `vlocity_cmt__CalculationMatrix__c` | `vlocity_ins__CalculationMatrix__c` |
-| Calculation Procedure | `CalculationProcedure` | `vlocity_cmt__CalculationProcedure__c` | `vlocity_ins__CalculationProcedure__c` |
-
-### Relationship Fields (Element → Parent)
-
-| Concept | Core | vlocity_cmt | vlocity_ins |
-|---------|------|-------------|-------------|
-| Element → Process lookup | `OmniProcessId` | `vlocity_cmt__OmniScriptId__c` | `vlocity_ins__OmniScriptId__c` |
-| DM Item → DM lookup | `OmniDataTransformId` | `vlocity_cmt__DRBundleId__c` | `vlocity_ins__DRBundleId__c` |
-
----
-
-## Field Mapping
-
-### OmniProcess / OmniScript Fields
-
-| Concept | Core (OmniProcess) | vlocity_cmt (OmniScript__c) | vlocity_ins (OmniScript__c) |
-|---------|-------------------|---------------------------|---------------------------|
-| Type | `Type` | `vlocity_cmt__Type__c` | `vlocity_ins__Type__c` |
-| SubType | `SubType` | `vlocity_cmt__SubType__c` | `vlocity_ins__SubType__c` |
-| Language | `Language` | `vlocity_cmt__Language__c` | `vlocity_ins__Language__c` |
-| Is Active | `IsActive` | `vlocity_cmt__IsActive__c` | `vlocity_ins__IsActive__c` |
-| Version | `VersionNumber` | `vlocity_cmt__Version__c` | `vlocity_ins__Version__c` |
-| Type Category | `TypeCategory` | N/A (use `vlocity_cmt__IsIntegrationProcedure__c`) | N/A (use `vlocity_ins__IsIntegrationProcedure__c`) |
-| Custom HTML | `CustomHtmlTemplates` | `vlocity_cmt__CustomHtmlTemplates__c` | `vlocity_ins__CustomHtmlTemplates__c` |
-| Is Reusable | `IsReusable` | `vlocity_cmt__IsReusable__c` | `vlocity_ins__IsReusable__c` |
-| Procedure Key | N/A | `vlocity_cmt__ProcedureKey__c` | `vlocity_ins__ProcedureKey__c` |
-
-**Note on TypeCategory vs IsIntegrationProcedure**: In Core namespace, `TypeCategory` distinguishes OmniScripts from Integration Procedures (`'OmniScript'` vs `'IntegrationProcedure'`). In Vlocity namespaces, use the boolean field `IsIntegrationProcedure__c` instead.
-
-### Element Fields
-
-| Concept | Core (OmniProcessElement) | vlocity_cmt (Element__c) | vlocity_ins (Element__c) |
-|---------|--------------------------|-------------------------|-------------------------|
-| Name | `Name` | `Name` | `Name` |
-| Type | `Type` | `vlocity_cmt__Type__c` | `vlocity_ins__Type__c` |
-| Property Set Config | `PropertySetConfig` | `vlocity_cmt__PropertySet__c` | `vlocity_ins__PropertySet__c` |
-| Order | `SequenceNumber` | `vlocity_cmt__Order__c` | `vlocity_ins__Order__c` |
-| Is Active | `IsActive` | `vlocity_cmt__Active__c` | `vlocity_ins__Active__c` |
-| Parent Element | `ParentElementId` | `vlocity_cmt__ParentElementId__c` | `vlocity_ins__ParentElementId__c` |
-| Level | `Level` | `vlocity_cmt__Level__c` | `vlocity_ins__Level__c` |
-
-### FlexCard / UI Template Fields
-
-| Concept | Core (OmniUiCard) | vlocity_cmt (VlocityUITemplate__c) | vlocity_ins (VlocityUITemplate__c) |
-|---------|-------------------|-----------------------------------|-----------------------------------|
-| Name | `Name` | `Name` | `Name` |
-| Is Active | `IsActive` | `vlocity_cmt__IsActive__c` | `vlocity_ins__IsActive__c` |
-| Definition | `Definition` | `vlocity_cmt__Definition__c` | `vlocity_ins__Definition__c` |
-| Author Name | `AuthorName` | `vlocity_cmt__Author__c` | `vlocity_ins__Author__c` |
-| Version | `VersionNumber` | `vlocity_cmt__Version__c` | `vlocity_ins__Version__c` |
-| Template Type | N/A | `vlocity_cmt__TemplateType__c` | `vlocity_ins__TemplateType__c` |
-
-### Data Mapper / DataRaptor Fields
-
-| Concept | Core (OmniDataTransform) | vlocity_cmt (DRBundle__c) | vlocity_ins (DRBundle__c) |
-|---------|-------------------------|--------------------------|--------------------------|
-| Name | `Name` | `Name` | `Name` |
-| Type | `Type` | `vlocity_cmt__Type__c` | `vlocity_ins__Type__c` |
-| Is Active | `IsActive` | `vlocity_cmt__IsActive__c` | `vlocity_ins__IsActive__c` |
-| Input Type | `InputType` | `vlocity_cmt__InputType__c` | `vlocity_ins__InputType__c` |
-| Output Type | `OutputType` | `vlocity_cmt__OutputType__c` | `vlocity_ins__OutputType__c` |
-
-### Data Mapper Item Fields
-
-| Concept | Core (OmniDataTransformItem) | vlocity_cmt (DRMapItem__c) | vlocity_ins (DRMapItem__c) |
-|---------|------------------------------|---------------------------|---------------------------|
-| Input Object | `InputObjectName` | `vlocity_cmt__InterfaceObject__c` | `vlocity_ins__InterfaceObject__c` |
-| Output Object | `OutputObjectName` | `vlocity_cmt__TargetFieldObjectType__c` | `vlocity_ins__TargetFieldObjectType__c` |
-| Input Field | `InputFieldName` | `vlocity_cmt__InterfaceFieldAPIName__c` | `vlocity_ins__InterfaceFieldAPIName__c` |
-| Output Field | `OutputFieldName` | `vlocity_cmt__TargetFieldAPIName__c` | `vlocity_ins__TargetFieldAPIName__c` |
-| Filter Data Type | `FilterDataType` | `vlocity_cmt__FilterDataType__c` | `vlocity_ins__FilterDataType__c` |
-| Query Sequence | `InputObjectQuerySequence` | `vlocity_cmt__InterfaceObjectLookupOrder__c` | `vlocity_ins__InterfaceObjectLookupOrder__c` |
-
----
-
-## Metadata Type Names for Deployment
-
-When using `sf project retrieve start` or `sf project deploy start`, reference the correct metadata type:
-
-| Component | Core Metadata Type | Vlocity Metadata Type |
-|-----------|-------------------|----------------------|
-| OmniScript | `OmniScript` | N/A (use Vlocity Build Tool) |
-| Integration Procedure | `OmniIntegrationProcedure` | N/A (use Vlocity Build Tool) |
-| FlexCard | `OmniUiCard` | N/A (use Vlocity Build Tool) |
-| Data Mapper | `OmniDataTransform` | N/A (use Vlocity Build Tool) |
-| Data Mapper Item | `OmniDataTransformItem` | N/A (use Vlocity Build Tool) |
-
-**Note**: Only Core namespace components support standard Salesforce metadata API deployment. Vlocity namespace components require the Vlocity Build Tool (`vlocity_build`) for migration between orgs.
-
-### Retrieve Example (Core)
-```bash
-sf project retrieve start --metadata OmniScript --target-org myorg
-sf project retrieve start --metadata OmniDataTransform --target-org myorg
-```
-
----
-
-## Mixed Namespace Scenarios
-
-### During Core Migration
-
-Organizations migrating from a Vlocity namespace to Core may temporarily have components under both namespaces. During this transition:
-
-1. **Probe both namespaces** — if both return results, the org is mid-migration
-2. **Core components take precedence** — runtime uses Core namespace objects when both exist
-3. **Report the state** — alert the user that migration is in progress and both namespaces contain data
-4. **Do not modify Vlocity-namespace components** — they are frozen during migration
-
-### Detection of Mixed State
-
-```bash
-# Check if Core has components
-sf data query --query "SELECT COUNT() FROM OmniProcess" --target-org myorg --json 2>/dev/null
-
-# Also check if Vlocity still has components
-sf data query --query "SELECT COUNT() FROM vlocity_cmt__OmniScript__c" --target-org myorg --json 2>/dev/null
-```
-
-If both return `totalSize > 0`, the org is in a mixed namespace state.
-
-### Recommended Actions During Mixed State
-
-- Inventory components under both namespaces
-- Compare counts to assess migration progress
-- Flag components that exist only in the old namespace (not yet migrated)
-- Do not create components under the old namespace
-
----
-
-## Data Mapper Type Values
-
-The `Type` field on OmniDataTransform / DRBundle indicates the mapper's purpose:
-
-| Type Value | Description |
-|-----------|-------------|
-| `Extract` | Reads data from Salesforce objects |
-| `Transform` | Maps and transforms data between structures |
-| `Load` | Writes data to Salesforce objects |
-| `Turbo Extract` | High-performance read (bypasses sharing rules) |
-
----
-
-## SOQL Query Templates
-
-### Core Namespace — Full Inventory
-
-```soql
--- All OmniScripts
-SELECT Id, Type, SubType, Language, IsActive, VersionNumber, LastModifiedDate
-FROM OmniProcess
-WHERE TypeCategory = 'OmniScript'
-ORDER BY Type, SubType, Language, VersionNumber DESC
-
--- All Integration Procedures
-SELECT Id, Type, SubType, Language, IsActive, VersionNumber, LastModifiedDate
-FROM OmniProcess
-WHERE TypeCategory = 'IntegrationProcedure'
-ORDER BY Type, SubType, Language, VersionNumber DESC
-
--- All FlexCards
-SELECT Id, Name, IsActive, AuthorName, VersionNumber, LastModifiedDate
-FROM OmniUiCard
-ORDER BY Name, VersionNumber DESC
-
--- All Data Mappers
-SELECT Id, Name, Type, IsActive, InputType, OutputType, LastModifiedDate
-FROM OmniDataTransform
-ORDER BY Name
-```
-
-### vlocity_cmt Namespace — Full Inventory
-
-```soql
--- All OmniScripts
-SELECT Id, vlocity_cmt__Type__c, vlocity_cmt__SubType__c,
-       vlocity_cmt__Language__c, vlocity_cmt__IsActive__c, vlocity_cmt__Version__c
-FROM vlocity_cmt__OmniScript__c
-WHERE vlocity_cmt__IsIntegrationProcedure__c = false
-ORDER BY vlocity_cmt__Type__c, vlocity_cmt__SubType__c
-
--- All Integration Procedures
-SELECT Id, vlocity_cmt__Type__c, vlocity_cmt__SubType__c,
-       vlocity_cmt__Language__c, vlocity_cmt__IsActive__c, vlocity_cmt__Version__c
-FROM vlocity_cmt__OmniScript__c
-WHERE vlocity_cmt__IsIntegrationProcedure__c = true
-ORDER BY vlocity_cmt__Type__c, vlocity_cmt__SubType__c
-
--- All FlexCards / UI Templates
-SELECT Id, Name, vlocity_cmt__IsActive__c, vlocity_cmt__Version__c
-FROM vlocity_cmt__VlocityUITemplate__c
-ORDER BY Name
-
--- All Data Mappers (DataRaptors)
-SELECT Id, Name, vlocity_cmt__Type__c, vlocity_cmt__IsActive__c
-FROM vlocity_cmt__DRBundle__c
-ORDER BY Name
-```
-
-### vlocity_ins Namespace — Full Inventory
-
-```soql
--- All OmniScripts
-SELECT Id, vlocity_ins__Type__c, vlocity_ins__SubType__c,
-       vlocity_ins__Language__c, vlocity_ins__IsActive__c, vlocity_ins__Version__c
-FROM vlocity_ins__OmniScript__c
-WHERE vlocity_ins__IsIntegrationProcedure__c = false
-ORDER BY vlocity_ins__Type__c, vlocity_ins__SubType__c
-
--- All Integration Procedures
-SELECT Id, vlocity_ins__Type__c, vlocity_ins__SubType__c,
-       vlocity_ins__Language__c, vlocity_ins__IsActive__c, vlocity_ins__Version__c
-FROM vlocity_ins__OmniScript__c
-WHERE vlocity_ins__IsIntegrationProcedure__c = true
-ORDER BY vlocity_ins__Type__c, vlocity_ins__SubType__c
-
--- All FlexCards / UI Templates
-SELECT Id, Name, vlocity_ins__IsActive__c, vlocity_ins__Version__c
-FROM vlocity_ins__VlocityUITemplate__c
-ORDER BY Name
-
--- All Data Mappers (DataRaptors)
-SELECT Id, Name, vlocity_ins__Type__c, vlocity_ins__IsActive__c
-FROM vlocity_ins__DRBundle__c
-ORDER BY Name
-```

package/skills/applying-cms-brand/SKILL.md

@@ -1,170 +0,0 @@
----
-name: applying-cms-brand
-description: "Extracts, retrieves, and applies CMS brand guidelines (voice, tone, style, colors, typography) to generated content. Use this skill ANY TIME a user request involves branding, brand voice, brand tone, brand guidelines, brand identity, brand styling, or applying a brand to content. Triggers for requests like \"apply my brand\", \"use our brand voice\", \"match our brand guidelines\", \"find my brand\", \"search for brand\", \"get brand instructions\", \"apply brand tone\". Handles the full workflow: searching for brands in Salesforce CMS, extracting brand instructions, and applying brand voice/tone/guidelines to generated content. Does not apply to media/image search (use searching-media skill), logo search, or creating new brand definitions."
-compatibility: "Requires get_brand_instructions and/or search_brands MCP tools"
-metadata:
-  version: "1.0"
----
-
-# Applying CMS Brand
-
-Universal skill for searching, extracting, and applying CMS brand guidelines to generated content.
-
-## Scope
-
-**This skill is for APPLYING existing brand guidelines from Salesforce CMS to content you generate.**
-
-**Use this skill when the user wants to:**
-- Apply their brand voice/tone to generated content
-- Find and use brand guidelines stored in Salesforce CMS
-- Search for an existing brand in their org
-- Get brand instructions for content generation
-- Ensure generated content matches their brand identity
-- Apply brand styling, tone, or voice to a page, component, or app
-
-**DO NOT use this skill when the user wants to:**
-- Search for images or media (use searching-media skill)
-- Create a new brand from scratch
-- Edit brand definitions in CMS
-- Generate logos or visual brand assets
-
-## Before You Start
-
-**CRITICAL: You must retrieve brand instructions BEFORE generating or modifying any brand.**
-
-When a user requests branded content:
-
-1. **Search for available brands** (if brand is not already identified)
-2. **Extract brand instructions** for the selected brand
-3. **Apply brand guidelines** to all content you generate
-
-**Never generate content first and retrofit branding later.** Brand instructions must inform content generation from the start.
-
-## Workflow Overview
-
-Copy this checklist and track your progress:
-
-```
-CMS Branding Progress:
-- [ ] Step 1: Determine if brand is already identified or needs search
-- [ ] Step 2: Search for brands (if needed) and present options to user
-- [ ] Step 3: Extract brand instructions for the selected brand
-```
-
-## Step 1: Determine Brand Context
-
-Check if the user has already specified which brand to use:
-
-**Brand is known** (user named it, or only one brand exists):
-- Skip to Step 3 (Extract Brand Instructions)
-
-**Brand is unknown** (user says "apply my brand" without specifying which):
-- Proceed to Step 2 (Search for Brands)
-
-## Step 2: Search for Brands
-
-**Tool:** `search_brands`
-
-**Process:**
-
-1. **Determine search query** — Use the user's description, company name, or a general keyword
-2. **Build the request:**
-
-```json
-{
-  "inputs": [{
-    "searchQuery": "keyword or brand name"
-  }]
-}
-```
-
-3. **Call `search_brands`** with the query
-4. **Parse the response** — Extract brand results:
-   - `managedContentId` — Unique ID (use this for extraction in Step 3)
-   - `managedContentKey` — Content key identifier
-   - `title` — Brand display name
-   - `contentUrl` — URL to the brand content
-   - `totalResults` — Number of brands found
-
-### Presenting Brand Results
-
-**If multiple brands found**, use `ask_followup_question` to present options:
-
-```
-I found [N] brands in your CMS. Which one should I apply?
-
-1. [Brand Title 1]
-2. [Brand Title 2]
-3. [Brand Title 3]
-
-Which brand would you like to use?
-```
-
-**If one brand found**, confirm with the user:
-
-```
-I found the brand "[Brand Title]". Should I apply this brand's guidelines to the content?
-```
-
-**If no brands found:**
-
-```
-No brands found in Salesforce CMS. To use branding:
-1. Create a brand in Salesforce CMS (Content Type: sfdc_cms__brand)
-2. Provide brand guidelines directly in this conversation
-
-Would you like to proceed without CMS branding, or provide guidelines manually?
-```
-
-**Never auto-select a brand without confirmation.** Always wait for user choice.
-
-## Step 3: Extract Brand Instructions
-
-**Tool:** `get_brand_instructions`
-
-**Process:**
-
-1. **Call `get_brand_instructions`** — This retrieves the branding extraction prompt template
-2. **Parse the response:**
-   - `promptBody` — Contains the full brand instruction prompt with extraction and application rules
-
-3. **Follow the instructions in `promptBody`** — The prompt template contains specific guidance on:
-   - How to extract brand properties from the brand content
-   - Brand voice and tone rules
-   - Typography and color guidelines
-   - Content formatting rules
-   - Guardrails and restrictions
-
-### What Brand Instructions Contain
-
-The extracted brand instructions typically include:
-
-| Property | Description |
-|---|---|
-| Brand Voice | How the brand speaks (e.g., professional, friendly, authoritative) |
-| Brand Tone | Emotional quality of communication (e.g., confident, warm, empathetic) |
-| Key Messages | Core messaging pillars and value propositions |
-| Content Rules | Dos and don'ts for content generation |
-| Style Guidelines | Typography, color, spacing preferences |
-| Guardrails | Hard restrictions on language, topics, or claims |
-
-## Error Handling
-
-| Error | Response |
-|---|---|
-| `search_brands` unavailable | "Brand search is unavailable. Please provide your brand name or guidelines directly." |
-| `get_brand_instructions` unavailable | "Cannot retrieve brand instructions. Please share your brand guidelines in this conversation and I'll apply them manually." |
-| Org lacks Vibes branding | "CMS branding is not enabled for this org. Contact your admin to enable the Agentforce Vibes branding feature." |
-| Permission denied | "You don't have permission to access CMS brands. Ensure you have Managed Content Authoring permission." |
-| Brand extraction returns empty | "The brand exists but has no configured guidelines. Please add brand properties in CMS or provide guidelines here." |
-
-**Never silently fail.** Always inform the user and offer alternatives.
-
-## Key Principles
-
-1. **Brand first, content second** — Always extract brand instructions before generating content
-2. **Never assume brand guidelines** — Only apply what was explicitly retrieved from CMS
-3. **Respect guardrails absolutely** — Brand content rules are hard constraints, not suggestions
-4. **Confirm brand selection** — Never auto-select a brand without user confirmation
-5. **Show your work** — Tell the user which guidelines you applied and how
-6. **Graceful degradation** — If tools are unavailable, ask for manual guidelines rather than proceeding without branding