npm - @salesforce/afv-skills - Versions diffs - 1.41.0 → 1.43.0 - Mend

@salesforce/afv-skills 1.41.0 → 1.43.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (288) hide show

package/skills/data360-segment/README.md DELETED Viewed

@@ -1,35 +0,0 @@
-# data360-segment
-Audience and insight workflows for Salesforce Data Cloud.
-## Use this skill for
-- creating and publishing segments
-- managing calculated insights
-- checking segment counts
-- troubleshooting segment SQL
-- understanding why a segment is empty or unexpectedly large
-## Example requests
-```text
-"Create a high-value customer segment in Data Cloud"
-"Why is my segment returning zero members?"
-"Run this calculated insight and help me verify it"
-"Show me how to get member counts for this segment"
-```
-## Common commands
-```bash
-sf data360 segment list -o myorg 2>/dev/null
-sf data360 segment create -o myorg -f segment.json --api-version 64.0 2>/dev/null
-sf data360 segment publish -o myorg --name High_Value_Customers 2>/dev/null
-sf data360 calculated-insight list -o myorg 2>/dev/null
-```
-## References
-- [SKILL.md](SKILL.md)
-- [../data360-orchestrate/assets/definitions/calculated-insight.template.json](../data360-orchestrate/assets/definitions/calculated-insight.template.json)
-- [../data360-orchestrate/assets/definitions/segment.template.json](../data360-orchestrate/assets/definitions/segment.template.json)

package/skills/data360-segment/SKILL.md DELETED Viewed

