@salesforce/afv-skills 1.63.0 → 1.65.0

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

@@ -0,0 +1,48 @@
+---
+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

@@ -0,0 +1,38 @@
+---
+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

@@ -0,0 +1,86 @@
+---
+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`