@salesforce/afv-skills 1.6.0 → 1.6.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/afv-skills",
-  "version": "1.6.0",
+  "version": "1.6.2",
   "description": "Salesforce skills for Agentforce Vibes",
   "license": "CC-BY-NC-4.0",
   "files": [

package/skills/generating-experience-lwr-site/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: generating-experience-lwr-site
-description: "Creates, modifies, or manages Salesforce Experience Cloud LWR sites via DigitalExperience metadata. Always trigger when users mention Experience sites, LWR sites, DigitalExperience, Experience Cloud, community sites, portals, creating pages, adding routes, views, theme layouts, branding sets, previewing sites, or any DigitalExperience bundle work. Also use when users mention specific content types like sfdc_cms__route, sfdc_cms__themeLayout, etc. or when troubleshooting site deployment."
+description: "Creates, modifies, or manages Salesforce Experience Cloud LWR sites via DigitalExperience metadata. Always trigger when users mention Experience sites, LWR sites, DigitalExperience, Experience Cloud, community sites, portals, creating pages, adding routes, views, theme layouts, branding sets, previewing sites, or any DigitalExperience bundle work. Also use when users mention specific content types like sfdc_cms__route, sfdc_cms__themeLayout, etc. or when troubleshooting site deployment. ALWAYS trigger for ANY guest sharing rule (metadata type sharingGuestRules) creation/modification, guest user access, sharing records to guest users, or when user provides a guest user ID (15 or 18 characters starting with 005)"
 ---
 
 # Experience LWR Site Builder
@@ -29,6 +29,7 @@ When working with Experience LWR sites:
 - Adding pages (routes + views)
 - Configuring LWC components, layouts, themes, or branding styles
 - Setting up guest user access (public sites)
+- Creating or modifying **guest sharing rules** (`sharingGuestRules`) for any Salesforce object (Account, Case, Contact, etc.) — including when the user refers to a "Site Guest User" username or any guest user by ID
 - Troubleshoot deployment errors related to Experience LWR Sites
 
 **Supported Template**: Build Your Own (LWR) - `talon-template-byo`
@@ -100,6 +101,7 @@ Before doing anything, you **MUST ALWAYS** load them first if they match user in
 - [configure-content-brandingSet.md](docs/configure-content-brandingSet.md) - Branding with color patterns/WCAG
 - [handle-component-and-region-ids.md](docs/handle-component-and-region-ids.md) - **UUID generation (CRITICAL)** for component and region ids used in views and themeLayout.
 - [handle-ui-components.md](docs/handle-ui-components.md) - Component discovery, schemas, insertion, configuration
+- [configure-guest-sharing-rules.md](docs/configure-guest-sharing-rules.md) - **Guest sharing rules** (`sharingGuestRules`) for public sites — use for any request involving "guest sharing rule", "Site Guest User", or sharing object records with unauthenticated visitors
 
 ## Common Workflows
 
@@ -185,6 +187,10 @@ Before doing anything, you **MUST ALWAYS** load them first if they match user in
 }
 ```
 
+### Configuring Guest User Sharing Rules
+
+- [ ] MUST read [configure-guest-sharing-rules.md](docs/configure-guest-sharing-rules.md) and follow all steps there.
+
 ### Retrieving Site Preview and Builder URLs After Deployment
 
 **Use when** user requests to preview a site, access a builder site, or after successfully deploying a site.
@@ -212,10 +218,16 @@ Use `sf` CLI to validate and deploy. Access help docs by attaching `--help`, e.g
 - `sf project deploy --help`
 - `sf project deploy validate --help`
 
-Note that metadata types are space-delimited.
+Note that metadata types are space-delimited. **Never** wrap them in quotes or use commas. For example, `--metadata "DigitalExperienceBundle DigitalExperience"` is **incorrect** — always use `--metadata DigitalExperienceBundle DigitalExperience`.
 
 **Validate**:
-`sf project deploy validate --metadata DigitalExperienceBundle DigitalExperience DigitalExperienceConfig Network CustomSite --target-org ${usernameOrAlias}`
+
+```bash
+sf project deploy validate --metadata DigitalExperienceBundle DigitalExperience DigitalExperienceConfig Network CustomSite --target-org ${usernameOrAlias}
+```
 
 **Deploy**:
-`sf project deploy start --metadata DigitalExperienceBundle DigitalExperience DigitalExperienceConfig Network CustomSite --target-org ${usernameOrAlias}`
+
+```bash
+sf project deploy start --metadata DigitalExperienceBundle DigitalExperience DigitalExperienceConfig Network CustomSite --target-org ${usernameOrAlias}
+```

package/skills/generating-experience-lwr-site/docs/bootstrap-template-byo-lwr.md

@@ -18,11 +18,66 @@ Ask user to choose:
 
 ### Option 1: Create in Org
 
+**Step 1:** Run the create command:
+
+```bash
+sf community create --name "{siteName}" --template-name 'Build Your Own (LWR)' --url-path-prefix "{prefix}" --target-org {usernameOrAlias} --json
+```
+
+Site creation is an async job. As soon as the terminal returns output, capture the `jobId` and move on — do not wait for the shell command to fully exit.
+
+**Step 2:** Ask the user: *"Would you like me to wait for the site creation to complete and then retrieve the metadata for you, or would you prefer to retrieve it yourself once it's ready?"*
+
+**Stop here and wait for the user's response before proceeding.**
+
+---
+
+**If the user wants to wait and retrieve:**
+
+Poll the `BackgroundOperation` object using the following command, replacing `{jobId}` with the ID returned from the create command:
+
+```soql
+SELECT Status FROM BackgroundOperation WHERE Id = '{jobId}'
+```
+
+Use the MCP tool `run_soql_query` to run this query on the given target org. If the MCP tool is not available, run the following command instead, replacing `{jobId}` and `{usernameOrAlias}` with the appropriate values:
+
+```bash
+sf data query --query "SELECT Status FROM BackgroundOperation WHERE Id = '{jobId}'" --target-org {usernameOrAlias} --json
+```
+
+Repeat until `Status` is `Complete`. If the query does not return `Complete` after several attempts, ask the user to manually check their target org to confirm whether site creation has completed. **Stop here and do not proceed until the user confirms the site is ready.**
+
+Once complete, run each of the following retrieval commands **one at a time**. Do not chain them together (e.g. do not use `&&`). Wait for each command to return output before running the next. Metadata types are space-delimited — **never** wrap them in quotes or use commas:
+
 ```bash