@@ -1,123 +0,0 @@
----
-name: data360-segment
-description: "Salesforce Data Cloud Segment phase. Use this skill when the user creates or publishes segments, manages calculated insights, or troubleshoots audience SQL in Data Cloud. TRIGGER when: user creates or publishes segments, manages calculated insights, inspects segment counts or membership, or troubleshoots audience SQL in Data Cloud. DO NOT TRIGGER when: the task is DMO/mapping/identity-resolution work (use data360-harmonize), activation work (use data360-activate), query/search-index work (use data360-query), or Standard Data Model (STDM)/session tracing (use agentforce-observe)."
-metadata:
-  cliTools:
-    - tool: ["node"]
-      semver: ">=18.0.0"
-    - tool: ["sf"]
-      semver: ">=2.0.0"
-  relatedSkills:
-    - "agentforce-observe"
-    - "data360-activate"
-    - "data360-harmonize"
-    - "data360-orchestrate"
-    - "data360-query"
-  version: "1.0"
-  domains: ["Data 360"]
----
-# data360-segment: Data Cloud Segment Phase
-Use this skill when the user needs **audience and insight work**: segments, calculated insights, publish workflows, member counts, or troubleshooting Data Cloud segment SQL.
-## When This Skill Owns the Task
-Use `data360-segment` when the work involves:
-- `sf data360 segment *`
-- `sf data360 calculated-insight *`
-- segment publish workflows
-- member counts and segment troubleshooting
-- calculated insight execution and verification
-Delegate elsewhere when the user is:
-- still building Data Model Objects (DMOs), mappings, or identity resolution → [data360-harmonize](../data360-harmonize/SKILL.md)
-- activating a segment downstream → [data360-activate](../data360-activate/SKILL.md)
-- writing read-only SQL or search-index queries → [data360-query](../data360-query/SKILL.md)
----
-## Required Context to Gather First
-Ask for or infer:
-- target org alias
-- unified DMO (Data Model Object) or base entity name
-- whether the user wants create, publish, inspect, or troubleshoot
-- whether the asset is a segment or calculated insight
-- expected success metric: member count, aggregate value, or publish status
----
-## Core Operating Rules
-- Treat Data Cloud segment SQL as distinct from CRM SOQL.
-- Run the shared readiness classifier from the `data360-orchestrate` skill before mutating audience assets: `node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase segment --json`.
-- Prefer reusable JSON definitions for repeatable segment and CI creation.
-- Use `--api-version 64.0` when segment creation behavior is unstable on newer defaults.
-- Verify with counts or SQL after publish/run steps instead of assuming success.
-- Use SQL joins rather than `segment members` when readable member details are needed.
----
-## Recommended Workflow
-### 1. Classify readiness for segment work
-```bash
-node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase segment --json
-```
-### 2. Inspect current state
-```bash
-sf data360 segment list -o <org> 2>/dev/null
-sf data360 calculated-insight list -o <org> 2>/dev/null
-```
-### 3. Create with reusable JSON definitions
-```bash
-sf data360 segment create -o <org> -f segment.json --api-version 64.0 2>/dev/null
-sf data360 calculated-insight create -o <org> -f ci.json 2>/dev/null
-```
-### 4. Publish or run explicitly
-```bash
-sf data360 segment publish -o <org> --name My_Segment 2>/dev/null
-sf data360 calculated-insight run -o <org> --name Lifetime_Value 2>/dev/null
-```
-### 5. Verify with counts or SQL
-```bash
-sf data360 segment count -o <org> --name My_Segment 2>/dev/null
-sf data360 query sql -o <org> --sql 'SELECT COUNT(*) FROM "UnifiedssotIndividualMain__dlm"' 2>/dev/null
-```
----
-## High-Signal Gotchas
-- Segment creation can require `--api-version 64.0`.
-- `segment members` returns opaque IDs; use SQL joins when human-readable member details are needed.
-- Segment SQL is not SOQL.
-- Calculated insight assets and segment SQL have different limitations.
-- Publish/run steps may kick off asynchronous work even when the command returns quickly.
-- An empty segment or calculated-insight list usually means the module is reachable but unconfigured, not unavailable.
----
-## Output Format
-```text
-Segment task: <segment / calculated-insight>
-Action: <create / publish / inspect / troubleshoot>
-Target org: <alias>
-Artifacts: <definition files / commands>
-Verification: <member count / query result / publish state>
-Next step: <act / retrieve / follow-up>
-```
----
-## References
-- [../data360-orchestrate/assets/definitions/calculated-insight.template.json](../data360-orchestrate/assets/definitions/calculated-insight.template.json)
-- [../data360-orchestrate/assets/definitions/segment.template.json](../data360-orchestrate/assets/definitions/segment.template.json)
-- [../data360-orchestrate/references/feature-readiness.md](../data360-orchestrate/references/feature-readiness.md)

package/skills/service-helpagent-coordinate/references/channel-help-portal.md DELETED Viewed

@@ -1,22 +0,0 @@
-# Channel branch — Help Portal *(Coming soon)*
-> **When to read this file.** Load it only if the user selected **Help Portal** at Checkpoint 3.
-## This is a hard stop, not an aspirational selection
-Help Portal is **not yet supported.** DO NOT attempt to build anything for this channel. Do not create supporting objects, records, or metadata "toward" the feature — standing up a portal site or wiring routing for it is out of scope and requires a dedicated skill that does not exist yet. Trying to fulfill it by creating adjacent objects produces broken half-configurations that look done but never work.
-Respond to the user verbatim:
-> *"This feature is coming soon, please select Web Chat."*
-Then re-present the channel selection (Web Chat / Help Portal / Voice) and wait for a supported choice. Do not proceed until the user picks Web Chat.
-## Intended future shape (for reference only — do not build)
-When the channel ships, it will ask the user for:
-- **Site Name / Domain Name**
-- **Logo image** (png, svg, or jpg — a file name or path)
-- **Brand colors (RGB)**: Action color, Link color, Border color, Background color, Text color
-…then use `experience-lwr-site-generate` to build the Experience Cloud site with the supplied branding and embed the agent on it. This is documented so the eventual implementation has a target; it is **not** a licence to build it now.