@salesforce/afv-skills 1.38.0 → 1.40.0

package/skills/omnistudio-integration-procedure-generate/SKILL.md

@@ -13,6 +13,7 @@ metadata:
     - "platform-apex-generate"
     - "platform-metadata-deploy"
   version: "1.0"
+  domains: ["OmniStudio"]
   minApiVersion: "60.0"
 ---
 

package/skills/omnistudio-omniscript-generate/SKILL.md

@@ -12,6 +12,7 @@ metadata:
     - "omnistudio-integration-procedure-generate"
     - "platform-metadata-deploy"
   version: "1.0"
+  domains: ["OmniStudio"]
 ---
 
 # omnistudio-omniscript-generate: OmniStudio OmniScript Creation and Validation

package/skills/platform-agentexchange-partner-offers-configure/SKILL.md

@@ -11,6 +11,7 @@ metadata:
     - "platform-apex-generate"
     - "platform-metadata-deploy"
   version: "1.0"
+  domains: ["Platform"]
   minApiVersion: "67.0"
 ---
 

package/skills/platform-agentsetup-categories-fetch/SKILL.md

@@ -7,6 +7,7 @@ metadata:
     - tool: ["sf"]
       semver: ">=2.0.0"
   version: "1.0"
+  domains: ["Platform", "Agentforce"]
   minApiVersion: "67.0"
 ---
 

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

@@ -3,6 +3,7 @@ name: platform-apex-generate
 description: "Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill for requests involving SObject CRUD, mapping collections, fetching related records, scheduled jobs, batch jobs, trigger design, @AuraEnabled controllers, @RestResource endpoints, custom REST APIs, or code review of existing Apex."
 metadata:
   version: "1.1"
+  domains: ["Platform"]
   minApiVersion: "66.0"
   relatedSkills:
     - "platform-apex-test-generate"

package/skills/platform-apex-logs-debug/SKILL.md

@@ -15,6 +15,7 @@ metadata:
     - "platform-metadata-deploy"
     - "platform-soql-query"
   version: "1.1"
+  domains: ["Platform"]
 ---
 
 # platform-apex-logs-debug: Salesforce Debug Log Analysis & Troubleshooting

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

@@ -3,6 +3,7 @@ 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."
 metadata:
   version: "1.1"
+  domains: ["Platform"]
   minApiVersion: "66.0"
   relatedSkills:
     - "platform-apex-generate"

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

@@ -3,6 +3,7 @@ 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)."
 metadata:
   version: "1.2"
+  domains: ["Platform"]
   relatedSkills:
     - "agentforce-test"
     - "experience-lwc-generate"

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

@@ -3,6 +3,7 @@ name: platform-custom-application-generate
 description: "Use this skill when users need to create or configure tab-based Salesforce Custom Applications with navigation, branding, and action overrides. Trigger when users mention custom apps, application metadata, app navigation, or organizing tabs into applications. Use when users want to create app containers for tabs and pages. Do NOT use when the goal is hosting a React UI bundle in the App Launcher — use experience-ui-bundle-custom-app-generate for that case."
 metadata:
   version: "1.0"
+  domains: ["Platform"]
   minApiVersion: "60.0"
 ---
 

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

@@ -3,6 +3,7 @@ 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."
 metadata:
   version: "1.0"
+  domains: ["Platform"]
   minApiVersion: "60.0"
   relatedSkills:
     - "platform-validation-rule-generate"

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

@@ -3,6 +3,7 @@ name: platform-custom-lightning-type-generate
 description: "Use this skill when users need to create Custom Lightning Types (CLTs) for Einstein Agent actions or structured input/output schemas. Trigger when users mention CLT, Custom Lightning Types, JSON schemas for agents, type definitions, lightning__objectType, or editor/renderer configurations. For widget renditions that combine a CLT with a Widget bundle, use the platform-lightning-type-widget-coordinate orchestrator instead. This is complex - always use this skill for CLT work."
 metadata:
   version: "1.1"
+  domains: ["Platform", "Agentforce"]
   minApiVersion: "60.0"
   relatedSkills:
     - "platform-lightning-type-widget-coordinate"

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

@@ -3,6 +3,7 @@ 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."
 metadata:
   version: "1.1"
+  domains: ["Platform"]
   minApiVersion: "60.0"
 ---
 

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

@@ -3,6 +3,7 @@ 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."
 metadata:
   version: "1.0"
+  domains: ["Platform"]
   minApiVersion: "51.0"
 ---
 

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

