@salesforce/afv-skills 1.63.0 → 1.65.0

package/skills/agentforce-wizard-ui-forecasting-analytics-components-configure/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: agentforce-wizard-ui-forecasting-analytics-components-configure
+description: "Use this skill when users want to einstein Forecasting Prediction Tuner setup (ForecastingPredictive AI application type). Trigger when users mention wizard, ui, forecasting, analytics, components."
+metadata:
+  version: "1.0"
+---
+
+# Managing Wizard Ui Forecasting Analytics Components
+
+## When to Use This Skill
+
+Einstein Forecasting Prediction Tuner setup (ForecastingPredictive AI application type). Three Aura ops — get-tuner-setup-state reads whether the predictor's AI application is provisioned; load-tuner-metadata returns the Opportunity field catalog plus the saved prediction configuration; save-tuner-metadata upserts the prediction configuration and returns the AI application id. All gate on Predictive Forecasting + Customize Application + Modify All Data. No public Connect/Tooling/Metadata alternative — the AI application record is tooling-internal.
+
+## Critical Constraints
+
+**Preconditions:**
+
+- Org has Predictive Forecasting (Einstein Forecasting Prediction) enabled. (check: `Predictive Forecasting enabled`)
+- Running user has the Customize Application user permission. (check: `USER_PERMISSION_CUSTOMIZE_APPLICATION`)
+- Running user has the Modify All Data user permission. (check: `USER_PERMISSION_MODIFY_ALL_DATA`)
+
+## Operations Reference
+
+Operations grouped by purpose. Use these as the building blocks for the workflows above.
+
+### Summary
+
+| Operation | Purpose | Status | Call | Depends on |
+|-----------|---------|--------|------|------------|
+| `forecasting-prediction-tuner-setup-flow-controller-get-tuner-setup-state` | read | implemented | `GET /headless/invoke/analytics/forecasting-analytics/get-tuner-setup-state` | — |
+| `forecasting-prediction-tuner-setup-flow-controller-load-tuner-metadata` | read | implemented | `GET /headless/invoke/analytics/forecasting-analytics/load-tuner-metadata` | `forecasting-prediction-tuner-setup-flow-controller-get-tuner-setup-state` |
+| `forecasting-prediction-tuner-setup-flow-controller-save-tuner-metadata` | write | implemented | `PATCH /headless/invoke/analytics/forecasting-analytics/save-tuner-metadata` | `forecasting-prediction-tuner-setup-flow-controller-load-tuner-metadata` |
+
+### Read operations
+
+#### `forecasting-prediction-tuner-setup-flow-controller-get-tuner-setup-state`
+
+Read whether the ForecastingPredictive AI application is provisioned. Returns hasAIApplication=true when the AI application exists with a valid id; false blocks downstream tuner steps until upstream Einstein/AI application setup runs.
+
+**Call:** `GET /headless/invoke/analytics/forecasting-analytics/get-tuner-setup-state`   — status: `implemented`
+
+**Output:** A single boolean field hasAIApplication. True when a ForecastingPredictive AI application exists in the org with a valid id; false otherwise.
+
+#### `forecasting-prediction-tuner-setup-flow-controller-load-tuner-metadata`
+
+Load Opportunity custom fields, picklist fields paired with their values (CurrencyIsoCode excluded), the RecordTypeId field with RecordTypeInfo entries when custom record types exist, and the org's saved prediction configuration (null on a fresh org).
+
+**Call:** `GET /headless/invoke/analytics/forecasting-analytics/load-tuner-metadata`   — status: `implemented`
+
+**Depends on:** `forecasting-prediction-tuner-setup-flow-controller-get-tuner-setup-state`
+
+**Output:** Carries availableOppFields (Opportunity custom field list), oppPicklistFieldsAndValues (picklist fields + values plus RecordTypeId+RecordTypeInfo when custom record types exist), and predictionConfig (current saved prediction configuration or null on a fresh org).
+
+### Write operations
+
+#### `forecasting-prediction-tuner-setup-flow-controller-save-tuner-metadata`
+
+Upsert the org's prediction configuration. Accepts a Map<String,Object> under key `predictionConfig`, but the controller first re-serializes it through a string-valued map type — every value is string-coerced — before deserializing into the prediction-config object, so send string-valued fields (e.g. `excludedFields` as a JSON-encoded string, not a native array). Updates when the config carries both AIApplicationId and PredictionDefinitionId, else creates the ForecastingPredictive AI application. Returns the AI application id. Round-trip predictionConfig from the load-tuner-metadata read on partial mutations to preserve unset fields.
+
+**Call:** `PATCH /headless/invoke/analytics/forecasting-analytics/save-tuner-metadata`   — status: `implemented`
+
+**Depends on:** `forecasting-prediction-tuner-setup-flow-controller-load-tuner-metadata`
+
+**Output:** String — the AI application id (aiAppId) of the upserted ForecastingPredictive AI application record. Use as evidence the predictor is now provisioned (a subsequent get-tuner-setup-state read should return hasAIApplication=true).

package/skills/agentforce-wizard-ui-sales-einstein-components-configure/SKILL.md

