@salesforce/afv-skills 1.56.0 → 1.58.0

package/skills/platform-apex-test-generate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-apex-test-generate
-description: "Generate and validate Apex test classes with TestDataFactory patterns, bulk testing (251+ records), mocking strategies, assertion best practices, and disciplined test-fix loops. Use this skill when creating new Apex test classes, improving test coverage, debugging and fixing failing Apex tests, running test execution and coverage analysis, or implementing testing patterns for triggers, services, controllers, batch jobs, queueables, and integrations. Triggers on *Test.cls, *_Test.cls files, sf apex run test workflows, coverage reports, test-fix loops. Do NOT trigger for production Apex code (use platform-apex-generate) or Jest/LWC tests."
+description: "Use to generate and validate Apex test classes with TestDataFactory patterns, bulk testing (251+ records), mocking, assertions, and disciplined test-fix loops. Use when creating Apex test classes (for triggers, services, controllers, batch jobs, queueables, and callouts), improving coverage, debugging or fixing failing Apex tests, or running test/coverage analysis. Triggers on *Test.cls files, sf apex run test, coverage reports. Do NOT trigger for production Apex (use platform-apex-generate) or Jest/LWC tests."
 metadata:
   version: "1.1"
   domains: ["Platform"]

package/skills/platform-apex-test-run/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-apex-test-run
-description: "Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. Use when the user needs to run Apex tests, check code coverage, fix failing tests, or work with *Test.cls / *_Test.cls files. TRIGGER when: user runs Apex tests, checks code coverage, fixes failing tests, or touches *Test.cls / *_Test.cls files. DO NOT TRIGGER when: writing Apex production code (use platform-apex-generate), Agentforce agent testing (use agentforce-test), or Jest/LWC tests (use experience-lwc-generate)."
+description: "Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. Use when the user runs Apex tests, checks code coverage, fixes failing tests, or touches *Test.cls / *_Test.cls files. DO NOT TRIGGER when writing Apex production code (use platform-apex-generate), Agentforce agent testing (use agentforce-test), or Jest/LWC tests (use experience-lwc-generate)."
 metadata:
   version: "1.2"
   domains: ["Platform"]

package/skills/platform-custom-field-generate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-custom-field-generate
-description: "Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from a field, or scoping/limiting picklist values for a specific record type. Also use when users encounter field deployment errors, especially around Roll-up Summary format, Master-Detail constraints, formula issues, or a record type that won't deploy without a business process. Use this skill for custom field metadata work, field generation, and field troubleshooting. DO NOT TRIGGER for creating or customizing the value set itself — defining a new GlobalValueSet, or modifying a StandardValueSet catalog like Industry or Lead Source — use platform-value-set-generate instead; this skill covers the field that references a value set, not the value set definition."
+description: "Use when users create, generate, or validate Salesforce Custom Field metadata. Trigger on custom fields, field types, Roll-Up Summary, Master-Detail/Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from a field, or scoping picklist values per record type; also field deployment errors, including a record type that won't deploy without a business process. DO NOT TRIGGER for creating/customizing the value set itself — a new GlobalValueSet or a StandardValueSet catalog like Industry — use platform-value-set-generate; this skill covers the field that references a value set, not the value set definition."
 metadata:
   version: "1.0"
   domains: ["Platform"]

package/skills/platform-custom-lightning-type-generate/SKILL.md

@@ -178,4 +178,4 @@ When you need the full list of supported primitive `lightning:type` identifiers,
 - [ ] Layout configurations use `lightning/propertyLayout` with ONLY the `property` attribute (no `label`, `title`, or other attributes)
 - [ ] All attribute mappings (`{!$attrs.propertyName}`) reference properties that exist in the type schema
 - [ ] Custom LWC components have correct targets in `-meta.xml`: `lightning__AgentforceInput` for editors, `lightning__AgentforceOutput` for renderers
-- [ ] Root schema does NOT include `"$schema"` field
+- [ ] Root schema does NOT include `"$schema"` field

package/skills/platform-custom-metadata-type-generate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-custom-metadata-type-generate
-description: "Use this skill when users need to create, generate, or validate Salesforce Custom Metadata Type metadata — the __mdt object, its fields, and its deployable records. Trigger when users mention custom metadata types, CMDT, __mdt objects, custom metadata records, .md-meta.xml files, or reference/config data that must ship between orgs. Also trigger for admin-maintained mapping, lookup, or crosswalk tables and field mappings (\"map fields from A to B\", code lookups) — config admins change without a code deploy belongs in a CMDT, never hardcoded in Apex or Flow — and when troubleshooting CMDT record/type deploy errors. DO NOT TRIGGER for Custom Settings — route to platform-custom-setting-generate; for regular custom objects holding business records — use platform-custom-object-generate; or for secrets and API keys — recommend a Named Credential, which this skill never generates."
+description: "Use to create, generate, or validate Salesforce Custom Metadata Type metadata — the __mdt object, fields, and deployable records. Trigger on custom metadata types, CMDT, __mdt objects, .md-meta.xml files, or cross-org reference/config data; also admin-maintained mapping/lookup/crosswalk tables (config that changes without a deploy belongs in a CMDT, never hardcoded in Apex/Flow), and CMDT deploy errors. DO NOT TRIGGER for Custom Settings (use platform-custom-setting-generate), business-record objects (use platform-custom-object-generate), or secrets/API keys (use a Named Credential)."
 metadata:
   version: "1.0"
   minApiVersion: "60.0"