@@ -3,6 +3,7 @@ name: platform-custom-tab-generate
 description: "Use this skill when users need to create or configure Salesforce Custom Tabs. Trigger when users mention tabs, navigation tabs, object tabs, web tabs, Visualforce tabs, Lightning component tabs, app page tabs, or tab configuration. Also use when users want to add navigation to custom objects, create tabs for external content, or set up Lightning page tabs. Always use this skill for any custom tab work."
 metadata:
   version: "1.0"
+  domains: ["Platform"]
   minApiVersion: "60.0"
 ---
 

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

@@ -3,6 +3,7 @@ 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)."
 metadata:
   version: "1.0"
+  domains: ["Platform"]
   minApiVersion: "67.0"
   relatedSkills:
     - "platform-metadata-api-context-get"

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

@@ -18,6 +18,7 @@ metadata:
     - "platform-metadata-deploy"
     - "platform-soql-query"
   version: "1.1"
+  domains: ["Platform"]
 ---
 
 # Salesforce Data Operations Expert (platform-data-manage)

package/skills/platform-dataspace-access-configure/SKILL.md

@@ -3,6 +3,7 @@ name: platform-dataspace-access-configure
 description: "Use this skill to configure Salesforce Data Cloud DataSpace access for permission sets. Grants dataspace-level access via MDAPI PermissionSet XML with dataspaceScopes elements, and optionally grants object-level access to specific DMO, DLO, or CIO objects via the Object Access Grants Connect API. TRIGGER when: user needs to create or update a permission set that includes DataSpace access, grant a permission set access to a specific dataspace, configure dataAccessLevel or objectAccessLevel for a dataspace scope, add RBAC object access grants for Data Cloud objects, or list or remove object access grants for a permission set and DataSpace pair. DO NOT TRIGGER when: the task is a generic permission set without any dataspace access (use platform-permission-set-generate), the request is about data ingestion or streams (use data360-prepare), or the work involves creating dataspaces themselves rather than granting access to them."
 metadata:
   version: "1.0"
+  domains: ["Platform", "Data 360"]
   minApiVersion: "67.0"
   cliTools:
     - tool: ["jq"]

package/skills/platform-docs-get/SKILL.md

@@ -3,6 +3,7 @@ name: platform-docs-get
 description: "Official Salesforce documentation retrieval skill. Use when you need authoritative Salesforce docs from developer.salesforce.com, help.salesforce.com, architect.salesforce.com, admin.salesforce.com, or lightningdesignsystem.com, especially when pages are JS-heavy, shell-rendered, or hard to extract with naive fetching. Use to ground answers in official Salesforce sources instead of third-party blogs or summaries. TRIGGER when: user asks for official Salesforce documentation, Apex or API reference, LWC docs, Agentforce docs, setup or help articles, or any doc from a Salesforce-owned domain. DO NOT TRIGGER when: user is asking for a code change, deployment task, or anything not requiring documentation retrieval — use the appropriate sf-* skill instead."
 metadata:
   version: "1.2"
+  domains: ["Platform"]
   cliTools:
     - tool: ["python3"]
       semver: ">=3.10.0"

package/skills/platform-encryption-configure/SKILL.md

@@ -3,6 +3,7 @@ name: platform-encryption-configure
 description: "Configure Salesforce Shield Platform Encryption — generate deployable encryption settings and encrypted-field metadata, and answer key-model and lifecycle questions. TRIGGER when: user wants to turn on deterministic encryption, encrypt a field, set up Cache-Only Keys, External Key Management, or replay detection, or mentions Shield Platform Encryption, encryption at rest, deterministic vs probabilistic encryption, encryptionScheme, PlatformEncryptionSettings, EncryptionKeySettings, BYOK, BYOKMS, tenant secrets, key rotation, or .settings-meta.xml / .field-meta.xml for encryption — even when they don't say 'Shield'. SKIP when: user needs a generic custom field with no encryption (use platform-custom-field-generate), needs the raw Metadata API type reference (use platform-metadata-api-context-get), or asks about Classic Encryption (encrypted text fields), which is a different feature. Use this skill for any Platform Encryption configuration, field-encryption, or key-model question."
 metadata:
   version: "1.0"
+  domains: ["Platform"]
   minApiVersion: "62.0"
   relatedSkills:
     - "platform-custom-field-generate"

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

@@ -4,6 +4,7 @@ description: "Use this skill when users need to create, generate, modify, or val
 allowed-tools: Bash Read Write
 metadata:
   version: "1.1"
+  domains: ["Platform"]
   minApiVersion: "60.0"
   cliTools:
     - tool: ["python3"]

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