@@ -0,0 +1,46 @@
+---
+name: agentforce-wizard-ui-sales-einstein-components-configure
+description: "Use this skill when users want to wizard subset of the Sales Email Assistant setup and filter-row picklist operations. Trigger when users mention wizard, ui, sales, einstein, components."
+metadata:
+  version: "1.0"
+---
+
+# Managing Wizard Ui Sales Einstein Components
+
+## When to Use This Skill
+
+Wizard subset of the Sales Email Assistant setup and filter-row picklist operations. Two boolean org-pref toggles (EinsteinGPTSalesEmailsPref and ORG_PREFERENCE_CALL_SUMMARIZATION) plus a filter-row picklist read for the filter-row UI. The sales-email toggle, when Discovery Framework is off and enabled=true, performs an atomic bulk pref write flipping OnlyUseBuilderPrompts to false alongside the pref write; both toggles echo the saved Boolean. The picklist read returns {label, value} pairs; fieldApiName='RecordTypeId' branches to return the object's record types instead (label = record-type label, value = record-type id). Sibling SOR GPTEmailGeneration covers the remaining 7 toggles + composite getState read on this setup page.
+
+## Operations Reference
+
+Operations grouped by purpose. Use these as the building blocks for the workflows above.
+
+### Summary
+
+| Operation | Purpose | Status | Call | Depends on |
+|-----------|---------|--------|------|------------|
+| `filter-row-picklist-controller-get-picklist-values` | read | implemented | `GET /headless/invoke/einstein/sales-einstein/filter-row-picklist/get-picklist-values` | — |
+| `sales-email-assistant-setup-controller-handle-sales-email-pref-toggle` | write | implemented | `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-email-pref-toggle` | — |
+| `sales-email-assistant-setup-controller-handle-sales-call-summarization-pref-toggle` | write | implemented | `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-call-summarization-pref-toggle` | — |
+
+### Read operations
+
+#### `filter-row-picklist-controller-get-picklist-values`
+
+Returns the available picklist values as {label, value} pairs for a field on an object, used to populate filter-row options. When the field is 'RecordTypeId', returns the object's record types instead (label = record-type label, value = record-type id). Returns an empty list when the object or field is not supplied. Requires View Setup access.
+
+**Call:** `GET /headless/invoke/einstein/sales-einstein/filter-row-picklist/get-picklist-values`   — status: `implemented`
+
+### Write operations
+
+#### `sales-email-assistant-setup-controller-handle-sales-email-pref-toggle`
+
+Sets EinsteinGPTSalesEmailsPref to `enabled`. When Discovery Framework is off and enabled=true, an atomic bulk pref write also flips OnlyUseBuilderPrompts to false (open-prompt defaults on); otherwise the write routes through the Discovery Framework path for the Sales Email feature. Returns Boolean. AURA-IS-CANONICAL: pref absent from Metadata Settings types and from Tooling Organization columns (source-verified).
+
+**Call:** `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-email-pref-toggle`   — status: `implemented`
+
+#### `sales-email-assistant-setup-controller-handle-sales-call-summarization-pref-toggle`
+
+Enables or disables the Sales Call Summarization org preference. Writing the preference requires Setup administrator access, and the saved boolean value is returned.
+
+**Call:** `PATCH /headless/invoke/platform/gptemail-generation/handle-sales-call-summarization-pref-toggle`   — status: `implemented`

package/skills/automation-company-profile-info-query/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: automation-company-profile-info-query
+description: "Use this skill when users want to read the org's company profile — name, address, primary contact, default locale, language, time zone, fiscal year start, and org type — by querying the Organization singleton sObject (read_company_profile step). Trigger when users mention company, profile, info, company profile info."
+metadata:
+  version: "1.0"
+---
+
+# Querying Company Profile Info
+
+## When to Use This Skill
+
+Read the org's company profile — name, address, primary contact, default locale, language, time zone, fiscal year start, and org type — by querying the Organization singleton sObject (read_company_profile step). An agent can report these settings without the admin opening the Setup page, provided the user has the "View Setup and Configuration" (ViewSetup) permission. To CHANGE any company-profile value, navigate to the Setup page via view_url and edit in the UI; write automation is intentionally out of scope for this skill.
+
+## Critical Constraints
+
+**Preconditions:**
+
+- Reading the company profile requires the "View Setup and Configuration" (ViewSetup) user permission. Without it the running user cannot access Setup and the company-profile context is not meaningfully retrievable.
+ (check: `USER_HAS_VIEW_SETUP`)
+
+## Operations Reference
+
+Operations grouped by purpose. Use these as the building blocks for the workflows above.
+
+### Summary
+
+| Operation | Purpose | Status | Call | Depends on |
+|-----------|---------|--------|------|------------|
+| `view_CompanyProfileInfo_1` | read | — | `CompanyProfileInfo.view` | — |
+| `read_company_profile` | read | — | `GET /services/data/v66.0/query` | — |
+
+### Read operations
+
+#### `view_CompanyProfileInfo_1`
+
+Navigate to the CompanyProfileInfo Setup page (no programmatic API). The agent should open view_url for the user to configure manually.
+
+**Call:** `CompanyProfileInfo.view`
+
+#### `read_company_profile`
+
+Read the org's company profile — name, address, primary contact, default locale, language, time zone, fiscal year start, and org type — by querying the `Organization` singleton sObject via SOQL. The org has exactly one Organization record, so the query returns a single row. This lets an agent report company-profile settings WITHOUT the admin opening the Setup page. The `FROM Organization` clause is fixed by this step — only the SELECT field list is variable — so the read is always scoped to the Organization entity. Read-only: to CHANGE any of these values, navigate to the Setup page (view_CompanyProfileInfo_1) and edit in the UI — write automation for the company profile is intentionally out of scope for this skill.
+
+
+**Call:** `GET /services/data/v66.0/query`
+
+**Inputs:**
+
+- `fields` *(`String`)* — Comma-separated SELECT field list for the Organization query. The `FROM Organization` clause is fixed by the step and is NOT part of this input — you choose the fields, never the object. Omit to use the default full company-profile field set below. Add or drop fields as the admin's question requires; note single-currency orgs do not expose DefaultCurrencyIsoCode (querying it errors on such orgs).
+
+- `q` *(`string`)*