@salesforce/afv-skills 1.62.0 → 1.64.0

package/skills/service-omni-routing-flow-deploy/SKILL.md

@@ -13,9 +13,7 @@ metadata:
     - "service-omni-queue-deploy"
     - "service-omni-queue-routing-config-deploy"
     - "service-omni-service-channel-configure"
-  accessCheck:
-    - type: license
-      value: ServiceCloud
+  accessCheck: "OrgPermissions.LightningService"
   cliTools:
     - tool: ["jq"]
       semver: ">=1.6"

package/skills/service-omni-service-channel-configure/SKILL.md

@@ -8,9 +8,7 @@ metadata:
   minApiVersion: "66.0"
   relatedSkills:
     - "service-omni-base-settings-configure"
-  accessCheck:
-    - type: license
-      value: ServiceCloud
+  accessCheck: "OrgPermissions.LightningService"
   cliTools:
     - tool: ["jq"]
       semver: ">=1.6"

package/skills/service-omni-sidebar-configure/SKILL.md

@@ -9,9 +9,7 @@ metadata:
   relatedSkills:
     - "service-omni-base-settings-configure"
     - "service-omni-channel-setup-coordinate"
-  accessCheck:
-    - type: license
-      value: ServiceCloud
+  accessCheck: "OrgPermissions.LightningService"
   cliTools:
     - tool: ["jq"]
       semver: ">=1.6"

package/skills/service-omni-skills-based-routing-configure/SKILL.md

@@ -9,9 +9,7 @@ metadata:
   relatedSkills:
     - "service-omni-agent-users-create"
     - "service-omni-base-settings-configure"
-  accessCheck:
-    - type: license
-      value: ServiceCloud
+  accessCheck: "OrgPermissions.LightningService"
   cliTools:
     - tool: ["jq"]
       semver: ">=1.6"

package/skills/service-omni-supervisor-config-deploy/SKILL.md

@@ -15,9 +15,7 @@ metadata:
     - "service-omni-service-channel-configure"
     - "service-omni-supervisor-permset-assign"
     - "service-omni-supervisor-surface-deploy"
-  accessCheck:
-    - type: license
-      value: ServiceCloud
+  accessCheck: "OrgPermissions.LightningService"
   cliTools:
     - tool: ["jq"]
       semver: ">=1.6"

package/skills/service-omni-supervisor-permset-assign/SKILL.md

@@ -8,9 +8,7 @@ metadata:
   minApiVersion: "66.0"
   relatedSkills:
     - "service-omni-supervisor-config-deploy"
-  accessCheck:
-    - type: license
-      value: ServiceCloud
+  accessCheck: "OrgPermissions.LightningService"
   cliTools:
     - tool: ["jq"]
       semver: ">=1.6"

package/skills/service-omni-supervisor-surface-deploy/SKILL.md

@@ -10,9 +10,7 @@ metadata:
     - "service-omni-command-center-analyze"
     - "service-omni-supervisor-config-deploy"
     - "service-omni-supervisor-permset-assign"
-  accessCheck:
-    - type: license
-      value: ServiceCloud
+  accessCheck: "OrgPermissions.LightningService"
   cliTools:
     - tool: ["jq"]
       semver: ">=1.6"

package/skills/service-omni-supervisor-users-create/SKILL.md

@@ -10,9 +10,7 @@ metadata:
     - "service-omni-agent-users-create"
     - "service-omni-supervisor-config-deploy"
     - "service-omni-supervisor-permset-assign"
-  accessCheck:
-    - type: license
-      value: ServiceCloud
+  accessCheck: "OrgPermissions.LightningService"
   cliTools:
     - tool: ["jq"]
       semver: ">=1.6"

package/skills/service-omni-work-skill-routing-configure/SKILL.md

@@ -10,9 +10,7 @@ metadata:
     - "service-omni-base-settings-configure"
     - "service-omni-channel-setup-coordinate"
     - "service-omni-skills-based-routing-configure"
-  accessCheck:
-    - type: license
-      value: ServiceCloud
+  accessCheck: "OrgPermissions.LightningService"
   cliTools:
     - tool: ["jq"]
       semver: ">=1.6"

package/skills/field-service-setup-orchestrator-get/SKILL.md