@@ -3,6 +3,7 @@ name: platform-lightning-app-coordinate
 description: "Build complete Salesforce Lightning Experience applications from natural language descriptions. Use this skill when a user requests a \"complete app\", \"Lightning app\", \"business solution\", \"management system\", or describes a scenario requiring multiple interconnected Salesforce components (objects, fields, pages, tabs, security). Orchestrates all required metadata types in proper dependency order to produce a deployable application."
 metadata:
   version: "1.0"
+  domains: ["Platform"]
   minApiVersion: "60.0"
   relatedSkills:
     - "automation-flow-generate"
@@ -84,7 +85,7 @@ This table shows which metadata types are commonly needed for Lightning Experien
 
 ### Phase 1: Data Model (Foundation)
 
-```
+```text
 Custom Objects (no dependencies)
     ↓
 Custom Fields (depends on: Objects exist)
@@ -99,7 +100,7 @@ Relationships (depends on: Both parent and child objects + fields exist)
 
 ### Phase 2: Business Logic (Optional - only if requested)
 
-```
+```text
 Validation Rules (depends on: Fields exist)
     ↓
 Flows (depends on: Objects, Fields exist)
@@ -112,7 +113,7 @@ Flows (depends on: Objects, Fields exist)
 
 ### Phase 3: User Interface
 
-```
+```text
 List Views (depends on: Objects, Fields exist)
     ↓
 Custom Tabs (depends on: Objects exist)
@@ -128,7 +129,7 @@ FlexiPages (depends on: Objects, Tabs exist)
 
 ### Phase 4: Application Assembly
 
-```
+```text
 Custom Application (depends on: Tabs exist)
 ```
 
@@ -138,7 +139,7 @@ Custom Application (depends on: Tabs exist)
 
 ### Phase 5: Security & Access
 
-```
+```text
 Permission Sets (depends on: Objects, Fields, Tabs, App exist)
 ```
 
@@ -170,7 +171,7 @@ Permission Sets (depends on: Objects, Fields, Tabs, App exist)
 
 Generate a structured plan listing:
 
-```
+```text
 Lightning App Build Plan: [App Name]
 
 DATA MODEL:
@@ -299,7 +300,7 @@ The completed build produces:
    - Organized by standard SFDX structure: `force-app/main/default/`
 2. **Metadata Files** - One file per component, organized by type:
 
-   ```
+   ```text
    force-app/main/default/
    ├── objects/              # Custom Objects (.object-meta.xml)
    ├── fields/               # Custom Fields (.field-meta.xml)
@@ -324,7 +325,7 @@ The completed build produces:
 
 **Example Summary Structure:**
 
-```
+```text
 Lightning App Build Complete: Project Management App
 
 METADATA GENERATED:
@@ -400,7 +401,7 @@ Log warning and continue if:
 
 **Warning Pattern:**
 
-```
+```yaml
 Warning: [Component Type] generation encountered issue
     Component: [Name]
     Issue: [Description]

package/skills/platform-lightning-type-widget-coordinate/SKILL.md

@@ -3,6 +3,7 @@ name: platform-lightning-type-widget-coordinate
 description: "Orchestrate Apex-backed Lightning Type + HXL widget generation. TRIGGER only when the prompt EXPLICITLY invokes Lightning Types: user says 'Lightning Type', 'CLT', 'Custom Lightning Type', 'Apex-backed type', references '@apexClassType/...', asks to build a widget or card for a named Lightning Type, asks to create a new Lightning Type and widget together, or grounds a widget in a specific Apex class as its schema. DO NOT TRIGGER when the prompt names only a subject, domain, feature, or entity noun. Also DO NOT TRIGGER when: authoring only a Custom Lightning Type (use platform-custom-lightning-type-generate), only an Apex class (use platform-apex-generate), editing an existing widget without any Lightning Type change, or grounding a widget on an object/JSON-based Lightning Type (lightning__objectType with primitives)."
 metadata:
   version: "1.3"
+  domains: ["Platform", "Agentforce"]
   minApiVersion: "68.0"
   relatedSkills:
     - "platform-apex-generate"

package/skills/platform-list-view-generate/SKILL.md

@@ -3,6 +3,7 @@ name: platform-list-view-generate
 description: "Use this skill when users need to create, generate, or validate Salesforce List View metadata. Trigger when users mention list views, filtered record lists, creating views, setting up record columns, filtering records by criteria, or ask about list view visibility. Also use when users say things like \"I need a view that shows...\", \"filter records by...\", \"create a list view for...\", or when they're working with ListView XML files and need validation or troubleshooting."
 metadata:
   version: "1.0"
+  domains: ["Platform"]
 ---
 
 ## When to Use This Skill

package/skills/platform-mcp-tool-widget-coordinate/SKILL.md

