@salesforce/afv-skills 1.6.0 → 1.6.1

package/package.json

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

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

@@ -212,10 +212,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-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