-sf community create --name "{siteName}" --template-name 'Build Your Own (LWR)' --url-path-prefix "{prefix}"
+sf project retrieve start --metadata DigitalExperienceBundle --target-org {usernameOrAlias} --json
 ```
 
-After creation, retrieve metadata using sf CLI.
+```bash
+sf project retrieve start --metadata DigitalExperienceConfig --target-org {usernameOrAlias} --json
+```
+
+```bash
+sf project retrieve start --metadata Network --target-org {usernameOrAlias} --json
+```
+
+```bash
+sf project retrieve start --metadata CustomSite --target-org {usernameOrAlias} --json
+```
+
+---
+
+**If the user wants to retrieve themselves:**
+
+Provide them with the retrieval command to run once the site is ready. Metadata types are space-delimited — **never** wrap them in quotes or use commas:
+
+```bash
+sf project retrieve start --metadata DigitalExperienceBundle DigitalExperienceConfig Network CustomSite --target-org {usernameOrAlias} --json
+```
+
+---
+
 
 ### Option 2: Scaffold Locally
 

package/skills/generating-experience-lwr-site/docs/configure-guest-sharing-rules.md

@@ -1,7 +1,14 @@
 # Guest User Sharing Rules (Public Sites Only)
 
-**Use when** the user explicitly wants to make the site **public** (accessible to unauthenticated visitors). If the site is private/login-required, guest sharing rules are not needed.
-If sharingRules metadata is not available locally in force-app/main/default/sharingRules, retrieve it from the org before creating new rules.
+**Use when** the user asks to create or modify a guest sharing rule, mentions a username containing "Guest User" or "Site Guest User" (e.g. "ZenLease Site Guest User"), or wants to share object records with unauthenticated visitors.
+
+## Steps
+
+1. **Resolve the guest user identity**: If the user provides a username like "ZenLease Site Guest User", use it directly as the `<guestUser>` value (`CommunityNickname`). If a user ID is provided (e.g. `005AAC00003f8EP`), query the org to get the `CommunityNickname` first.
+2. **Check for existing file**: Look for `sharingRules/{ObjectName}.sharingRules-meta.xml` locally. If missing, retrieve it from the org before editing.
+3. **Generate the rule**: Follow the XML example and critical requirements below. Never use `sharingCriteriaRules` or `<role>`/`<group>` for guest rules.
+
+If `sharingRules` metadata is not available locally in `force-app/main/default/sharingRules`, retrieve it from the org before creating new rules.
 
 ## Retrieve Full SharingRules Schema
 

package/skills/generating-permission-set/SKILL.md

@@ -154,6 +154,21 @@ Specify license requirements and record type visibility:
     <default>true</default>
 </recordTypeVisibilities>
 ```
+## Step 8: Set Agent Access (Optional)
+                                              
+Enable access to Agentforce Employee Agents for users assigned to this permission set:
+
+<agentAccesses>
+    <agentName>Sales_Assistant_Agent</agentName>
+    <enabled>true</enabled>
+</agentAccesses>
+
+Field requirements:
+- agentName (Required): The developer name of the employee agent
+- enabled (Required): Set to true to grant access, false to deny
+
+Important:
+- Agent names must match existing Agentforce Employee Agent developer names
 
 ## Validation Checklist