@@ -3,6 +3,7 @@ name: platform-mcp-tool-widget-coordinate
 description: "Orchestrate object-based Lightning Type + HXL widget generation to render the output of a custom MCP server tool backed by an Apex Invocable Action. TRIGGER only when the prompt EXPLICITLY involves rendering an MCP tool result: user says 'MCP server', 'MCP tool', 'custom MCP server', references a tool 'output schema' / 'tool output' / 'outputValues' envelope, names an 'invocable action' backing an MCP tool, or asks to build a widget or rich UI rendition for the output of an Apex-invocable-backed MCP tool. DO NOT TRIGGER when: customizing an Apex-backed agent action output (use platform-lightning-type-widget-coordinate), authoring only a Custom Lightning Type (use platform-custom-lightning-type-generate), authoring only an Apex class (use platform-apex-generate), or building a standalone widget with no Lightning Type or MCP tool involved (use platform-widget-generate)."
 metadata:
   version: "1.0"
+  domains: ["Platform", "Agentforce"]
   minApiVersion: "67.0"
   relatedSkills:
     - "platform-apex-generate"

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

@@ -3,6 +3,7 @@ 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."
 metadata:
   version: "1.0"
+  domains: ["Platform"]
   minApiVersion: "67.0"
   cliTools:
     - tool: ["jq"]

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

@@ -3,6 +3,7 @@ name: platform-metadata-deploy
 description: "Salesforce DevOps automation using sf CLI v2. TRIGGER when: user deploys metadata, creates/manages scratch orgs or sandboxes, sets up CI/CD pipelines, or troubleshoots deployment errors with sf project deploy. DO NOT TRIGGER when: writing Apex code (use platform-apex-generate), building LWC components (use experience-lwc-generate), creating metadata definitions (use platform-custom-object-generate or platform-custom-field-generate), or querying org data (use platform-data-manage)."
 metadata:
   version: "1.1"
+  domains: ["Platform", "Developer Experience"]
   relatedSkills:
     - "agentforce-generate"
     - "agentforce-test"

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

@@ -1,9 +1,9 @@
 ---
 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."
-compatibility: Salesforce CLI (sf) v2+
 metadata:
   version: "1.0"
+  domains: ["Platform", "Developer Experience"]
   relatedSkills:
     - "platform-metadata-deploy"
   cliTools:

package/skills/platform-models-api-configure/SKILL.md

@@ -13,6 +13,7 @@ metadata:
     - "integration-connectivity-connected-app-configure"
     - "integration-connectivity-generate"
   version: "1.0"
+  domains: ["Platform", "Agentforce"]
 ---
 
 # Salesforce Models API setup for an AI coding agent

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

@@ -3,6 +3,7 @@ name: platform-permission-set-generate
 description: "Generates correct, deployable Salesforce permission set metadata (PermissionSet XML) with object, field, user, and app permissions. Use this skill when creating or editing permission set metadata, object permissions, field-level security (FLS), tab visibility, or deploying permission sets."
 metadata:
   version: "1.0"
+  domains: ["Platform"]
   minApiVersion: "60.0"
 ---
 

package/skills/platform-policy-rule-generate/SKILL.md

@@ -3,6 +3,7 @@ name: platform-policy-rule-generate
 description: "Use this skill when authoring PolicyRuleDefinition and PolicyRuleDefinitionSet metadata XML for Salesforce Data Cloud governance policies, or when editing *.policyRuleDefinition / *.policyRuleDefinitionSet files. Covers the category decision tree, full schema for all policy variants (ACCESS, GOVERNANCE, RECORD, TRANSFORM), UI-compatibility rules for the Data Governance Policy Builder, output hygiene for user-facing agent responses, and validation guardrails. Do NOT use this skill for UserAccessPolicy, AccessPolicy, SharingRules, PermissionSet, or any other access-control metadata type — those have their own types and live outside the PolicyRuleDefinition schema."
 metadata:
   version: "1.0"
+  domains: ["Platform", "Data 360"]
   minApiVersion: "64.0"
   cliTools:
     - tool: ["jq"]

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

@@ -3,6 +3,7 @@ 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."
 metadata:
   version: "1.0"
+  domains: ["Platform"]
   minApiVersion: "60.0"
   relatedSkills:
     - "platform-custom-report-type-generate"

package/skills/platform-sandbox-configure/SKILL.md