package/skills/platform-custom-object-generate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-custom-object-generate
-description: "Use this skill when users need to create, generate, or validate Salesforce Custom Object metadata. Trigger when users mention custom objects, creating objects, object metadata, .object files, sharing models, name fields, or validation rules on objects. Also use when users say things like \"create a custom object\", \"generate object metadata\", \"set up an object for...\", or when they're troubleshooting object deployment errors especially around sharing models and Master-Detail relationships. Always use this skill for any custom object metadata work, including enriching and keeping the object's description current whenever its fields or validation rules change. Do NOT use this skill for non-Custom-Object metadata (Apex, Flows, LWC, Permission Sets, Custom Metadata Types) or for standard Salesforce objects."
+description: "Use when users create, generate, or validate Salesforce Custom Object metadata. Trigger on custom objects, .object files, sharing models, name fields, or validation rules — e.g. \"create a custom object\" — and deployment errors around sharing models and Master-Detail relationships. Also keep the object's <description> current when its fields or validation rules change. Do NOT use for non-Custom-Object metadata (Apex, Flows, LWC, Permission Sets, Custom Metadata Types) or standard objects."
 metadata:
   version: "1.1"
   domains: ["Platform"]

package/skills/platform-custom-report-type-generate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-custom-report-type-generate
-description: "Use this skill when users need to create, generate, or validate Salesforce Custom Report Type metadata. Trigger when users mention custom report types, report types, CRTs, reporting frameworks, cross-object reports, report builder data sources, or ask to expose fields for reporting across related objects. Also use when users mention primary and related objects for reports, inner vs outer joins in reports, report type categories, or encounter deployment errors for .reportType-meta.xml files. Do NOT trigger for: running, editing, or filtering existing reports; creating report folders, dashboards, or list views; or general reporting questions that don't involve authoring a .reportType-meta.xml file."
+description: "Use to create, generate, or validate Salesforce Custom Report Type metadata. Trigger on custom report types, CRTs, cross-object reports, report builder data sources, exposing fields for reporting across related objects, inner vs outer joins in reports, report type categories, or deployment errors for .reportType-meta.xml files. Do NOT trigger for running, editing, or filtering existing reports; creating report folders, dashboards, or list views; or non-authoring reporting questions."
 metadata:
   version: "1.0"
   domains: ["Platform"]

package/skills/platform-custom-setting-generate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-custom-setting-generate
-description: "Use this skill when users need to create, generate, or validate Salesforce Custom Setting metadata. Trigger when users mention custom settings (hierarchy or list), customSettingsType, SetupOwnerId, per-profile/per-user config overrides, feature flags, feature toggles, kill switches, or on/off switches admins flip to enable/disable behavior, e.g. bypass triggers/automation during a data load. Also use for \"create a custom setting\" or errors like \"Cannot specify: pluralLabel for CustomSettings\" or a setting that silently deployed as a regular custom object. A trigger bypass or kill switch is just a checkbox on a hierarchy custom setting — generate ONLY the setting, never an Apex trigger/handler. DO NOT TRIGGER for Custom Metadata Types or __mdt objects — route to platform-custom-metadata-type-generate; for business-record objects — use platform-custom-object-generate; for secrets, API keys, passwords, or tokens — recommend a Named Credential, never generated here."
+description: "Use to create, generate, or validate Salesforce Custom Setting metadata. Trigger on custom settings (hierarchy/list), customSettingsType, SetupOwnerId, per-profile/per-user config overrides, feature flags/toggles, kill switches, or admin on/off switches (e.g. bypass triggers during a data load); also \"create a custom setting\" or a setting that silently deployed as a regular object. A kill switch is just a checkbox on a hierarchy setting — generate ONLY the setting, never an Apex trigger/handler. DO NOT TRIGGER for Custom Metadata Types (use platform-custom-metadata-type-generate), business-record objects (use platform-custom-object-generate), or secrets/tokens (use a Named Credential)."
 metadata:
   version: "1.0"
   minApiVersion: "60.0"

package/skills/platform-data-and-tooling-api-context-get/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-data-and-tooling-api-context-get
-description: "Authoritative field/schema reference for 2130 STANDARD Salesforce objects — use to look up standard sObject and Tooling field API names, types, properties (filterable/sortable/groupable/updateable), and relationship names for Account, Contact, Opportunity, Lead, Case, ApexClass, ApexCodeCoverage, TraceFlag, and more. Load this alongside a SOQL/query/Apex skill when the field names, types, or Filter/Sort/Group capabilities are unverified — not when the fields are already known and only query syntax or optimization is needed. TRIGGER when verifying, validating, or debugging fields in a SOQL/SOSL query or DML against a standard object — capabilities, relationship/subquery paths, or what fields an object has — so the query runs instead of guessing. Custom __c objects and __c fields are NOT in these assets; describe the live org for those (sf sobject describe). DO NOT TRIGGER for authoring/deploying *-meta.xml or sfdx source (use the Metadata API skill)."
+description: "Authoritative field/schema reference for 2130 STANDARD Salesforce objects — sObject and Tooling field API names, types, properties (filterable/sortable/groupable/updateable), and relationships for Account, Contact, Opportunity, Lead, Case, ApexClass, and more. Load alongside a SOQL/Apex skill when fields/types/capabilities are unverified — not for query syntax or optimization alone. TRIGGER when verifying/debugging fields in a SOQL/SOSL query or DML against a standard object. Custom __c objects/fields are NOT covered — describe the live org (sf sobject describe). DO NOT TRIGGER for authoring/deploying *-meta.xml or sfdx source (use the Metadata API skill)."
 metadata:
   version: "1.0"
   domains: ["Platform"]

package/skills/platform-data-manage/SKILL.md

@@ -1,14 +1,9 @@
 ---
 name: platform-data-manage
-description: "Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use platform-soql-query), Apex test execution (use platform-apex-test-run), or metadata deployment (use platform-metadata-deploy)."
+description: "Salesforce data operations with 130-point scoring. Use to create, update, delete, bulk import/export, generate test data, and clean up org records via sf CLI and anonymous Apex. TRIGGER on creating test data, bulk import/export, sf data CLI commands, data-factory patterns for Apex tests, or seeding/cleaning org records. DO NOT TRIGGER for SOQL query writing only (use platform-soql-query), Apex test execution (use platform-apex-test-run), or metadata deployment (use platform-metadata-deploy)."
 metadata:
-  cliTools:
-    - tool: ["jq"]
-      semver: ">=1.6.0"
-    - tool: ["python3"]
-      semver: ">=3.8.0"
-    - tool: ["sf"]
-      semver: ">=2.0.0"
+  version: "1.1"
+  domains: ["Platform"]
   relatedSkills:
     - "automation-flow-generate"
     - "platform-apex-generate"
@@ -17,8 +12,13 @@ metadata:
     - "platform-custom-object-generate"
     - "platform-metadata-deploy"
     - "platform-soql-query"
-  version: "1.1"
-  domains: ["Platform"]
+  cliTools:
+    - tool: ["sf"]
+      semver: ">=2.0.0"
+    - tool: ["jq"]
+      semver: ">=1.6.0"
+    - tool: ["python3"]
+      semver: ">=3.8.0"
 ---
 
 # Salesforce Data Operations Expert (platform-data-manage)

package/skills/platform-flexipage-generate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-flexipage-generate
-description: "Use this skill when users need to create, generate, modify, or validate Salesforce Lightning pages (FlexiPages). Trigger when users mention RecordPage, AppPage, HomePage, Lightning pages, page layouts, adding components to pages, or page customization. Also use when users say things like 'create a Lightning page', 'add a component to a page', 'customize the record page', 'generate a FlexiPage', or when they're working with FlexiPage XML files and need help with components, regions, or deployment errors. Always use this skill for any FlexiPage-related work, even if they just mention 'page' in the context of Salesforce. DO NOT TRIGGER when users ask about Visualforce pages, Aura components without FlexiPage context, page layout assignments in the UI, or Lightning Web Component development that does not involve placing components on a FlexiPage."
+description: "Use when users create, generate, modify, or validate Salesforce Lightning pages (FlexiPages). Trigger on RecordPage, AppPage, HomePage, Lightning pages, adding components to a page, page customization (e.g. 'customize the record page'), or .flexipage-meta.xml files (regions, components, deployment errors). DO NOT TRIGGER for Visualforce pages, page layout assignments in the UI, UI Bundle/Experience Cloud site pages, or Aura/Lightning Web Component development without FlexiPage context."
 allowed-tools: Bash Read Write
 metadata:
   version: "1.1"

package/skills/platform-lightning-app-coordinate/SKILL.md

@@ -438,4 +438,4 @@ Check for:
 - Reserved words in API names
 - Relationship limits (max 2 M-D per object)
 - Name length limits
-- Duplicate names
+- Duplicate names

package/skills/platform-metadata-api-context-get/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-metadata-api-context-get
-description: "REQUIRED companion for Salesforce metadata generation — load this schema/API-context skill in the SAME turn as ANY metadata generation skill; if you load a generator, you ALSO load this. Use it whenever you create, generate, add, edit, or author metadata or a *-meta.xml file: custom object, custom field, formula field, picklist, lookup, master-detail, validation rule, permission set, profile, custom tab, lightning record page, flexipage, list view, custom application, flow, layout, record type, sharing rules, report, and 604 Metadata API types. It provides the authoritative schema, fields, field properties, required flags, allowed enum values, and XML structure so generated *-meta.xml deploys cleanly — skipping it causes hallucinated element names and deploy failures. Trigger on *-meta.xml, metadata schema, api context, 'Salesforce metadata', or 'sfdx project'. DO NOT use for SOQL, DML, runtime sObject access, or Tooling API records."
+description: "REQUIRED companion for Salesforce metadata generation — load this schema/API-context skill in the SAME turn as ANY metadata generator (if you load a generator, you ALSO load this). Use whenever you create, generate, edit, or author metadata or a *-meta.xml file (custom object, field, flow, and 604 Metadata API types): it gives authoritative schema, required flags, and XML structure so files deploy cleanly. Trigger on *-meta.xml, metadata schema, api context. DO NOT use for SOQL, DML, runtime sObject access, or Tooling API records."
 metadata:
   version: "1.0"
   domains: ["Platform"]

package/skills/platform-metadata-retrieve/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-metadata-retrieve
-description: "ALWAYS USE THIS SKILL to retrieve metadata from an org to your local project using the sf project retrieve start command. Supports multiple retrieval modes: retrieve all remote changes, retrieve by source directory, retrieve by metadata type with wildcards, retrieve by manifest (package.xml), or retrieve by package name. Use when the user asks to retrieve, pull, sync, or download metadata, Apex classes, custom objects, or org changes. Supports source format (default) or metadata format (ZIP). DO NOT TRIGGER for deploying metadata (use platform-metadata-deploy skill), listing metadata, or generating package.xml. NEVER use MCP tools - always use this skill and the Bash tool with sf project retrieve start."
+description: "ALWAYS USE THIS SKILL to retrieve metadata from an org to your local project with sf project retrieve start. Supports retrieval by all changes, source directory, metadata type (wildcards), manifest (package.xml), or package name, in source or metadata (ZIP) format. Use when the user asks to retrieve, pull, sync, or download metadata, Apex classes, or custom objects. DO NOT TRIGGER for deploying metadata (use platform-metadata-deploy), listing metadata, or generating a package.xml (use platform-manifest-generate). NEVER use MCP tools."
 metadata:
   version: "1.0"
   domains: ["Platform", "Developer Experience"]

package/skills/platform-permission-set-generate/SKILL.md

@@ -186,4 +186,4 @@ Before deploying, verify:
 
 ## Deployment
 
-Deploy using Salesforce CLI
+Deploy using Salesforce CLI

package/skills/platform-report-generate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-report-generate
-description: "Use this skill when users need to create, generate, or validate Salesforce Lightning Report metadata. Trigger when users mention reports, creating reports, report metadata, .report-meta.xml files, tabular reports, summary reports, matrix reports, joined reports, report columns, report groupings, report filters, report charts, cross-filters, bucket fields, report formulas, or report time frame filters. Also use when users say things like 'create a report', 'generate a report', 'build a report on Accounts', 'add a chart to my report', or when they encounter deployment errors for .report-meta.xml files. Do NOT trigger for: creating or modifying Custom Report Type metadata (.reportType-meta.xml — use platform-custom-report-type-generate), creating dashboards, creating list views, running or viewing existing reports in the UI, or SOQL queries."
+description: "Use when users create, generate, or validate Salesforce Lightning Report metadata (.report-meta.xml) — tabular, summary, matrix, or joined reports with columns, groupings, filters, charts, cross-filters, buckets, formulas, or time-frame filters. Triggers on \"create a report\", \"build a report\", \"add a chart\", or .report-meta.xml deploy errors. Do NOT trigger for Custom Report Type metadata (use platform-custom-report-type-generate), dashboards, list views, running reports in the UI, or SOQL."
 metadata:
   version: "1.0"
   domains: ["Platform"]