@@ -1,47 +0,0 @@
----
-name: field-service-setup-orchestrator-get
-description: "Use this skill to set up Salesforce Field Service — Work Types, Skills, Service Territories, Operating Hours, Scheduling Policy, Work Rules, Service Objectives, Data Capture Forms, FSL mobile forms, Pre-Work Brief, Mobile Branding, or any FSL setup, enablement, or configuration request. Entry point that identifies what the user wants to configure and routes to the right sub-workflow: Foundation Setup, Scheduling Policy, Data Capture Forms, Pre-Work Brief, or Mobile Branding."
-owning_team: sfs-setup-experience
-metadata:
-  version: "1.0"
-  domains: ["Field Service"]
----
-
-## How It Works
-
-This skill is the entry point for all Field Service setup. It identifies what the user wants to configure and routes to the correct sub-skill. It does not perform setup work itself.
-
-## Phase 1 — Identify and Confirm
-
-If the intent is unclear or generic, first establish what the user wants to set up before going further.
-
-Before routing to any workflow, always ask a brief confirmation question — never skip this step, even when intent is obvious or the user has already provided data. Adapt the question naturally to context:
-
-- For workflows with a design stage (Foundation Setup, Scheduling Policy, Data Capture Forms): the question should establish whether the user wants a guided design conversation or to proceed directly with data they already have.
-- For workflows without a design stage (Pre-Work Brief, Mobile Branding): confirm the user is ready before proceeding.
-
-One short question. Wait for the answer before delegating.
-
-## Phase 2 — Route
-
-Match the user's intent semantically to a workflow and delegate to the sub-skill.
-
-| Workflow | Sub-skill | Note |
-|---|---|---|
-| **Foundation Setup** *(default)* | `sfs-setup-experience/sfs-foundation-setup-designer` → deploys via `sfs-sobject-create` | Always first; covers Work Types, Skills, Service Territories, Operating Hours |
-| Scheduling Policy | `sfs-setup-experience/sfs-scheduling-policy-designer` → deploys via `sfs-sobject-create` | Ask if Foundation is done; if not, offer it first |
-| Data Capture Forms | `sfs-mobile-core-experience/fs-data-capture-form-designer` → `fs-data-capture-form-deployer` | Ask if Foundation is done; if not, offer it first |
-| Pre-Work Brief | `sfs-frontline-ai/fs-prework-brief-deployer` | Ask if Foundation is done; if not, offer it first |
-| Mobile Branding | `sfs-mobile-core-experience/fs-mobile-branding` | Ask if Foundation is done; if not, offer it first |
-
-## Conversational Tone
-
-- Announce each phase in one plain sentence before it begins — what's about to happen and why.
-- Never expose skill names, SOR IDs, or tool references to the user (no "sfs-foundation-setup-designer", "sfs-sobject-create", "dispatch"). Use plain labels: "Foundation Setup", "design interview", "creating your records".
-
-## Key Principles
-
-- This skill routes — it never does setup work itself.
-- One workflow at a time; wait for explicit confirmation before the next.
-- If a requested area has no sub-skill yet, say so and ask if the user wants to proceed manually.
-- Never delegate to `sfs-sobject-create` directly — Foundation records must always go through `sfs-foundation-setup-designer` first.

package/skills/tableau-next-asset-create/README.md

@@ -1,65 +0,0 @@
-# tableau-next-asset-create
-
-A skill for building **Tableau Next semantic models that actually return data**
-via a `tableau-next-*` MCP server, then enriching, querying, and visualizing
-them.
-
-## What it does
-
-Routes an agent through the full authoring workflow: ingest CSVs to DLO/DMO,
-discover and row-gate sources, join the semantic data model (SDM), add
-calculated fields and metrics, run semantic queries, and build visualizations
-and dashboards. It encodes the failure modes that produce **empty or
-confidently-wrong dashboards** in Tableau Next — building on zero-row source
-objects, leaving objects unjoined, inventing field apiNames instead of reading
-them back, and shipping a populated-but-wrong model (an ID summed as a measure,
-a snapshot inflated by its date count).
-
-Trigger it for "analyze this CSV", "analyze account engagement", "build a
-dashboard from these extracts" — whenever the user wants insight from data that
-**isn't modeled yet** — and also for unnamed counts/totals ("how many orders…
-from existing Tableau Next data") and for designing the dashboard
-narrative/layout *before* charting. Plain counts, totals, and scalars against
-existing Tableau Next data go to `run_semantic_query` (the model need not be
-named). Interpreted breakdowns, rankings, trends, and comparisons go to
-`analyze_data`. Not for debugging a broken MCP server, writing application
-code, or reviewing someone else's existing dashboard without changing it.
-
-## Structure
-
-```text
-SKILL.md                     # thin router: G1 precondition + intent→guide table + no-dispatch rule
-references/
-  shared-gates.md            # single source of truth for the overlapping guardrails (G1–G8)
-  tasks/                     # thin task guides — one per capability; each opens with its gate header
-    build-end-to-end.md      # greenfield: build model + dashboard from scratch (Step 0→11)
-    ingest-flat-file.md      # ingest CSV → DLO → DMO
-    profile-dataset.md       # read-only: profile / discover / verify / triage empty
-    edit-sdm.md              # add a RAW object / dimension / measure / join / logical view
-    enrich-model.md          # add a CALCULATED dimension / measure / metric
-    ai-readiness-audit.md    # backfill readiness metadata / validate a model
-    query-model.md           # run_semantic_query for figures (model need not be named)
-    analyze-data.md          # interpreted breakdown / ranking / trend / comparison
-    create-viz.md            # create a single visualization
-    edit-viz.md              # edit an EXISTING visualization / persist via update_visualization
-    build-dashboard.md       # design / create / update a dashboard, add widgets/filters
-  # deep references (verified payloads + tool shapes) — cited BY the task guides:
-  build-workflow.md          # full numbered-step procedural spine with verified payloads
-  large-flat-file-handling.md
-  data-understanding.md
-  sdm-tool-reference.md
-  empty-source-handling.md
-  semantic-query-and-enrichment.md
-  ingest-and-metric-gotchas.md
-  viz-authoring.md
-  edit-visualization.md
-  dashboard-authoring.md
-  dashboard-design-principles.md
-  ai-readiness.md
-```
-
-The router asserts **G1** (a Tableau Next MCP server must be connected) once,
-then dispatches an intent to a task guide. Each guide's header names the gates
-it must assert (from `shared-gates.md`) before any tool call, then points *down*
-to a deep reference for the verified payload. The overlapping guardrails live
-in exactly one place (`shared-gates.md`).