@@ -3,6 +3,7 @@ name: platform-sandbox-configure
 description: "MUST USE this skill for ANY sandbox request — including simply getting a sandbox's details, status, license type, or pending-activation state by name or ID. TRIGGER when the user: types \"sandbox -help\"/\"sandbox help\"; mentions a sandbox ID (07E prefix); asks to list or show sandboxes; asks for the details, status, license type, or config of a sandbox by name or ID; activates or discards a completed refresh; deletes a sandbox; verifies activation or deletion; creates or refreshes a sandbox. DO NOT TRIGGER when: the user wants to clone a sandbox."
 metadata:
   version: "1.0"
+  domains: ["Platform"]
   minApiVersion: "66.0"
   accessCheck:
     - type: "userPerm"

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

@@ -3,6 +3,7 @@ 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."
 metadata:
   version: "1.2"
+  domains: ["Platform"]
   cliTools:
     - tool: ["sf"]
       semver: ">=2.0.0"

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

@@ -3,6 +3,7 @@ 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)."
 metadata:
   version: "1.3"
+  domains: ["Platform"]
   minApiVersion: "60.0"
   relatedSkills:
     - "platform-custom-object-generate"

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

@@ -16,6 +16,7 @@ metadata:
     - "platform-apex-test-run"
     - "platform-data-manage"
   version: "1.1"
+  domains: ["Platform"]
 ---
 
 # platform-soql-query: Salesforce SOQL Query Expert

package/skills/platform-tracing-agentforce-configure/SKILL.md

@@ -3,6 +3,7 @@ name: platform-tracing-agentforce-configure
 description: "Generate AgentforcePlatformTracingSettings metadata to enable or disable Agentforce agent execution trace spans flowing to Data Cloud. Use this skill for any AgentforcePlatformTracingSettings metadata work. TRIGGER when: user mentions Agentforce tracing, agent trace spans, Data Cloud tracing, AgentforcePlatformTracingSettings, platform observability tracing, enable agent tracing, wants agent execution spans in Data Cloud, mentions .settings-meta.xml for AgentforcePlatformTracing, or asks about enabling observability for Agentforce agents. DO NOT TRIGGER when: user wants Platform Tracing for TraceSpanEvent (use platform-tracing-configure), wants to query or analyze existing agent trace data in Data Cloud (use agentforce-observe), wants Event Log Files or ELF configuration, wants Change Data Capture (use integration-eventing-cdc-configure), or wants ManagedEventSubscription (use integration-eventing-subscription-configure)."
 metadata:
   version: "1.0"
+  domains: ["Platform", "Agentforce", "Data 360"]
   minApiVersion: "68.0"
   relatedSkills:
     - "agentforce-observe"

package/skills/platform-tracing-configure/SKILL.md

@@ -3,6 +3,7 @@ name: platform-tracing-configure
 description: "Generate EventSettings metadata to enable or disable Platform Tracing (TraceSpanEvent publishing) in Event Monitoring. Use this skill for any EventSettings enablePlatformTracing metadata work. TRIGGER when: user mentions Platform Tracing, TraceSpanEvent, enable tracing in Event Monitoring Settings, event monitoring tracing toggle, enablePlatformTracing, .settings-meta.xml for Event settings tracing, turn on trace span events, or stop publishing trace spans. DO NOT TRIGGER when: user wants Agentforce agent tracing to Data Cloud (use platform-tracing-agentforce-configure), wants Event Log Files or ELF generation, wants Change Data Capture (use integration-eventing-cdc-configure), or wants ManagedEventSubscription (use integration-eventing-subscription-configure)."
 metadata:
   version: "1.0"
+  domains: ["Platform"]
   minApiVersion: "68.0"
   relatedSkills:
     - "integration-eventing-cdc-configure"

package/skills/platform-trust-archive-manage/SKILL.md

@@ -3,6 +3,7 @@ name: platform-trust-archive-manage
 description: "ALWAYS USE THIS SKILL for anything involving Salesforce Archive (also called Trusted Services Archive) — search, view, unarchive, analyze, mask, and erase (RTBF) archived records via the Archive Connect API, and reading archive job status from the ArchiveActivity object. TRIGGER when: user mentions Salesforce Archive, Trusted Services Archive, archive/unarchive records, ArchiveActivity, archive jobs, archive policy, archive analyzer, archived record search, archive storage, archive failure logs, right to be forgotten / RTBF on archived data, or masking archived PII — including phrasings like 'find records that were archived', 'restore archived data', 'why did the archive job fail', 'download the archive failure log', or 'monitor my archive jobs', AND even when they ask you to explain, give guidance, or write a runbook/doc about these topics rather than run code. SKIP when: the user wants generic data-export/backup unrelated to the Archive add-on, or wants to build the archive policy UI metadata."
 metadata:
   version: "1.0"
+  domains: ["Platform"]
   cliTools:
     - tool: ["sf"]
       semver: ">=2.0.0"