package/skills/platform-salesforce-connect-adapter-generate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-salesforce-connect-adapter-generate
-description: "Custom Apex adapter generation for Salesforce Connect — connects any external REST API to Salesforce as live, queryable External Objects without ETL or data copying. TRIGGER when: user wants to connect a non-standard external API to Salesforce, asks to write a DataSource.Provider or DataSource.Connection, wants to surface external data as Salesforce records, says \"connect my API to Salesforce without copying data\", or asks whether custom Apex is the right approach for any system. Also trigger on: \"custom adapter\", \"ExternalId field\", \"DataSource namespace\". DO NOT TRIGGER when: user is configuring a standard adapter they already have and is NOT asking about custom Apex (e.g., OData endpoint setup, Snowflake connector config). DO NOT TRIGGER when: user wants to copy or bulk-sync data — use platform-data-manage. DO NOT TRIGGER for Apex callouts outside Connect — use platform-apex-generate or integration-connectivity-generate."
+description: "Custom Apex adapter generation for Salesforce Connect — connects any external REST API to Salesforce as live, queryable External Objects without ETL or copying. TRIGGER when: connecting a non-standard external API, writing a DataSource.Provider/Connection or a `.cls`/`.cls-meta.xml` custom adapter class, adding a `.namedCredential-meta.xml` for the adapter's callout, surfacing external data as records, \"custom adapter\", \"ExternalId field\", \"DataSource namespace\", or whether custom Apex fits. DO NOT TRIGGER when: a standard adapter is already configured (OData, Snowflake), for copy/bulk-sync (use platform-data-manage), or for Apex callouts outside Connect (use platform-apex-generate or integration-connectivity-generate)."
 metadata:
   version: "1.0"
   minApiVersion: "66.0"
@@ -26,7 +26,7 @@ Route the user through building a complete custom Salesforce Connect Apex adapte
 
 **In scope:** Generating `DataSource.Connection` and `DataSource.Provider` Apex classes, Named Credential metadata, deployment via sf CLI, and step-by-step Setup registration guidance for any REST API.
 
-**Out of scope:** Configuring standard adapters (OData, Snowflake, GraphQL — those have their own flows). Generating the External Data Source metadata file (not deployable via sf CLI — must be registered manually in Setup). Writing Apex that calls external APIs outside the Salesforce Connect framework (use [platform-apex-generate](../platform-apex-generate/SKILL.md) or [integration-connectivity-generate](../integration-connectivity-generate/SKILL.md)).
+**Out of scope:** Configuring standard adapters (OData, Snowflake, GraphQL — those have their own flows). Generating the External Data Source metadata file (not deployable via sf CLI — must be registered manually in Setup). Writing Apex that calls external APIs outside the Salesforce Connect framework (use the platform-apex-generate or integration-connectivity-generate skills).
 
 ## Before starting
 
@@ -37,11 +37,11 @@ Confirm two things. If either is missing, ask before proceeding.
 | The user wants to… | Right tool |
 |---|---|
 | Query external data live without copying it — read-only or read-write, appears as Salesforce records | **This skill** |
-| Copy or sync data into Salesforce on a schedule | [platform-data-manage](../platform-data-manage/SKILL.md) |
+| Copy or sync data into Salesforce on a schedule | the platform-data-manage skill |
 | Connect to OData, GraphQL, DynamoDB, Athena, or Cross-Org | Standard adapter setup — no Apex needed, different flow |
 | Connect to Snowflake via Salesforce's native Snowflake adapter (direct Snowflake protocol) | Built-in Snowflake adapter — no Apex needed |
 | Access Snowflake (or any database) data via a REST or HTTP API | **This skill** — Snowflake REST endpoint → custom Apex adapter |
-| Call an external API from Apex or Flow logic | [platform-apex-generate](../platform-apex-generate/SKILL.md) or [integration-connectivity-generate](../integration-connectivity-generate/SKILL.md) |
+| Call an external API from Apex or Flow logic | the platform-apex-generate skill or [integration-connectivity-generate](../integration-connectivity-generate/SKILL.md) |
 | Expose Salesforce data to an external system | [integration-connectivity-generate](../integration-connectivity-generate/SKILL.md) |
 | Receive real-time pushed data or subscribe to external events | Not Salesforce Connect — Connect is pull-only. Use Platform Events or Change Data Capture instead |
 | Sync or copy data for analytics or bulk processing | Data Cloud or ETL — Connect is zero-copy virtualization only |

package/skills/platform-sharing-owd-configure/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-sharing-owd-configure
-description: "Use when the user wants to retrieve or update Organization-Wide Default (OWD) sharing settings for Salesforce objects. TRIGGER when: user asks to check current OWD settings, view sharing defaults, change default access levels (Private, Public Read Only, Public Read/Write, Controlled by Parent), configure internal or external access for standard or custom objects, mentions org-wide defaults, wants to make records private or restrict who can see records, wants to control default record visibility for an object, or references .settings-meta.xml sharing fields or sharingModel in .object-meta.xml files. DO NOT TRIGGER when: user asks about sharing rules, criteria-based sharing, role hierarchy, or manual sharing — delegate to platform-sharing-rules-generate."
+description: "Use when the user wants to retrieve or update Organization-Wide Default (OWD) sharing settings for Salesforce objects. TRIGGER on org-wide defaults, checking/viewing sharing defaults, changing default access levels (Private, Public Read Only, Public Read/Write, Controlled by Parent), internal/external access for standard or custom objects, making records private, or sharingModel in .object-meta.xml files. DO NOT TRIGGER for sharing rules, criteria-based sharing, role hierarchy, or manual sharing — delegate to platform-sharing-rules-generate."
 metadata:
   relatedSkills:
     - "platform-metadata-deploy"

