@salesforce/afv-skills 1.65.0 → 1.66.0

package/skills/experience-briefcase-configure/SKILL.md

@@ -1,287 +0,0 @@
----
-name: experience-briefcase-configure
-description: "Use this skill when users want to manage Briefcase Definitions for offline mobile data priming. Trigger when users mention briefcase."
-metadata:
-  version: "1.0"
-  accessCheck: "(Briefcase.userCanEditBriefcase) || (Briefcase.userCanViewBriefcase)"
----
-
-# Managing Briefcase
-
-## When to Use This Skill
-
-Manage Briefcase Definitions for offline mobile data priming. This setup page lets admins create, edit, activate/deactivate, and delete Briefcase definitions that control which records are cached on mobile devices for offline use. It also manages briefcase rule configurations, user/profile assignments, connected app associations, and profile-level briefcase regeneration. Use this SOR when a user needs to configure offline data availability for Salesforce mobile apps.
-
-## Critical Constraints
-
-**Preconditions:**
-
-- User must have Briefcase EditBriefcase access (check: `Edit Briefcase permission`)
-- User must have Briefcase ViewBriefcase access (check: `View Briefcase permission`)
-
-**Destructive operations — require explicit user confirmation:**
-
-- **`delete-briefcase-tooling`** — Permanently delete a Briefcase definition by its Salesforce ID via the Tooling API.
-  - Rollback: Cannot be undone — the Briefcase definition and all its rules/assignments are permanently removed
-
-## Verification Checklist
-
-After every write operation, confirm the effect by re-reading state:
-
-- After `get-briefcase-list-and-guardrail-org-values`: call `verify-acknowledge-hyperforce` (`GET /headless/invoke/platform/briefcase/get-briefcase-list-and-guardrail-org-values`)
-- After `create-briefcase-tooling`: call `verify-create-briefcase-tooling` (`GET /services/data/v67.0/tooling/query`)
-- After `update-briefcase-tooling`: call `verify-update-briefcase-tooling` (`GET /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}`)
-- After `update-briefcase-state-tooling`: call `verify-update-briefcase-state-tooling` (`GET /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}`)
-- After `delete-briefcase-tooling`: call `verify-delete-briefcase-tooling` (`GET /services/data/v67.0/tooling/query`)
-- After `update-briefcase-assignments-sobject`: call `verify-update-briefcase-assignments-sobject` (`GET /services/data/v67.0/query`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `update-briefcase-connected-apps` | write | implemented | `PATCH /headless/invoke/platform/briefcase/update-briefcase-connected-apps` | — |
-| `get-apps-list-for-briefcase` | read | implemented | `GET /headless/invoke/platform/briefcase/get-apps-list-for-briefcase` | — |
-| `get-briefcase-list-and-guardrail-org-values` | read | implemented | `GET /headless/invoke/platform/briefcase/get-briefcase-list-and-guardrail-org-values` | — |
-| `acknowledge-hyperforce-for-high-volume-priming` | write | implemented | `PATCH /headless/invoke/platform/briefcase/acknowledge-hyperforce-for-high-volume-priming` | — |
-| `get-briefcase` | read | implemented | `GET /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}` | — |
-| `verify-acknowledge-hyperforce` | verify | implemented | `GET /headless/invoke/platform/briefcase/get-briefcase-list-and-guardrail-org-values` | `get-briefcase-list-and-guardrail-org-values` |
-| `create-briefcase-tooling` | write | implemented | `POST /services/data/v67.0/tooling/sobjects/BriefcaseDefinition` | `get-briefcase-list-and-guardrail-org-values`, `get-apps-list-for-briefcase` |
-| `verify-create-briefcase-tooling` | verify | implemented | `GET /services/data/v67.0/tooling/query` | `create-briefcase-tooling` |
-| `update-briefcase-tooling` | write | implemented | `PATCH /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}` | `get-briefcase-list-and-guardrail-org-values` |
-| `verify-update-briefcase-tooling` | verify | implemented | `GET /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}` | `update-briefcase-tooling` |
-| `update-briefcase-state-tooling` | write | implemented | `PATCH /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}` | `get-briefcase-list-and-guardrail-org-values` |
-| `verify-update-briefcase-state-tooling` | verify | implemented | `GET /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}` | `update-briefcase-state-tooling` |
-| `delete-briefcase-tooling` | delete | implemented | `DELETE /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}` | `get-briefcase-list-and-guardrail-org-values` |
-| `verify-delete-briefcase-tooling` | verify | implemented | `GET /services/data/v67.0/tooling/query` | `delete-briefcase-tooling` |
-| `update-briefcase-assignments-sobject` | write | implemented | `POST /services/data/v67.0/sobjects/BriefcaseAssignment` | `get-briefcase-list-and-guardrail-org-values` |
-| `verify-update-briefcase-assignments-sobject` | verify | implemented | `GET /services/data/v67.0/query` | `update-briefcase-assignments-sobject` |
-
-### Dependency graph
-
-```mermaid
-graph TD
-  update_briefcase_connected_apps["update-briefcase-connected-apps (write)"]
-  get_apps_list_for_briefcase["get-apps-list-for-briefcase (read)"]
-  get_briefcase_list_and_guardrail_org_values["get-briefcase-list-and-guardrail-org-values (read)"]
-  acknowledge_hyperforce_for_high_volume_priming["acknowledge-hyperforce-for-high-volume-priming (write)"]
-  get_briefcase["get-briefcase (read)"]
-  verify_acknowledge_hyperforce["verify-acknowledge-hyperforce (verify)"]
-  create_briefcase_tooling["create-briefcase-tooling (write)"]
-  verify_create_briefcase_tooling["verify-create-briefcase-tooling (verify)"]
-  update_briefcase_tooling["update-briefcase-tooling (write)"]
-  verify_update_briefcase_tooling["verify-update-briefcase-tooling (verify)"]
-  update_briefcase_state_tooling["update-briefcase-state-tooling (write)"]
-  verify_update_briefcase_state_tooling["verify-update-briefcase-state-tooling (verify)"]
-  delete_briefcase_tooling["delete-briefcase-tooling (delete)"]
-  verify_delete_briefcase_tooling["verify-delete-briefcase-tooling (verify)"]
-  update_briefcase_assignments_sobject["update-briefcase-assignments-sobject (write)"]
-  verify_update_briefcase_assignments_sobject["verify-update-briefcase-assignments-sobject (verify)"]
-  get_briefcase_list_and_guardrail_org_values --> verify_acknowledge_hyperforce
-  get_briefcase_list_and_guardrail_org_values --> create_briefcase_tooling
-  get_apps_list_for_briefcase --> create_briefcase_tooling
-  create_briefcase_tooling --> verify_create_briefcase_tooling
-  get_briefcase_list_and_guardrail_org_values --> update_briefcase_tooling
-  update_briefcase_tooling --> verify_update_briefcase_tooling
-  get_briefcase_list_and_guardrail_org_values --> update_briefcase_state_tooling
-  update_briefcase_state_tooling --> verify_update_briefcase_state_tooling
-  get_briefcase_list_and_guardrail_org_values --> delete_briefcase_tooling
-  delete_briefcase_tooling --> verify_delete_briefcase_tooling
-  get_briefcase_list_and_guardrail_org_values --> update_briefcase_assignments_sobject
-  update_briefcase_assignments_sobject --> verify_update_briefcase_assignments_sobject
-```
-
-### Read operations
-
-#### `get-apps-list-for-briefcase`
-
-Get apps list for briefcase.
-
-**Call:** `GET /headless/invoke/platform/briefcase/get-apps-list-for-briefcase`   — status: `implemented`
-
-#### `get-briefcase-list-and-guardrail-org-values`
-
-Get briefcase list and guardrail org values.
-
-**Call:** `GET /headless/invoke/platform/briefcase/get-briefcase-list-and-guardrail-org-values`   — status: `implemented`
-
-#### `get-briefcase`
-
-Retrieve a single Briefcase definition by its ID via the Tooling API. Returns full Metadata including briefcaseRules, filters, and relatedRules.
-
-**Call:** `GET /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}`   — status: `implemented`
-
-**Inputs:**
-
-- `id` *(`String`)* — The Salesforce ID of the BriefcaseDefinition to retrieve. Source: query BriefcaseDefinition sObject or output of get-briefcase-list-and-guardrail-org-values.
-
-**Output:** String representation of the Briefcase definition including masterLabel, developerName, description, id, active, type, briefcaseRules, assignments, connectedAppIds, syncStatus
-
-### Write operations
-
-#### `update-briefcase-connected-apps`
-
-Update briefcase connected apps.
-
-**Call:** `PATCH /headless/invoke/platform/briefcase/update-briefcase-connected-apps`   — status: `implemented`
-
-**Inputs:**
-
-- `briefcaseData` *(`Map<String, Object>`)* — Value for briefcase data.
-
-#### `acknowledge-hyperforce-for-high-volume-priming`
-
-Acknowledge hyperforce for high volume priming.
-
-**Call:** `PATCH /headless/invoke/platform/briefcase/acknowledge-hyperforce-for-high-volume-priming`   — status: `implemented`
-
-#### `create-briefcase-tooling`
-
-Create a new Briefcase definition with rules, assignments, and connected app associations via the Tooling API. The Metadata field accepts the full BriefcaseDefinition shape including briefcaseRules and filters.
-
-**Call:** `POST /services/data/v67.0/tooling/sobjects/BriefcaseDefinition`   — status: `implemented`
-
-**Inputs:**
-
-- `FullName` *(`String`)* — The developer name (unique identifier) for the Briefcase definition.
-- `Metadata` *(`Object`)* — BriefcaseDefinition metadata. Required fields: masterLabel (string), briefcaseRules (array, at least one rule). Each BriefcaseRule requires: targetEntity (API name of the sObject, e.g. 'Account'), queryScope (allowed values: 'Everything', 'Mine'; additionally 'AssignedToMe' is supported only for the ServiceAppointment entity — source: BriefcaseRule.QueryScope restrictedPicklist). Optional rule fields: briefcaseRuleFilters (array — each filter requires targetEntityField, filterOperator (short form: 'e'=equals, 's'=startsWith, 'd'=endsWith, 'l'=lessThan, 'g'=greaterThan, 'm'=lessThanOrEqual, 'h'=greaterThanOrEqual; NOTE: 'n'=notEquals is NOT supported for Briefcase filters — source: BriefcaseRuleFilter.FilterOperator restrictedPicklist), filterValue, filterSeqNumber (required, 1-based index)), filterLogic (REQUIRED when briefcaseRuleFilters present, e.g. '1' or '1 AND 2'), isAscendingOrder (boolean), orderBy (field name), recordLimit (integer), relatedRules (array of nested related rules — each requires targetEntity, queryScope, relationshipField, relationshipType; relationshipType is 'ParentToChild' for parent→child lookups or 'ChildToParent' for child→parent lookups — source: BriefcaseRule.RelationshipType restrictedPicklist; multiple relatedRules under one parent rule are supported). Operator+field compatibility is validated server-side — not all operators work with all field types (error: 'The combination of the field X and the operator Y for the entity Z is invalid'). Optional top-level: description (string), isActive (boolean, default false), type ('Standard' (default) or 'HighVolume' — source: BriefcaseDefinition.Type restrictedPicklist; MobileAppSync excluded for agent use).
-
-**Depends on:** `get-briefcase-list-and-guardrail-org-values`, `get-apps-list-for-briefcase`
-
-**Rollback:** Delete the created Briefcase using delete-briefcase-tooling with the record Id
-
-#### `update-briefcase-tooling`
-
-Update an existing Briefcase definition's metadata (label, description, rules, filters) via the Tooling API. Note that PATCH requires the full Metadata object (complete replacement, not partial).
-
-**Call:** `PATCH /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}`   — status: `implemented`
-
-**Inputs:**
-
-- `id` *(`String`)* — The Salesforce ID of the BriefcaseDefinition to update. Source: query BriefcaseDefinition sObject or output of get-briefcase-list-and-guardrail-org-values.
-- `Metadata` *(`Object`)* — Full BriefcaseDefinition metadata (complete replacement): masterLabel, description, briefcaseRules, isActive. Must include all fields — omitted fields revert to defaults.
-
-**Depends on:** `get-briefcase-list-and-guardrail-org-values`
-
-**Rollback:** Call update-briefcase-tooling again with the previous field values retrieved from get-briefcase
-
-#### `update-briefcase-state-tooling`
-
-Activate or deactivate a Briefcase definition by updating the isActive flag in its Metadata via the Tooling API.
-
-**Call:** `PATCH /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}`   — status: `implemented`
-
-**Inputs:**
-
-- `id` *(`String`)* — The Salesforce ID of the BriefcaseDefinition. Source: query BriefcaseDefinition sObject.
-- `Metadata` *(`Object`)* — Full Metadata with isActive set to true (activate) or false (deactivate). Must include briefcaseRules and masterLabel even for state-only changes (full replacement semantics).
-
-**Depends on:** `get-briefcase-list-and-guardrail-org-values`
-
-**Rollback:** Call update-briefcase-state-tooling with the opposite active value to revert
-
-#### `update-briefcase-assignments-sobject`
-
-Manage Briefcase assignments by creating or deleting BriefcaseAssignment records. Each record links a BriefcaseDefinition to a user, group, or profile. Create one record per assignee; delete to unassign.
-
-**Call:** `POST /services/data/v67.0/sobjects/BriefcaseAssignment`   — status: `implemented`
-
-**Inputs:**
-
-- `BriefcaseId` *(`String`)* — The ID of the BriefcaseDefinition to assign.
-- `UserOrGroupId` *(`String`)* — Polymorphic reference — the ID of the User, Group, or Profile to assign. Accepts any of the three entity types in a single field.
-
-**Depends on:** `get-briefcase-list-and-guardrail-org-values`
-
-**Rollback:** DELETE /services/data/v67.0/sobjects/BriefcaseAssignment/{id} to remove the assignment
-
-### Verify operations
-
-#### `verify-acknowledge-hyperforce`
-
-Check whether the org has acknowledged Hyperforce AND actually has HighVolume capacity enabled. Reads briefcaseHyperforceAck flag and HighVolume guardrail limits from get-briefcase-list-and-guardrail-org-values output. If ack is true but limits are 0, the org does not support HighVolume — do NOT proceed.
-
-**Call:** `GET /headless/invoke/platform/briefcase/get-briefcase-list-and-guardrail-org-values`   — status: `implemented`
-
-**Depends on:** `get-briefcase-list-and-guardrail-org-values`
-
-#### `verify-create-briefcase-tooling`
-
-Confirm the new Briefcase was created by querying via Tooling SOQL.
-
-**Call:** `GET /services/data/v67.0/tooling/query`   — status: `implemented`
-
-**Inputs:**
-
-- `q` *(`string`)*
-
-**Depends on:** `create-briefcase-tooling`
-
-#### `verify-update-briefcase-tooling`
-
-Confirm the Briefcase update landed by re-reading the definition via Tooling API.
-
-**Call:** `GET /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}`   — status: `implemented`
-
-**Inputs:**
-
-- `id` *(`String`)* — The Salesforce ID of the BriefcaseDefinition to verify. Source: the id used in update-briefcase-tooling.
-
-**Depends on:** `update-briefcase-tooling`
-
-#### `verify-update-briefcase-state-tooling`
-
-Confirm activation/deactivation by re-reading the BriefcaseDefinition via Tooling API.
-
-**Call:** `GET /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}`   — status: `implemented`
-
-**Inputs:**
-
-- `id` *(`String`)* — The Salesforce ID of the BriefcaseDefinition to verify. Source: the id used in update-briefcase-state-tooling.
-- `fields` *(`string`)*
-
-**Depends on:** `update-briefcase-state-tooling`
-
-#### `verify-delete-briefcase-tooling`
-
-Confirm deletion by querying via Tooling SOQL and verifying the entry is gone.
-
-**Call:** `GET /services/data/v67.0/tooling/query`   — status: `implemented`
-
-**Inputs:**
-
-- `developerName` *(`String`)* — The DeveloperName of the BriefcaseDefinition to verify was deleted. Source: the developerName of the record passed to delete-briefcase-tooling.
-- `q` *(`string`)*
-
-**Depends on:** `delete-briefcase-tooling`
-
-#### `verify-update-briefcase-assignments-sobject`
-
-Confirm assignment changes by querying BriefcaseAssignment via SOQL.
-
-**Call:** `GET /services/data/v67.0/query`   — status: `implemented`
-
-**Inputs:**
-
-- `q` *(`string`)*
-
-**Depends on:** `update-briefcase-assignments-sobject`
-
-### Destructive operations
-
-#### `delete-briefcase-tooling`
-
-Permanently delete a Briefcase definition by its Salesforce ID via the Tooling API.
-
-**Call:** `DELETE /services/data/v67.0/tooling/sobjects/BriefcaseDefinition/{id}`   — status: `implemented`
-
-**Inputs:**
-
-- `id` *(`String`)* — The Salesforce ID of the BriefcaseDefinition to delete. Source: query BriefcaseDefinition sObject.
-
-**Depends on:** `get-briefcase-list-and-guardrail-org-values`
-
-**Rollback:** Cannot be undone — the Briefcase definition and all its rules/assignments are permanently removed

package/skills/experience-community-flexi-page-list-create/SKILL.md

@@ -1,74 +0,0 @@
----
-name: experience-community-flexi-page-list-create
-description: "Use this skill when users want to browse and manage FlexiPage records that drive Experience Cloud (Communities) Builder pages — the records whose Type sits in the FlexiPageType.Container=COMMUNITIES subset (CommObjectPage, CommRecordPage, CommLoginPage, CommThemeLayoutPage, CommSearchResultPage, etc.). Trigger when users mention community, flexi, page, list, community flexi page list."
-metadata:
-  version: "1.0"
----
-
-# Managing Community Flexi Page List
-
-## When to Use This Skill
-
-Browse and manage FlexiPage records that drive Experience Cloud (Communities) Builder pages — the records whose Type sits in the FlexiPageType.Container=COMMUNITIES subset (CommObjectPage, CommRecordPage, CommLoginPage, CommThemeLayoutPage, CommSearchResultPage, etc.). The Aloha Setup page at view_url renders this list filtered server-side; for programmatic CRUD use the Tooling sObject FlexiPage (read-flexi-page-list, read-flexi-page, write-flexi-page). Page-content edits are authored in the Lightning App Builder, not by direct sObject PATCH on the record's Metadata field. Org gates: Experience Cloud sites enabled, Experience Cloud pages enabled; user gates: view Experience Cloud pages (read), create Experience Cloud pages (write).
-
-## Critical Constraints
-
-**Preconditions:**
-
-- Networks (Experience Sites / Communities) feature must be enabled on the org. (check: `Experience Cloud sites enabled || Experience Cloud sites enabled`)
-- FlexiPage feature must be enabled for Communities on the org. (check: `Experience Cloud pages enabled`)
-- Org must NOT be a Help-Center-Networks-only org (the page is hidden in that mode). (check: `!Help Center networks-only mode`)
-- User must hold View Setup to load the page; Customize Application (or equivalent) is needed for write/delete row actions and Tooling FlexiPage CRUD. (check: `UserPermissions.ViewSetup; view Experience Cloud pages; create Experience Cloud pages (writes)`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `view_CommunityFlexiPageList_1` | read | — | `CommunityFlexiPageList.view` | — |
-| `read-flexi-page-list` | read | — | `GET /services/data/v66.0/tooling/query` | — |
-| `read-flexi-page` | read | — | `GET /services/data/v66.0/tooling/sobjects/FlexiPage/{id}` | `read-flexi-page-list` |
-| `write-flexi-page` | write | — | `POST /services/data/v66.0/tooling/sobjects/FlexiPage` | — |
-
-### Read operations
-
-#### `view_CommunityFlexiPageList_1`
-
-Open the Aloha Setup list view at view_url (PlatformTools > FeatureSettings > Networks). Renders FlexiPage records with FlexiPageType.Container=COMMUNITIES, with row-level Edit (App Builder) and Delete actions. For programmatic record access use steps read-flexi-page-list, read-flexi-page, write-flexi-page.
-
-**Call:** `CommunityFlexiPageList.view`
-
-#### `read-flexi-page-list`
-
-List Community FlexiPage records via Tooling SOQL filtered to FlexiPageType.Container=COMMUNITIES. Sibling FlexiPageList SOR's list_FlexiPage_1 is the unfiltered analog.
-
-**Call:** `GET /services/data/v66.0/tooling/query`
-
-**Output:** QueryResult.records[] of FlexiPage rows: Id, DeveloperName, MasterLabel, Type, NamespacePrefix, LastModifiedDate. The agent should call Tooling.describe(FlexiPage).Type for the authoritative community subset rather than relying on this step's hard-coded WHERE list, since the Container=COMMUNITIES set evolves across releases. Note LastModifiedById is not a valid FlexiPage column on the Tooling entity — resolve the actor via a follow-up SOQL against User if needed.
-
-#### `read-flexi-page`
-
-Read a single FlexiPage record by Id via the Tooling sObject API. Apply this once the agent has an Id from read-flexi-page-list or another source.
-
-**Call:** `GET /services/data/v66.0/tooling/sobjects/FlexiPage/{id}`
-
-**Depends on:** `read-flexi-page-list`
-
-**Output:** Tooling FlexiPage record. GET without ?fields returns the full record: Id, FullName, DeveloperName, MasterLabel, Type, Description, NamespacePrefix, ManageableState, ParentFlexiPage, EntityDefinitionId, LastModifiedDate, LastModifiedById, CreatedDate, SystemModstamp, plus the load-bearing Metadata sub-object. Metadata carries masterLabel, type, sobjectType, description, events[], flexiPageRegions[], parentFlexiPage, platformActionlist, quickActionList, template, and urls. flexiPageRegions[] elements carry name, type (Region), mode, appendable, prependable, replaceable, and itemInstances[] (each with a componentInstance authored via the Lightning App Builder — do not construct these from prose). template.name references an existing platform-bundled template (for example one:utilityBarTemplateDesktop on UtilityBar records, or flexipage:defaultTemplate on Community pages). To project a smaller payload, append ?fields=Id,MasterLabel,Type,...
-
-### Write operations
-
-#### `write-flexi-page`
-
-Create or update a Community-context FlexiPage record via the Tooling sObject API. On POST the wire contract requires a top-level FullName and a Metadata sub-object; Metadata must carry masterLabel, type (a FlexiPageType value in the COMMUNITIES subset — for example CommObjectPage or CommRecordPage), a non-empty flexiPageRegions[] array, and template.name referencing an existing platform-bundled template. sobjectType is set on record-page-type variants (for example CommObjectPage with sobjectType Account). PATCH also requires the Metadata sub-object — sending just top-level scalar field updates without Metadata returns 400 REQUIRED_FIELD_MISSING. The item-instance component graph inside flexiPageRegions[] is authored in the Lightning App Builder after this step provisions the record — do not synthesize componentInstance bodies from prose.
-
-**Call:** `POST /services/data/v66.0/tooling/sobjects/FlexiPage`
-
-**Output:** Tooling sObject create response — { id, success, errors[] } — on POST, and an empty 204 on PATCH. On create, only the shell record is provisioned; the flexiPageRegions[].itemInstances[] component graph is authored later in the Lightning App Builder. Verify the record shape post-write by calling read-flexi-page with the returned Id.
-
-**Rollback:** Delete the created FlexiPage via DELETE /services/data/v66.0/tooling/sobjects/FlexiPage/{id}. Confirmed reachable — DELETE on a non-existent Id returns 404 NOT_FOUND with a well-formed error body, so the surface exists and is idempotent from the caller's perspective. No separate rollback step is emitted because deletion is not a first-class customer workflow for this SOR — it is the undo verb for a mistaken create.
-
-**Notes:** patch_semantics: PATCH requires the full Metadata sub-object. Sending a partial Metadata does not merge with the persisted body — always read the current record first, mutate in-memory, and PATCH the full Metadata to avoid dropping fields.; fullname_immutability: FullName is set once on POST and is the record's stable developer-name identifier. Renaming requires deleting and recreating.; invalid_type_returns_500: An invalid FlexiPage type value (a string outside the FlexiPageType enum) returns 500 UNKNOWN_EXCEPTION rather than a validated 400 — this is a Core defect surface, not a documented contract. Agents constructing type values should pick from the community subset enumerated in agent_description.; empty_region_array_rejected: Metadata.flexiPageRegions must be a non-empty array. An empty [] is rejected with 400 "Required field is missing: flexiPageRegions" even though the key is present.; template_name_must_exist: Metadata.template.name must reference an existing platform-bundled template FullName. Templates are not created via this SOR.

package/skills/experience-community-template-definition-list-query/SKILL.md

@@ -1,48 +0,0 @@
----
-name: experience-community-template-definition-list-query
-description: "Use this skill when users want to lists Experience Cloud community templates (Aloha, Build Your Own, Customer Service, Help Center, Partner Central, etc.) available in the org. Trigger when users mention community, template, definition, list, community template definition list."
-metadata:
-  version: "1.0"
----
-
-# Querying Community Template Definition List
-
-## When to Use This Skill
-
-Lists Experience Cloud community templates (Aloha, Build Your Own, Customer Service, Help Center, Partner Central, etc.) available in the org. Use the programmatic step `read-get-community-template-collection` to retrieve `{publisher, templateName}` per template via `GET /connect/communities/templates`. The setup_page step is the manual UI fallback at `/lightning/setup/CommunityTemplateDefinitionList/home`. Read-only — template creation is a Salesforce-published artifact, not a customer-org operation.
-
-## Critical Constraints
-
-**Preconditions:**
-
-- Digital Experiences (Communities/Networks) is enabled or has been enabled at least once in the org. (check: `Experience Cloud sites enabled || Experience Cloud sites enabled`)
-- The org is not on a Help-Center-only edition (which suppresses the template list). (check: `!Help Center networks-only mode`)
-- Community Template feature is available to this org. (check: `Community templates enabled`)
-- User has permission to create community templates. (check: `create community template permission`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `view_CommunityTemplateDefinitionList_1` | read | — | `CommunityTemplateDefinitionList.view` | — |
-| `read-get-community-template-collection` | read | implemented | `GET /services/data/v66.0/connect/communities/templates` | — |
-
-### Read operations
-
-#### `view_CommunityTemplateDefinitionList_1`
-
-Open the Setup page UI at view_url for manual template browsing. Programmatic alternative: step `read-get-community-template-collection` (GET /connect/communities/templates) returns the same template list as JSON.
-
-**Call:** `CommunityTemplateDefinitionList.view`
-
-#### `read-get-community-template-collection`
-
-List the community templates available in this org. Returns `{templates: array<{publisher, templateName}>, total: integer}`. No parameters; pulls the org-context template registry.
-
-**Call:** `GET /services/data/v66.0/connect/communities/templates`   — status: `implemented`
-
-**Output:** `CommunityTemplateCollectionRepresentation` — `{templates: array<CommunityTemplateRepresentation{publisher: string, templateName: string}>, total: integer}`.

package/skills/experience-community-theme-definition-list-query/SKILL.md

@@ -1,38 +0,0 @@
----
-name: experience-community-theme-definition-list-query
-description: "Use this skill when users want to lists Experience Cloud theme definitions (CommunityThemeDefinition metadata type) for the Setup > Networks > Theme Definitions page. Trigger when users mention community, theme, definition, list, community theme definition list."
-metadata:
-  version: "1.0"
----
-
-# Querying Community Theme Definition List
-
-## When to Use This Skill
-
-Lists Experience Cloud theme definitions (CommunityThemeDefinition metadata type) for the Setup > Networks > Theme Definitions page. Programmatic inventory available via Metadata API listMetadata at /headless/metadata. Edit / create of theme definitions has no public Connect / Aura alternative — agent must open view_url for those flows. Page-access requires the Networks feature (orgHasNetworks || orgHasNetworksEnabledOnce), the org NOT being a Service-SMB Help-Center-only org, and Community templates enabled.
-
-## Critical Constraints
-
-**Preconditions:**
-
-- Experience Cloud (Networks) feature must be enabled on the org — either currently (Experience Cloud sites enabled) or previously enabled at any point (Experience Cloud sites enabled). Without one of these, the Setup page is hidden. (check: `Experience Cloud sites enabled || Experience Cloud sites enabled`)
-- Org must NOT be a Service-SMB Help-Center-only org. Help-Center-only Service SMB orgs have a restricted Networks surface that hides the general Theme Definitions list. (check: `!Help Center networks-only mode`)
-- Org must have the Community-Template feature license — theme definitions are templated artifacts and require the template entitlement to be visible. (check: `Community templates enabled`)
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `view_CommunityThemeDefinitionList_1` | read | — | `CommunityThemeDefinitionList.view` | — |
-
-### Read operations
-
-#### `view_CommunityThemeDefinitionList_1`
-
-Open Theme Definitions Setup page for manual edit/create/delete of CommunityThemeDefinition. No public Connect/Tooling/Aura covers themeSetting, customThemeLayoutType, defaultBrandingSet, or bundlesInfo mutations.
-
-**Call:** `CommunityThemeDefinitionList.view`

package/skills/experience-content-assets-configure/SKILL.md

@@ -1,86 +0,0 @@
----
-name: experience-content-assets-configure
-description: "Use this skill when users want to manage ContentAsset records end-to-end via Tooling sObject CRUD + Connect assetize-file. Trigger when users mention content, assets, content assets."
-metadata:
-  version: "1.0"
----
-
-# Managing Content Assets
-
-## When to Use This Skill
-
-Manage ContentAsset records end-to-end via Tooling sObject CRUD + Connect assetize-file. ContentAssets are file-backed asset records with a stable DeveloperName (Setup UI column "Unique Name") + MasterLabel (UI column "Label"), a Language, and IsVisibleByExternalUsers gate. The Setup page /lightning/setup/ContentAssets/home is a read-only Aloha-era list with no New/Edit/Delete row actions — this skill exceeds UI parity by exposing all six verbs: list (SOQL enumeration), read (get by Id), create-shell (Tooling POST with 4 top-level fields, no file linkage), create-file-backed (Connect postAssetizeFile wrapping an already-uploaded ContentDocument — the canonical create-with-file path today), update (Tooling PATCH on MasterLabel / Language / IsVisibleByExternalUsers), and delete. The ContentDocumentId FK derived from the underlying file is non-editable; the file itself cannot be swapped on an existing asset. Setting IsVisibleByExternalUsers=true additionally requires the org-level external-asset permission.
-
-## Critical Constraints
-
-**Preconditions:**
-
-- Content Assets is enabled at the org level (feature gate).
-- Caller has the Content Assets read+create permission (per-action gates separate read/create from edit/delete).
-- Setting IsVisibleByExternalUsers requires the org-level external-asset permission in addition to edit access.
-
-**Destructive operations — require explicit user confirmation:**
-
-- **`delete_ContentAsset_1`** — Delete a ContentAsset by Id via the Tooling sObject API. Removes the ContentAsset record; the underlying ContentDocument may persist depending on org retention settings. Use list_ContentAsset_1 (SOQL) or get_ContentAsset_1 to resolve DeveloperName → Id first.
-  - Rollback: No automatic rollback.
-
-## Operations Reference
-
-Operations grouped by purpose. Use these as the building blocks for the workflows above.
-
-### Summary
-
-| Operation | Purpose | Status | Call | Depends on |
-|-----------|---------|--------|------|------------|
-| `list_ContentAsset_1` | read | — | `query.ContentAsset` | — |
-| `get_ContentAsset_1` | read | — | `sobjects/ContentAsset/{id}` | — |
-| `create_ContentAsset_1` | write | — | `sobjects/ContentAsset` | — |
-| `update_ContentAsset_1` | write | — | `sobjects/ContentAsset/{id}` | `create_ContentAsset_1` |
-| `delete_ContentAsset_1` | delete | — | `sobjects/ContentAsset/{id}` | `create_ContentAsset_1` |
-| `postAssetizeFile_1` | write | — | `/services/data/v67.0/connect/files/{fileId}/asset` | — |
-
-### Read operations
-
-#### `list_ContentAsset_1`
-
-Enumerate ContentAsset records via SOQL through the Tooling API. Selectable columns include Id, DeveloperName, MasterLabel, Language, IsVisibleByExternalUsers, NamespacePrefix, SystemModstamp. This is the discover/list/filter surface; use get_ContentAsset_1 (by-Id deep-read) once the caller knows the Id to round-trip into an update. The {q} input is the full SOQL string the agent supplies.
-
-**Call:** `query.ContentAsset`
-
-#### `get_ContentAsset_1`
-
-Deep-read one ContentAsset by Id via the Tooling sObject API. Returns the typed record body (DeveloperName, MasterLabel, Language, IsVisibleByExternalUsers, NamespacePrefix, SystemModstamp, and ContentDocumentId — the FK to the underlying file). Pair with list_ContentAsset_1 (SOQL) to enumerate by DeveloperName + look up an Id, then round-trip into update_ContentAsset_1.
-
-**Call:** `sobjects/ContentAsset/{id}`
-
-### Write operations
-
-#### `create_ContentAsset_1`
-
-Create a SHELL ContentAsset record via the Tooling sObject API — a ContentAsset with no file attached. Tooling POST accepts only DeveloperName, MasterLabel, Language, and IsVisibleByExternalUsers; there is no createable column for file linkage on this surface. For a file-backed ContentAsset (the common case), use postAssetizeFile_1 instead — it wraps an already-uploaded ContentDocument, wires sharing + external visibility, and returns the fileAsset in one call. Setting IsVisibleByExternalUsers=true additionally requires the org-level external-asset permission.
-
-**Call:** `sobjects/ContentAsset`
-
-#### `update_ContentAsset_1`
-
-Update an existing ContentAsset by Id via the Tooling sObject API. Body fields replace existing values. Editable columns include MasterLabel, Language, IsVisibleByExternalUsers. DeveloperName is the stable identity key and the ContentDocumentId FK is non-editable — the underlying file cannot be swapped on an existing asset. Toggling IsVisibleByExternalUsers to true requires the org-level external-asset permission.
-
-**Call:** `sobjects/ContentAsset/{id}`
-
-**Depends on:** `create_ContentAsset_1`
-
-#### `postAssetizeFile_1`
-
-Convert an already-uploaded file (ContentDocument, Id prefix 069) into a ContentAsset in one call. Wires the asset's DeveloperName + MasterLabel, sets external visibility, and applies initial sharing. Returns the enriched FileDetailRepresentation with a nested fileAsset block carrying the new asset's Id, name, and masterLabel. Use this instead of create_ContentAsset_1 when the file already exists — this path avoids constructing a Tooling shell record with no file linkage.
-
-**Call:** `/services/data/v67.0/connect/files/{fileId}/asset`
-
-### Destructive operations
-
-#### `delete_ContentAsset_1`
-
-Delete a ContentAsset by Id via the Tooling sObject API. Removes the ContentAsset record; the underlying ContentDocument may persist depending on org retention settings. Use list_ContentAsset_1 (SOQL) or get_ContentAsset_1 to resolve DeveloperName → Id first.
-
-**Call:** `sobjects/ContentAsset/{id}`
-
-**Depends on:** `create_ContentAsset_1`