package/skills/platform-validation-rule-generate/SKILL.md

@@ -3,6 +3,7 @@ name: platform-validation-rule-generate
 description: "Use this skill when users need to create, modify, or validate Salesforce Validation Rules. Trigger when users mention validation rules, field validation, data quality rules, formula validation, error messages, or validation logic. Also use when users encounter validation errors, need to update formulas, or want to enforce business rules at the data layer. Always use this skill for any validation rule work."
 metadata:
   version: "1.0"
+  domains: ["Platform"]
   minApiVersion: "60.0"
 ---
 

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

@@ -3,6 +3,7 @@ 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."
 metadata:
   version: "1.0"
+  domains: ["Platform"]
   minApiVersion: "60.0"
   cliTools:
     - tool: ["sf"]

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

@@ -3,6 +3,7 @@ name: platform-widget-generate
 description: "Use this skill to author a complete HXL WidgetBundle (UEM body + schema.json + -meta.xml). TRIGGER when: user asks for a widget, mosaic, fragment, card, or rich UI surface for any subject, domain, feature, or entity noun; the prompt names only an entity or data shape without invoking Lightning Types, CLTs, or Apex-backed types. DO NOT TRIGGER when: the prompt explicitly says 'Lightning Type', 'CLT', 'Custom Lightning Type', 'Apex-backed type', or references '@apexClassType/...' (use platform-lightning-type-widget-coordinate); authoring a custom-LWC renderer for a Custom Lightning Type (use platform-custom-lightning-type-generate); or editing only an LWC component."
 metadata:
   version: "1.2"
+  domains: ["Platform", "Agentforce"]
   minApiVersion: "68.0"
   relatedSkills:
     - "platform-apex-generate"

package/skills/sales-agentforce-pipeline-management-configure/SKILL.md

@@ -3,6 +3,7 @@ name: sales-agentforce-pipeline-management-configure
 description: "Use to configure, set up, or repair the Sales Management agent and Agentforce Pipeline Management in a Salesforce org. Automates metadata creation for flows, prompt templates, permission sets, and data source configuration. TRIGGER when: user wants to enable Pipeline Management, configure Sales pipeline features, set up the Sales Management agent for opportunity field updates (including autonomous updates), connect enabled data sources like Einstein Conversation Insights or Einstein Activity Capture, customize opportunity stage descriptions, configure post-meeting suggestions, verify or audit configuration status, fix partially configured orgs, or troubleshoot Pipeline Management metadata issues. DO NOT TRIGGER when: user wants to build a custom agent (use agentforce-generate), configure general Agentforce tracing (use platform-tracing-agentforce-configure), work with non-Sales agents, or enable Einstein Conversation Insights or Einstein Activity Capture from scratch (provisioning is out of scope)."
 metadata:
   version: "1.0"
+  domains: ["Sales", "Agentforce"]
   minApiVersion: "67.0"
   relatedSkills:
     - "agentforce-generate"

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

@@ -3,6 +3,7 @@ name: service-digital-engagement-channel-configure
 description: "Configures and deploys enhanced chat Messaging Channels for Messaging for In-App and Web (MIAW). Use when the user needs to create, deploy, and activate a messaging channel configured with Omni-Channel Flow, Omni-Channel Queue, User, or Agentforce Service Agent routing. Generates MessagingChannel metadata, deploys it to the target org, and activates the channel with User Verification, pre-chat forms, automated responses, consent settings, and all customizable channel options via Metadata API. TRIGGER when the user mentions messaging channel, MIAW, enhanced chat, in-app messaging, web messaging setup, or references a .messagingChannel-meta.xml file. DO NOT TRIGGER when the user is configuring legacy Live Agent chat, Embedded Service deployments without messaging, or standard Omni-Channel routing rules without a messaging channel."
 metadata:
   version: "1.0"
+  domains: ["Service"]
   minApiVersion: "67.0"
   relatedSkills:
     - "automation-flow-generate"

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

@@ -3,6 +3,7 @@ name: service-digital-engagement-deployment-configure
 description: "Configures Embedded Messaging Deployments for Messaging for In-App and Web (MIAW). Use when the user needs to create a new embedded messaging deployment from scratch using Connect API with defaults, or update an existing deployment's settings using Metadata API. Produces Connect API request payloads for new deployments and EmbeddedServiceConfig metadata XML for updates. TRIGGER when the user mentions embedded messaging deployment, embedded service deployment, MIAW deployment, messaging widget setup, chat widget configuration, embedded chat deployment, or references a .EmbeddedServiceConfig-meta.xml file. DO NOT TRIGGER when the user is creating a messaging channel (use service-digital-engagement-channel-configure), configuring legacy Live Agent embedded service, or generating the JavaScript code snippet for website embedding."
 metadata:
   version: "1.0"