package/skills/platform-sharing-rules-generate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-sharing-rules-generate
-description: "Use this skill when users need to get, create, edit, delete, or manage Salesforce Sharing Rules metadata. TRIGGER when: users mention sharing rules, record sharing, criteria-based sharing, role-based sharing, guest user sharing, sharingRules, sharingCriteriaRules, sharingGuestRules, sharingOwnerRules, .sharingRules-meta.xml files, or ask to share records with specific roles or groups. Also trigger when users want to retrieve or view existing sharing rules from an org, modify or remove existing sharing rules, or update sharing rule criteria or access levels. DO NOT TRIGGER when user needs permission sets or profiles (use platform-permission-set-generate), or needs object-level security rather than record-level sharing (use platform-permission-set-generate)."
+description: "Use when users get, create, edit, delete, or retrieve Salesforce Sharing Rules metadata for record-level access. TRIGGER on sharing rules, record/criteria-based/role-based/guest-user sharing, sharingCriteriaRules/sharingOwnerRules/sharingGuestRules, .sharingRules-meta.xml files, or sharing records with roles or groups, including viewing or modifying existing rules. DO NOT TRIGGER for permission sets/profiles or object-level (not record-level) security (use platform-permission-set-generate)."
 metadata:
   version: "1.3"
   domains: ["Platform"]

package/skills/platform-soql-query/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-soql-query
-description: "SOQL query generation, optimization, and analysis with 100-point scoring. Use this skill when the user needs SOQL/SOSL authoring or optimization: natural-language-to-query generation, relationship queries, aggregates, query-plan analysis, and performance or safety improvements for Salesforce queries. TRIGGER when: user writes, optimizes, or debugs SOQL/SOSL queries, touches .soql files, or asks about relationship queries, aggregates, or query performance. DO NOT TRIGGER when: bulk data operations (use platform-data-manage), Apex DML logic (use platform-apex-generate), or report/dashboard queries."
+description: "Use when the user needs SOQL/SOSL authoring or optimization: natural-language-to-query generation, relationship queries, aggregates, query-plan/selectivity analysis, and performance or safety improvements. TRIGGER when the user writes, optimizes, or debugs SOQL/SOSL, touches .soql files, or asks about relationship queries, aggregates, or query performance. DO NOT TRIGGER for bulk data operations (use platform-data-manage), Apex DML logic (use platform-apex-generate), or report/dashboard queries."
 metadata:
   version: "1.1"
   domains: ["Platform"]

package/skills/platform-value-set-generate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: platform-value-set-generate
-description: "Use this skill when users need to create, generate, or validate a Salesforce global value set or customize a standard value set. Trigger when users mention a global value set, GlobalValueSet, standard value set, StandardValueSet, a reusable picklist, a picklist value set shared across fields, or customizing standard picklists like Industry, Lead Source, or Opportunity Stage. Also use when users hit deployment errors adding values to a standard picklist, referencing a value set from a custom field, or working with .globalValueSet-meta.xml or .standardValueSet-meta.xml files. DO NOT TRIGGER for an inline one-off picklist on a single field with no reuse, or for general custom field metadata work that does not involve a GlobalValueSet or StandardValueSet — use platform-custom-field-generate instead."
+description: "Use to create, generate, or validate a Salesforce GlobalValueSet (reusable picklist shared across fields) or customize a StandardValueSet (built-in picklists like Industry, Lead Source, Opportunity Stage). Trigger on global/standard value set, reusable picklist, .globalValueSet-meta.xml or .standardValueSet-meta.xml, or deploy errors adding values to a standard picklist. DO NOT TRIGGER for a one-off inline picklist on a single field with no reuse — use platform-custom-field-generate."
 metadata:
   version: "1.0"
   domains: ["Platform"]

package/skills/service-agentforce-human-escalation-configure/SKILL.md

@@ -196,6 +196,10 @@ A single JSON object to stdout:
 
 Existing queue, `QueueSobject`, `QueueRoutingConfig`, queue members, and an already-active outbound flow are reused, not recreated (members are only added when the queue has zero active members and `QUEUE_MEMBER_USERNAMES` is supplied; already-present members are left untouched). The doc-driven edits (`canEscalate`, `outboundRouteConfigs`) are set-if-absent. A second run against a fully configured org performs no writes and returns `CONFIGURED`.
 
+## Classifier contracts
+
+Before investigating or changing any of the deterministic Node classifiers referenced above (`scripts/classify-agent-active.mjs`, `scripts/verify-escalation-config.mjs`, `scripts/extract-outbound-route.mjs`, `scripts/classify-nga-escalation.mjs`), read [references/classifier-contracts.md](references/classifier-contracts.md) for each one's exact input/output contract.
+
 ## Verification
 
 Run the bundled escalation contract tests after changing this skill or its scripts:

package/skills/service-agentforce-human-escalation-configure/scripts/tests/_bootstrap.py

@@ -6,12 +6,30 @@ import subprocess
 import tempfile
 from pathlib import Path
 
-# skills/ root is three levels up (.../<skill>/scripts/tests/_bootstrap.py).
+# skills/ root is three levels up (.../<skill>/scripts/tests/_bootstrap.py). In the flat copy
+# this is the repo's skills/ directory; in a plugin mirror it is that plugin's own bundled
+# skills/ directory, which only contains its own roster.
 SKILLS_ROOT = Path(__file__).resolve().parents[3]
 
