@salesforce/afv-skills 1.65.0 → 1.65.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/afv-skills",
-  "version": "1.65.0",
+  "version": "1.65.1",
   "description": "Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools.",
   "license": "Apache-2.0",
   "files": [

package/skills/field-service-data-capture-form-deployer-configure/SKILL.md

@@ -1,8 +1,10 @@
 ---
 name: field-service-data-capture-form-deployer-configure
 description: "Assemble a Data Capture Flow from a JSON spec and deploy it to a connected Field Service org via the Tooling Flow sObject (JSON Metadata, no XML). Use when given a data-capture spec JSON and asked to build or deploy a DataCaptureFlow."
+user-invocable: false
 metadata:
   version: "1.0"
+  domains: ["Field Service"]
 ---
 
 # Build a Data Capture Form (Field Service Mobile)
@@ -176,26 +178,3 @@ This skill has **no executable scripts**. Auth checks, record reads, the `Dynami
 - **`fs-data-capture-reference`** (sibling library skill) — reference manual for hand-authoring patterns, prohibited patterns + exact deploy errors, visual polish HTML, supporting CustomObject/PermissionSet/CustomTab deploy. Read this when diagnosing a deploy error or extending the JSON field mappings.
 - **`fs-data-capture-form-designer`** — produces the spec this skill consumes (from prose or an image/PDF).
 - **`fs-data-capture-form-editor`** — patches an already-deployed flow in the org. Uses the same Tooling `Flow` JSON round-trip (GET Metadata → edit → PATCH) this skill uses to create.
-
-<!-- skill-validate: ignore-start -->
-<!-- codey:operations start -->
-## Operations Reference
-
-Operations this skill uses — routing and dependency reference.
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `check-org-auth` | verify | — | `GET /services/data/v67.0/query` | — |
-| `check-flow-name-collision` | read | — | `GET /services/data/v67.0/tooling/query` | `check-org-auth` |
-| `verify-flow-deployed` | verify | — | `GET /services/data/v67.0/tooling/query` | `deploy-flow-metadata-json` |
-| `attach-ddc-to-parent` | write | — | `POST /services/data/v67.0/sobjects/DynamicDataCapture` | `verify-flow-deployed` |
-| `verify-ddc-attached` | verify | — | `GET /services/data/v67.0/query` | `attach-ddc-to-parent` |
-| `verify-parent-object-sharing-model` | verify | — | `GET /services/data/v67.0/tooling/query` | `verify-ddc-attached` |
-| `toggle-fss-sharing-flags` | write | — | `PATCH /headless/invoke/platform/field-service-operations-setup-page/save-field-service-settings-config` | `verify-parent-object-sharing-model` |
-| `verify-fss-sharing-flags` | verify | — | `GET /services/data/v67.0/tooling/query` | `toggle-fss-sharing-flags` |
-| `list-workorder-layouts-by-profile` | read | — | `GET /services/data/v67.0/tooling/query` | `verify-fss-sharing-flags` |
-| `rollback-detach-ddc` | write | — | `DELETE /services/data/v67.0/sobjects/DynamicDataCapture/{id}` | — |
-| `deploy-flow-metadata-json` | write | — | `POST /services/data/v67.0/tooling/sobjects/Flow` | `check-flow-name-collision` |
-| `patch-layout-add-ddc-related-list` | read | — | `GET /services/data/v67.0/tooling/sobjects/Layout/{id}` | `list-workorder-layouts-by-profile` |
-<!-- codey:operations end -->
-<!-- skill-validate: ignore-end -->

package/skills/field-service-data-capture-form-designer-configure/SKILL.md

@@ -1,8 +1,10 @@
 ---
 name: field-service-data-capture-form-designer-configure
-description: "Design a Field Service Mobile Data Capture Flow from either a natural-language description OR a PDF/image of an existing paper form. Extracts field labels, types, required-state, and section structure into an intermediate JSON spec, confirms the plan with the user, then hands off to `fs-data-capture-form-deployer` for compile + deploy. Handles both input modes in one skill — prose (\"build a Field Service form for asset inspection that captures…\", \"make a DataCaptureFlow that asks the technician to…\", \"create an inventory transfer form with…\") and visual sources (\"convert this PDF to a Data Capture Flow\", \"make a Field Service form from this image\", \"turn this paper form into a DataCaptureFlow\"). Detects the input mode automatically: if the user supplies a `.pdf`, `.png`, `.jpg`, or `.jpeg` path, extract from the visual source; otherwise extract from the prose. Do NOT use this skill to patch an already-deployed flow — that's `fs-data-capture-form-editor`."
+description: "Design a Field Service Mobile Data Capture Flow from either a natural-language description OR a PDF/image of an existing paper form. Extracts field labels, types, required-state, and section structure into an intermediate JSON spec, confirms the plan with the user, then hands off to fs-data-capture-form-deployer for compile + deploy. Handles both input modes in one skill — prose ('build a Field Service form for asset inspection', 'make a DataCaptureFlow that asks the technician to…', 'create an inventory transfer form') and visual sources ('convert this PDF to a Data Capture Flow', 'make a Field Service form from this image', 'turn this paper form into a DataCaptureFlow'). Detects the input mode automatically from a .pdf/.png/.jpg/.jpeg path, else extracts from the prose. Do NOT use this skill to patch an already-deployed flow — that's fs-data-capture-form-editor."
+user-invocable: false
 metadata:
   version: "1.0"
+  domains: ["Field Service"]
 ---
 
 # Design a Data Capture Form (from prose or from an image / PDF)
@@ -106,15 +108,3 @@ After a successful deploy, the flow exists but is invisible from the Forms tab o
 
 - `reference/extraction-from-prompt.md` — prose-evidence rules for picking field types from user descriptions, screen grouping, visibility rules, outcome-elicitation, validation checklist. Used in **prose mode**.
 - `reference/extraction-from-image.md` — control-evidence rules for picking field types from rendered widgets, repeater extraction rules, screen grouping, visibility rules, outcome-elicitation, validation checklist. Used in **image / PDF mode**.
-
-<!-- skill-validate: ignore-start -->
-<!-- codey:operations start -->
-## Operations Reference
-
-Operations this skill uses — routing and dependency reference.
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `handoff-to-deployer` | write | — | → `sfs-mobile-core-experience/fs-data-capture-form-deployer` | — |
-<!-- codey:operations end -->
-<!-- skill-validate: ignore-end -->

package/skills/field-service-mobile-branding-configure/SKILL.md

@@ -1,8 +1,10 @@
 ---
 name: field-service-mobile-branding-configure
-description: "Derive a Field Service mobile app color scheme from a brand source (URL, hex codes, brand-guide paste, or color description), validate WCAG AA contrast in both light and dark mode, and apply the 14-field scheme to the org-default `FieldServiceMobileSettings` record. Trigger phrases include \"brand the mobile app\", \"apply branding to Field Service mobile\", \"update the mobile app colors\", \"use this brand guide for the app\", \"set the color scheme for the mobile app\". Do NOT use this skill for Dispatcher console / Gantt branding (`FSLQA__GanttPalette__c`), Experience Cloud `BrandingSet` records, or scheduling policy colors — out of scope."
+description: "Derive a Field Service mobile app color scheme from a brand source (URL, hex codes, brand-guide paste, or color description), validate WCAG AA contrast in both light and dark mode, and apply the 14-field scheme to the org-default FieldServiceMobileSettings record. Trigger phrases include 'brand the mobile app', 'apply branding to Field Service mobile', 'update the mobile app colors', 'use this brand guide for the app', 'set the color scheme for the mobile app'. Do NOT use this skill for Dispatcher console / Gantt branding, Experience Cloud BrandingSet records, or scheduling policy colors — out of scope."
+user-invocable: false
 metadata:
   version: "1.0"
+  domains: ["Field Service"]
 ---
 
 # Field Service Mobile Branding
@@ -129,19 +131,3 @@ Contrast validation and scheme derivation are performed by the agent inline (see
 
 - `configure-field-service-mobile` — page layouts, permissions, and `FieldServiceSettings` toggles. This skill defers branding to here, and this skill defers structural mobile config to it.
 - `fs-data-capture-form-deployer` — generates and deploys Data Capture Flow metadata.
-
-<!-- skill-validate: ignore-start -->
-<!-- codey:operations start -->
-## Operations Reference
-
-Operations this skill uses — routing and dependency reference.
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `check-org-auth` | verify | — | `GET /services/data/v63.0/query` | — |
-| `describe-fsms-object` | verify | — | `GET /services/data/v63.0/sobjects/FieldServiceMobileSettings/describe` | `check-org-auth` |
-| `query-default-fsms-record` | read | — | `GET /services/data/v63.0/query` | `describe-fsms-object` |
-| `apply-fsms-scheme` | write | — | `PATCH /services/data/v63.0/sobjects/FieldServiceMobileSettings/{id}` | `query-default-fsms-record` |
-| `verify-fsms-scheme` | verify | — | `GET /services/data/v63.0/sobjects/FieldServiceMobileSettings/{id}` | `apply-fsms-scheme` |
-<!-- codey:operations end -->
-<!-- skill-validate: ignore-end -->