+  domains: ["Service"]
   minApiVersion: "67.0"
   relatedSkills:
     - "automation-flow-generate"

package/skills/service-digital-engagement-messaging-site-integrate/SKILL.md

@@ -3,6 +3,7 @@ name: service-digital-engagement-messaging-site-integrate
 description: "Integrates a Messaging for In-App and Web (MIAW) Embedded Messaging chat widget into an Experience Cloud site by patching the site's LWR or Aura page bundle, deploying, publishing, and verifying guest access. Use when the user wants to embed messaging on an Experience site, add a chat widget to a community, place the Embedded Messaging component on an LWR or Aura page, wire an embedded service deployment to a site, references the retrieved bundle artifacts (`content.json`, `homeGuestLayout.json`, or a `*.site-meta.xml` file), or automates the retrieve/patch-JSON/deploy/publish flow instead of clicking through Experience Builder. DO NOT TRIGGER when creating the messaging channel (use service-digital-engagement-channel-configure), when creating or updating the EmbeddedServiceConfig deployment (use service-digital-engagement-deployment-configure), or when generating a standalone JavaScript snippet for a non-Experience website."
 metadata:
   version: "1.0"
+  domains: ["Service", "Experience"]
   minApiVersion: "62.0"
   relatedSkills:
     - "experience-lwr-site-generate"

package/skills/service-helpagent-coordinate/SKILL.md

@@ -4,6 +4,7 @@ description: "Use to set up, configure, ground, or go live with a Salesforce Hel
 allowed-tools: Bash Read Write Edit Glob Grep WebFetch AskUserQuestion TodoWrite
 metadata:
   version: "0.9"
+  domains: ["Service", "Agentforce", "Experience"]
   minApiVersion: "67.0"
   relatedSkills:
     - "agentforce-generate"

package/skills/service-itsm-agentic-setup-cmdb-access-assign/SKILL.md

@@ -3,6 +3,7 @@ name: service-itsm-agentic-setup-cmdb-access-assign
 description: "Grant a specific user access to CMDB (Configuration Management Database) data in Service Cloud ITSM against a production or sandbox org by assigning the license-backed CMDB permission sets (Configuration Item Reader, Owner, Type Reader, Type Manager) and their permission-set licenses. Use when the user asks to give someone CMDB access, assign CMDB permission sets, grant a user the Configuration Item Reader/Owner role, or fix a CMDB 403 FUNCTIONALITY_NOT_ENABLED that a user still hits after the CMDB feature is already enabled. Triggers on: assign CMDB permission set, grant CMDB access, give user Configuration Item access, CMDB access for user, user still gets CMDB 403 after enable. DO NOT TRIGGER when: the user wants to turn on the CMDB feature or provision the ITOM tenant for the whole org (that is the CMDB feature-enable skill), only install a CMDB content bundle, work with CMDB records directly, or assign general (non-CMDB) permission sets to users (use dx-org-permission-set-assign)."
 metadata:
   version: "1.0"
+  domains: ["Service"]
   minApiVersion: "67.0"
   relatedSkills:
     - "dx-org-permission-set-assign"

package/skills/service-itsm-agentic-setup-cmdb-bundle-deploy/SKILL.md

@@ -3,6 +3,7 @@ name: service-itsm-agentic-setup-cmdb-bundle-deploy
 description: "Deploy (install) the CMDB Foundation base content bundle in Service Cloud ITSM against a production or sandbox org, after the CMDB feature is enabled. Use when the user asks to install the CMDB bundle, deploy CMDB Foundation, set up the CMDB base content, install CMDB out-of-the-box content, or finish CMDB setup with the base bundle. Triggers on: install CMDB bundle, deploy CMDB Foundation, CMDB base content, CMDB content bundle, bundleInstallation, finish CMDB setup. DO NOT TRIGGER when: the user wants to enable the CMDB feature for the org (that is the CMDB feature-enable skill), assign CMDB permission sets to a user (that is the CMDB access-assign skill), install optional non-base add-on bundles, deploy general (non-CMDB) metadata or packages, or work with CMDB records directly."
 metadata:
   version: "1.0"
+  domains: ["Service"]
   minApiVersion: "67.0"
   relatedSkills:
     - "service-itsm-agentic-setup-cmdb-access-assign"

package/skills/service-itsm-agentic-setup-cmdb-configure/SKILL.md