+
+def _find_flat_skills_root(start: Path) -> Path:
+    """Walk up from this file to the repo's flat skills/ root, which bundles every skill
+    exactly once. Cross-skill references that aren't part of this skill's own plugin roster
+    (like the ITSM coordinator's verdict script below) must resolve here, not under
+    SKILLS_ROOT, since a plugin mirror's SKILLS_ROOT only contains its own bundled skills."""
+    for parent in start.parents:
+        candidate = parent / "skills" / "service-itsm-agentic-setup-agentforce-coordinate"
+        if candidate.is_dir():
+            return parent / "skills"
+    raise RuntimeError("could not locate the repo's flat skills/ root")
+
+
+FLAT_SKILLS_ROOT = _find_flat_skills_root(Path(__file__).resolve())
+
 SKILL_DIR = "service-agentforce-human-escalation-configure"
 SCRIPT = f"{SKILL_DIR}/scripts/verify-and-configure.sh"
-# The ITSM coordinator's advancement gate - exercised for the escalation verdict mapping.
+# The ITSM coordinator's advancement gate - exercised for the escalation verdict mapping. Not
+# bundled per-plugin, so resolved against FLAT_SKILLS_ROOT (see run_node's root parameter).
 VERDICT_SCRIPT = "service-itsm-agentic-setup-agentforce-coordinate/scripts/verify-child-verdict.mjs"
 
 # A fake `sf` that reports a PRODUCTION customer org so the safe_to_write guard must refuse.
@@ -220,11 +238,13 @@ def run(args, path_prefix=None, scrub_sf=False, extra_env=None):
     return proc.returncode, (proc.stdout or "") + (proc.stderr or "")
 
 
-def run_node(script_rel, args):
-    """Run a bundled Node helper; return (returncode, stdout)."""
+def run_node(script_rel, args, root=None):
+    """Run a bundled Node helper; return (returncode, stdout). Pass `root=FLAT_SKILLS_ROOT`
+    for cross-skill scripts not bundled in this skill's own plugin roster."""
+    base = root if root is not None else SKILLS_ROOT
     proc = subprocess.run(
-        ["node", str(SKILLS_ROOT / script_rel), *args],
-        capture_output=True, text=True, cwd=str(SKILLS_ROOT),
+        ["node", str(base / script_rel), *args],
+        capture_output=True, text=True, cwd=str(base),
     )
     return proc.returncode, (proc.stdout or "")
 

package/skills/service-agentforce-human-escalation-configure/scripts/tests/test_escalation_contracts.py