@@ -3,6 +3,7 @@ name: service-itsm-agentic-setup-cmdb-configure
 description: "Enable the CMDB (Configuration Management Database) feature in Service Cloud ITSM against a production or sandbox org: verify the CMDB org SKU, provision the ITOM tenant, and enable the service-cloud-itsm-cmdb-integration feature that lifts the CMDB access gate. Use when the user asks to enable CMDB, turn on the Configuration Management Database, provision the ITOM tenant, enable the CMDB feature, or fix a CMDB 403 FUNCTIONALITY_NOT_ENABLED error. Triggers on: enable CMDB feature, provision ITOM tenant, turn on CMDB, CMDB not enabled, CMDB 403 error, service-cloud-itsm-cmdb-integration. DO NOT TRIGGER when: the user only wants to assign CMDB permission sets to users, only install a CMDB content bundle, or work with CMDB records directly."
 metadata:
   version: "1.0"
+  domains: ["Service"]
   minApiVersion: "67.0"
   relatedSkills:
     - "service-itsm-agentic-setup-cmdb-access-assign"

package/skills/service-itsm-agentic-setup-cmdb-coordinate/SKILL.md

@@ -3,6 +3,7 @@ name: service-itsm-agentic-setup-cmdb-coordinate
 description: "Orchestrator skill for enabling CMDB (Configuration Management Database) end-to-end in Service Cloud ITSM against a production or sandbox org. Use when the user asks to set up CMDB, enable Configuration Management Database, configure the ITSM CMDB, onboard CMDB from scratch, wants a guided walkthrough of CMDB enablement, or asks what CMDB setup steps are available. Triggers on: set up CMDB, enable CMDB, configure CMDB, CMDB onboarding, Configuration Management Database setup, ITSM CMDB walkthrough. DO NOT TRIGGER when: the user asks about a specific CMDB sub-step directly (e.g. only installing a bundle, only assigning permission sets), CMDB record CRUD (creating CIs, relationships), Discovery/Service Graph Connector configuration, or general ITSM queries without CMDB setup intent."
 metadata:
   version: "1.0"
+  domains: ["Service"]
   relatedSkills:
     - "service-itsm-agentic-setup-cmdb-access-assign"
     - "service-itsm-agentic-setup-cmdb-bundle-deploy"

package/skills/service-itsm-agentic-setup-cmdb-discovery-configure/SKILL.md

@@ -3,6 +3,7 @@ name: service-itsm-agentic-setup-cmdb-discovery-configure
 description: "Enable CMDB Asset Discovery in Service Cloud ITSM against a production or sandbox org by turning on the service-cloud-itsm-discovery-integration feature, then grant a user the Discovery page by assigning the IT Service Discovery Manager permission set and its license — the final CMDB setup layer, run after the CMDB feature, user access, and content bundle are in place. Use when the user asks to enable CMDB discovery, turn on asset discovery, enable service-cloud-itsm-discovery-integration, grant Discovery page access, or assign the Discovery Manager permission set. Triggers on: enable CMDB discovery, turn on asset discovery, service-cloud-itsm-discovery-integration, assign Discovery Manager access, CMDB discovery not enabled. DO NOT TRIGGER when: the user wants to enable the base CMDB feature, provision the ITOM tenant, assign the four CMDB Configuration-Item permission sets, install a CMDB content bundle, or work with CMDB records directly — those are earlier CMDB layers."
 metadata:
   version: "1.0"
+  domains: ["Service"]
   minApiVersion: "67.0"
   relatedSkills:
     - "service-itsm-agentic-setup-cmdb-access-assign"

package/skills/service-itsm-incident-priority-configure/SKILL.md

@@ -3,6 +3,7 @@ name: service-itsm-incident-priority-configure
 description: "Configures the Incident Priority Matrix for Salesforce ITSM through the sf CLI — enabling or disabling the matrix, shaping the Impact x Urgency grid that derives Priority on Incident records, toggling the manual-override preference, and reading or setting the default fallback priority. Reads every value before writing, is idempotent, and requires explicit user confirmation before any mutation. Use when the user wants to view, enable, disable, set up, seed, add to, change, or remove priority matrix configuration for Incident records, change the default incident priority, or asks about incident priority setup, impact/urgency mapping, override, or the ITSM incident priority matrix. DO NOT TRIGGER for Problem or ChangeRequest priority matrices, Case priority fields, standard Priority picklists outside ITSM, SLA or milestone configuration, or enabling Incident Management itself (use the service-itsm-incident-mgmt-configure skill)."
 metadata:
   version: "1.0"
+  domains: ["Service"]
   minApiVersion: "67.0"
   cliTools:
     - tool: ["sf"]