@@ -17,6 +17,7 @@ from pathlib import Path
 sys.path.insert(0, str(Path(__file__).resolve().parent))
 from _bootstrap import (  # noqa: E402
     SKILLS_ROOT,
+    FLAT_SKILLS_ROOT,
     SKILL_DIR,
     SCRIPT,
     VERDICT_SCRIPT,
@@ -700,13 +701,13 @@ class NgaClassifierHardeningTests(unittest.TestCase):
 
 class CoordinatorGateTests(unittest.TestCase):
     def test_escalation_verdict_mapping(self):
-        rc, out = run_node(VERDICT_SCRIPT, ["escalation", "CONFIGURED"])
+        rc, out = run_node(VERDICT_SCRIPT, ["escalation", "CONFIGURED"], root=FLAT_SKILLS_ROOT)
         self.assertEqual(rc, 0, out)
-        rc, _ = run_node(VERDICT_SCRIPT, ["escalation", "ALREADY-CONFIGURED"])
+        rc, _ = run_node(VERDICT_SCRIPT, ["escalation", "ALREADY-CONFIGURED"], root=FLAT_SKILLS_ROOT)
         self.assertEqual(rc, 0)
-        rc, _ = run_node(VERDICT_SCRIPT, ["escalation", "INCOMPLETE"])
+        rc, _ = run_node(VERDICT_SCRIPT, ["escalation", "INCOMPLETE"], root=FLAT_SKILLS_ROOT)
         self.assertEqual(rc, 1)
-        rc, _ = run_node(VERDICT_SCRIPT, ["escalation", "BLOCKED"])
+        rc, _ = run_node(VERDICT_SCRIPT, ["escalation", "BLOCKED"], root=FLAT_SKILLS_ROOT)
         self.assertEqual(rc, 1)
 
 

package/skills/service-de-waba-integrate/SKILL.md

@@ -1,12 +1,13 @@
 ---
 name: service-de-waba-integrate
-description: "Confirm the customer's WhatsApp Business Account is shared with Salesforce on Meta's side. Pure instruction + one user-confirmation prompt — no API calls, no token handling. The actual sharing happens in Meta Business Suite (UI-only; Meta provides no Graph endpoint to automate this step). Renders step-by-step instructions with Salesforce's Business Manager ID substituted in, then asks the user to confirm whether \"Salesforce\" appears in the WABA's Partners list."
+description: "Confirm the customer's WhatsApp Business Account is shared with Salesforce on Meta's side. TRIGGER when the user asks to link, share, or confirm sharing of a WhatsApp Business Account with Salesforce, or to verify Salesforce appears in the WABA's Partners list. Pure instruction + one user-confirmation prompt — no API calls, no token handling. Sharing happens in Meta Business Suite (UI-only; Meta has no Graph endpoint for this). Renders step-by-step instructions with Salesforce's Business Manager ID substituted in, then asks the user to confirm whether \"Salesforce\" appears in the WABA's Partners list. DO NOT TRIGGER when the user needs full end-to-end WhatsApp setup (use `service-de-headless-channel-configure`) or to insert the channel record itself (use `service-de-channel-create`)."
 metadata:
   version: "1.0"
   minApiVersion: "67.0"
   domains: ["Service"]
   relatedSkills:
     - "service-de-channel-create"
+    - "service-de-headless-channel-configure"
 ---
 
 # Linking a WABA to Salesforce

package/skills/service-digital-engagement-deployment-configure/SKILL.md

@@ -10,6 +10,8 @@ metadata:
     - "platform-permission-set-generate"
     - "service-digital-engagement-channel-configure"
   cliTools:
+    - tool: ["python3"]
+      semver: ">=3.8"
     - tool: ["sf"]
       semver: ">=2.0.0"
 ---

package/skills/service-digital-engagement-deployment-configure/scripts/check-api-version.sh

@@ -0,0 +1,29 @@
+#!/bin/bash
+# Verifies the target org's API version meets the minimum requirement.
+# Usage: check-api-version.sh <min-version> <org-alias>
+# Exits 0 if version >= min-version, exits 1 with error message otherwise.
+
+MIN_VERSION="${1:?Usage: check-api-version.sh <min-version> <org-alias>}"
+ORG_ALIAS="${2:?Usage: check-api-version.sh <min-version> <org-alias>}"
+
+API_VERSION=$(sf org display --target-org "$ORG_ALIAS" --json 2>/dev/null | python3 -c "
+import json, sys
+try:
+    data = json.load(sys.stdin)
+    print(data.get('result', {}).get('apiVersion', ''))
+except Exception:
+    print('')
+")
+
+if [ -z "$API_VERSION" ]; then
+  echo "ERROR: Could not determine API version for org '$ORG_ALIAS'."
+  exit 1
+fi
+
+if python3 -c "import sys; sys.exit(0 if float(sys.argv[1]) >= float(sys.argv[2]) else 1)" "$API_VERSION" "$MIN_VERSION"; then
+  echo "OK: Org API version $API_VERSION meets minimum $MIN_VERSION."
+  exit 0
+else
+  echo "ERROR: Org API version $API_VERSION is below minimum $MIN_VERSION. Generate a sfdx-project.json with \"sourceApiVersion\": \"$MIN_VERSION\" in the metadata output folder."
+  exit 1
+fi

package/skills/service-email-to-case-configure/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: service-email-to-case-configure
-description: "Use to configure Salesforce Email-to-Case in a headless flow via the Metadata API. Reads the current CaseSettings, applies the desired emailToCase configuration with the updateMetadata CRUD call, and verifies by re-reading. Also the entry point when the user wants an Agentforce service agent on Email-to-Case: this skill configures the E2C base, then delegates agent creation and channel wiring. Start here even when no agent exists yet. TRIGGER when the user says set up Email-to-Case, configure email to case, enable Email-to-Case routing addresses, add an email routing address, Email-to-Case Metadata API, or set up Email-to-Case with an Agentforce service agent (attach an agent to an email routing address). DO NOT TRIGGER when the user needs the interactive Service Easy Setup wizard for E2cEasy addresses, when configuring On-Demand Email-to-Case only, for general Case object or web-to-case setup, or when only creating an Agentforce agent with no Email-to-Case involved."
+description: "Use to configure Salesforce Email-to-Case headlessly via the Metadata API. Reads CaseSettings, applies the emailToCase config with updateMetadata, and verifies by re-reading. Also the entry point for attaching an Agentforce agent to Email-to-Case: configures the E2C base, then delegates agent creation and channel wiring. TRIGGER on set up/configure Email-to-Case, enable E2C routing addresses, add a routing address, or E2C with an Agentforce agent. DO NOT TRIGGER for the interactive Easy Setup wizard, On-Demand E2C only, general Case/web-to-case setup, or an agent with no E2C involved."
 metadata:
   version: "1.1"
   domains: ["Service", "Agentforce"]

package/skills/service-omni-channel-setup-coordinate/SKILL.md

@@ -13,6 +13,7 @@ metadata:
     - "service-omni-base-settings-configure"
     - "service-omni-channel-inventory-analyze"
     - "service-omni-command-center-analyze"
+    - "service-omni-command-center-configure"
     - "service-omni-permission-set-assign"
     - "service-omni-presence-status-deploy"
     - "service-omni-presence-user-config-deploy"

package/skills/service-omni-command-center-analyze/SKILL.md

@@ -8,6 +8,7 @@ metadata:
   minApiVersion: "66.0"
   relatedSkills:
     - "service-omni-channel-setup-coordinate"
+    - "service-omni-command-center-configure"
     - "service-omni-supervisor-config-deploy"
   accessCheck:
     - type: license

package/skills/service-omni-command-center-configure/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: service-omni-command-center-configure
+description: "Use to enable Command Center for Service V2 and configure its supported supervisor controls through the OmniChannel Settings Metadata API while preserving unrelated settings. Requires explicit apply consent, refuses production customer orgs, and verifies the seeded V2 page and tab. TRIGGER when: enable Command Center V2, configure conversation monitoring, enable agent sneak peek, enable customer sneak peek, configure whisper messaging, or enable queues and skills actions. Do not use to assign supervisor permissions or configure classic OmniSupervisorConfig metadata."
+allowed-tools: Bash Read Write Edit Grep Glob
+metadata:
+  version: "1.0"
+  domains: ["Service"]
+  minApiVersion: "69.0"
+  relatedSkills:
+    - "service-omni-base-settings-configure"
+    - "service-omni-channel-setup-coordinate"
+    - "service-omni-command-center-analyze"
+    - "service-omni-supervisor-config-deploy"
+  accessCheck:
+    - type: license
+      value: ServiceCloud
+  cliTools:
+    - tool: ["jq"]
+      semver: ">=1.6"
+    - tool: ["python3"]
+      semver: ">=3.8"
+    - tool: ["sf"]
+      semver: ">=2.139.6"
+---
+
+# service-omni-command-center-configure
+
+Enable Command Center for Service V2 through `Settings:OmniChannel` and optionally configure the five supervisor controls exposed by the same Metadata API contract. The writer retrieves the org's complete settings document, changes only requested elements, deploys that preserved document, retrieves it again, and verifies both the values and the platform-created `CommandCenterForServiceV2_L` page and V2 tab.
+
+The skill fails closed with `platform_api_unavailable` when the retrieved settings document does not expose `enableCommandCenterForServiceV2`.
+
+Run `service-omni-base-settings-configure` first so the Omni foundation is enabled. If the org does not support Command Center V2, use `service-omni-supervisor-config-deploy` for the classic supervisor configuration instead.
+
+For an end-to-end setup, `service-omni-channel-setup-coordinate` invokes this skill only when `OMNI_COMMAND_CENTER_V2=1`; the coordinator's default supervisor path remains unchanged.
+
+## Inputs
+
+```bash
+bash scripts/configure-and-report.sh plan <org-alias> [options]
+bash scripts/configure-and-report.sh run  <org-alias> --apply [options]
+```
+
+Options:
+
+| Option | Metadata element | Values |
+|---|---|---|
+| `--conversation-monitoring` | `enableConversationMonitoring` | `true` or `false` |
+| `--agent-sneak-peek` | `enableAgentSneakPeek` | `true` or `false` |
+| `--customer-sneak-peek` | `enableClientSneakPeek` | `true` or `false` |
+| `--whisper-messaging` | `enableWhisperMessaging` | `true` or `false` |
+| `--queues-and-skills` | `enableSkillsAndQueueActions` | `true` or `false` |
+
+`enableCommandCenterForServiceV2=true` is always requested. Unspecified supervisor controls are preserved exactly as retrieved. The skill intentionally does not disable V2 because disabling an org-level supervisor experience is a materially different operation.
+
+## Safety
+
+- `plan` is read-only and never deploys.
+- `run` requires the literal `--apply` flag before any mutation.
+- Writes are allowed only when `IsSandbox=true`, `TrialExpirationDate` is non-null, or `OrganizationType` is `Developer Edition` or `Base Edition`. There is no production override.
+- `Settings` is a whole-document Metadata API type. Never deploy a partial or hardcoded `OmniChannel.settings-meta.xml`; doing so can reset unrelated Omni settings.
+- The target org must have Enhanced Omni-Channel and the Command Center for Service V2 release gater. The API field is also permission-gated by `Customize Application`.
+
+## Behavior
+
+1. Authenticate and retrieve `Settings:OmniChannel` at API v66.
+2. Confirm the V2 field is present. If it is absent, return `blocked` with `reason_code=platform_api_unavailable`; do not attempt a deploy.
+3. Build a requested-value set containing V2=`true` plus only the optional controls explicitly supplied by the caller.
+4. In `plan`, return `action_needed` or `reused` without writing.
+5. In `run`, enforce `--apply` and the non-production guard, mutate a private copy of the retrieved document, and deploy it.
+6. Retrieve the settings again and require every requested value to match.
+7. Require both the seeded `FlexiPage` (`CommandCenterForServiceV2_L`) and V2 `TabDefinition` to be observable. Missing or unreadable provisioning evidence returns `blocked`; the skill never guesses.
+
+The platform's ON-transition hook is idempotent: it creates missing profile tab configuration and seeds the baseline FlexiPage only when needed. Existing page customizations are not overwritten. If the preference is already true but its seed artifacts are missing, the skill returns `seed_incomplete`; it does not force a destructive OFF→ON cycle.
+
+## Output contract
+
+The script emits one JSON object with:
+
+- `status`: `configured`, `reused`, `action_needed`, or `blocked`
+- `reason_code`: a stable reason such as `changes_required`, `already_configured`, `platform_api_unavailable`, `unsafe_target`, `deploy_failed`, `verification_failed`, or `seed_incomplete`
+- `requested`, `before`, and `after`: setting values, with presence retained in the snapshots
+- `safe_to_write`, `deploy_id`, and `verification`
+- `manual_actions`: permission assignment and any required follow-up
+- `blocking_issue`: populated only when blocked
+
+Enabling the org preference does not grant user access. Assign a permission set containing `CommandCenterForServiceUser` to each intended supervisor, then run `service-omni-command-center-analyze <org> <supervisor>` to verify end-to-end readiness.
+
+## References
+
+| File | When to read |
+|---|---|
+| `references/api-notes.md` | Metadata names, platform gates, seed behavior, and known limitations |

package/skills/service-omni-command-center-configure/references/api-notes.md

@@ -0,0 +1,50 @@
+# Command Center for Service V2 API notes
+
+## Metadata contract
+
+Core work item `W-24039822` and Core PR `#16874` expose these fields on `Settings:OmniChannel`:
+
+| Metadata field | Product control |
+|---|---|
+| `enableCommandCenterForServiceV2` | Command Center for Service V2 |
+| `enableConversationMonitoring` | Conversation monitoring |
+| `enableAgentSneakPeek` | Agent sneak peek |
+| `enableClientSneakPeek` | Customer sneak peek |
+| `enableWhisperMessaging` | Whisper messaging |
+| `enableSkillsAndQueueActions` | Queues and skills actions |
+
+The V2 preference is Metadata API writable only when the target release contains that contract and the `OmniChannel.commandCenterForServiceV2Available` access check passes. That access check requires the feature gater and Enhanced Omni-Channel. Standard Omni orgs on the EOL extension cannot enable V2.
+
+## ON-transition side effects
+
+Changing `enableCommandCenterForServiceV2` from false to true invokes the existing `CommandCenterForServiceV2OrgPreference` hook. The hook:
+
+1. inserts missing profile tab configurations for the V2 tab;
+2. checks for `FlexiPage.DeveloperName='CommandCenterForServiceV2_L'`;
+3. clones the platform seed only when that page is absent.
+
+Disabling the preference does not delete the page. Re-enabling preserves an existing page. This skill enables but does not disable V2.
+
+## Verification signals
+
+The writer verifies the settings by a fresh Metadata API retrieve and verifies provisioning through:
+
+```sql
+SELECT Id FROM FlexiPage WHERE DeveloperName='CommandCenterForServiceV2_L'
+```
+
+using Tooling API, and:
+
+```sql
+SELECT Name FROM TabDefinition WHERE Name='standard-commandcenterforservicev2'
+```
+
+using the data API. Query errors remain `unknown` and block a successful write claim.
+
+## User access
+
+The org preference and its seed artifacts establish org-level readiness only. A supervisor also needs a permission set with `PermissionsCommandCenterForServiceUser=true`. This skill reports that follow-up but does not create users or permission sets.
+
+## Whole-document requirement
+
+Salesforce Settings metadata is deployed as a complete document. The implementation retrieves the current document and updates it in place. Do not replace this approach with a static template: a static template can silently drop existing Omni settings that are outside this skill's scope.