@salesforce/afv-skills 1.23.0 → 1.25.0

package/package.json

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

package/skills/commerce-b2b-open-code-components-replace/SKILL.md

@@ -0,0 +1,244 @@
+---
+name: commerce-b2b-open-code-components-replace
+description: "Replace OOTB (out-of-the-box) B2B Commerce components with open source equivalents in site metadata content.json files, or look up the equivalent open code `site:` component for OOTB definitions. Use when users mention \"replace OOTB components\", \"replace commerce components with open code\", \"swap OOTB for open source\", \"replace commerce_builder:\", \"replace OOTB in site\", \"replace component in site metadata\", \"replace component definition\", \"find open code equivalent\", \"equivalent open code component\", \"OOTB to open code mapping\", \"what is the site component for\", components \"in this view\" or \"for a given view\", or a specific list of component names — and want to update or only discover mappings in their store metadata."
+allowed-tools: Bash(grep:*) Bash(ls:*) Read Write
+metadata:
+  version: "1.0"
+---
+
+# Replacing OOTB B2B Commerce Components with Open Code
+
+This skill replaces OOTB (out-of-the-box) B2B Commerce component definitions in site metadata `content.json` files with their open source `site:` equivalents, or looks up the equivalent open code component for given OOTB definitions without making changes. It uses an authoritative mapping loaded from `assets/ootb-to-open-code-mapping.json`.
+
+## Scope
+
+**Modes:** **Full replace** runs the scan (Step 1), user selection if needed, then `content.json` updates (Step 2–3). **Lookup only** (user asks for equivalents but not to change files): apply the mapping-authority rule and report OOTB → `site:` for the named components or for definitions found in the scoped `content.json` — **do not** call Write unless the user confirms replacement. **View-scoped** work: limit file discovery and reads to `sfdc_cms__view/<ViewName>/` (or the path the user gives) instead of all views.
+
+---
+
+## Prerequisites
+
+### Resolve `<package-dir>`
+
+Read `sfdx-project.json` and pick the active package directory. Extract `packageDirectories[]` and use the entry with `"default": true`; if no entry is flagged default, use the first entry. Use this value as `<package-dir>` everywhere below. If `sfdx-project.json` is missing or has no `packageDirectories`, tell the user and abort.
+
+### Delegate setup
+
+Before replacing components, delegate to the **commerce-b2b-open-code-components-integrate** skill to ensure:
+
+1. Open source repository is cloned at `.tmp/b2b-commerce-open-source-components`
+2. Store is selected and site metadata is retrieved locally
+3. Open code components are copied to the store's site metadata
+
+The integrating skill owns the `.tmp/` clone lifecycle (it prompts the user to reuse or re-clone an existing checkout); this skill assumes the clone is already present.
+
+Send a plain-text chat reply to the user (per Rule 1): "Before replacing components, I need to verify that the open code components are set up in your store. Let me check..."
+
+If any prerequisite is not met, the integrating skill will handle it. Once all checks pass, proceed to the replacement workflow.
+
+**Required state** after prerequisites:
+- **Package dir** — the value resolved above (e.g., `force-app`)
+- **Store name** — e.g., `My_B2B_Store1`
+- **Site metadata path** — `<package-dir>/main/default/digitalExperiences/site/<store-name>/`
+
+---
+
+## Replacement Workflow
+
+### Step 1: Scan Site and Cross-Reference Mapping
+
+**This step is MANDATORY.** Always scan the site first before attempting any replacements.
+
+Send a plain-text chat reply to the user (per Rule 1): "I'm scanning your store's site metadata to find all OOTB commerce components currently in use and checking which have open code equivalents."
+
+**Step 1a — Find affected files** (one command, simple literal match):
+
+```bash
+grep -rl '"commerce' \
+  <package-dir>/main/default/digitalExperiences/site/<store-name>/sfdc_cms__view/ \
+  <package-dir>/main/default/digitalExperiences/site/<store-name>/sfdc_cms__themeLayout/ \
+  --include="content.json"
+```
+
+**Step 1b — Read the mapping and parse the matched files.** Read `assets/ootb-to-open-code-mapping.json` once into memory. Then, using the **Read** tool, parse each matched file and extract all `"definition"` values that start with `commerce` (e.g., `commerce_builder:cartBadge`). Collect a deduplicated list of OOTB components across all files.
+
+**Step 1c — List repo components** (one command):
+
+```bash
+ls .tmp/b2b-commerce-open-source-components/force-app/main/default/sfdc_cms__lwc/
+```
+
+Using the parsed definitions, the `ls` output, and the mapping table, categorize every discovered OOTB component into three groups:
+
+**Show the user a breakdown and a selectable list:**
+
+First, inform the user about skipped and unmapped components:
+```text
+Found X OOTB components in your site:
+
+In mapping table but NOT in repo (skipping):
+  - commerce_builder:quoteSummary → site:quoteSummary (not found in repo)
+
+No mapping available (not in mapping table):
+  - commerce_builder:actionButtons
+  - commerce_builder:layoutHeaderOne
+  - commerce_builder:searchInputContainer
+  - commerce_builder:myAccountMegaMenu
+```
+
+Then present the replaceable components as a **multi-select list** so the user can pick from checkboxes instead of typing. Include an "All of the above" option:
+
+```text
+Which components would you like to replace?
+
+☐ commerce_builder:heading → site:productHeading
+☐ commerce_builder:cartBadge → site:cartBadge
+☐ commerce_builder:searchInput → site:searchInput
+☐ All of the above
+```
+
+If user provided specific component name(s) in the original request, pre-filter to those and skip the selection prompt.
+
+### Step 2: Replace in content.json
+
+Send a plain-text chat reply to the user (per Rule 1): "I'm now replacing the selected OOTB component definitions with their open code equivalents in your site's content.json files."
+
+The affected files are already known from Step 1. For each file that contains selected components:
+1. Use the **Read** tool to read the file
+2. For each selected OOTB component, confirm again that the mapped **`site:`** target exists in the open code repo. Only proceed with replacements that pass this check.
+3. Replace all matching `"definition"` values with their mapped open code equivalents — **always** use the exact `site:<name>` string from the mapping table
+   - Example: `"definition": "commerce_builder:heading"` → `"definition": "site:productHeading"`
+4. Use the **Write** tool to save the updated file
+5. Preserve all other JSON properties — only `"definition"` values change
+
+**Batch efficiently:** if a file contains multiple OOTB components, apply ALL replacements in a single Read → modify → Write pass. Do NOT read and write the same file multiple times.
+
+### Step 3: Report
+
+```text
+✅ Replacement Complete!
+
+Replaced X components across Y files:
+- commerce_builder:heading → site:productHeading (3 files)
+- commerce_builder:cartBadge → site:cartBadge (2 files)
+- commerce_builder:searchInput → site:searchInput (4 files)
+
+Skipped (not in repo):
+- commerce_builder:quoteSummary
+
+No mapping available (left unchanged):
+- commerce_builder:actionButtons
+- commerce_builder:layoutHeaderOne
+- commerce_builder:searchInputContainer
+
+Modified files:
+- sfdc_cms__view/Home/content.json
+- sfdc_cms__view/Product_Detail/content.json
+- sfdc_cms__themeLayout/DefaultTheme/content.json
+
+Next Steps:
+1. Deploy: sf project deploy start -d <package-dir>/main/default/digitalExperiences/site/<store-name>
+2. Test the store thoroughly in Experience Builder
+3. Publish your site when ready
+```
+
+---
+
+## Example Interaction
+
+**User:** "Replace OOTB components with open code versions"
+
+**Agent:** "Before replacing components, I need to verify that the open code components are set up in your store. Let me check..."
+- ✓ Open source repo cloned
+- ✓ Store metadata available for My_B2B_Store1
+- ✓ Open code components are integrated
+
+**Agent:** "I'm scanning your store's site metadata to find all OOTB commerce components and checking which have open code equivalents."
+
+_(Runs grep -rl to find files with commerce definitions, Reads those files to extract component names, runs ls to list repo components, then cross-references with mapping table)_
+
+```text
+Found 8 OOTB components in your site:
+
+No mapping available (not in mapping table):
+  - commerce_builder:searchInputContainer
+  - commerce_builder:layoutHeaderOne
+  - commerce_builder:myAccountMegaMenu
+  - commerce_builder:actionButtons
+```
+
+**Agent** _(asks the user via a multi-select prompt):_
+```text
+Which components would you like to replace?
+
+☐ commerce_builder:heading → site:productHeading
+☐ commerce_builder:cartBadge → site:cartBadge
+☐ commerce_builder:searchInput → site:searchInput
+☐ commerce_builder:cartSummary → site:cartSummary
+☐ All of the above
+```
+
+**User:** _(selects heading and cartBadge)_
+
+**Agent:** "I'm now replacing the selected OOTB component definitions with their open code equivalents in your site's content.json files."
+
+_(Files already known from scan — one Read/Write pass per affected file, all replacements batched)_
+
+```text
+✅ Replacement Complete!
+
+Replaced 2 components across 5 files:
+- commerce_builder:heading → site:productHeading (3 files)
+- commerce_builder:cartBadge → site:cartBadge (2 files)
+
+No mapping available (left unchanged):
+- commerce_builder:searchInputContainer
+- commerce_builder:layoutHeaderOne
+- commerce_builder:myAccountMegaMenu
+- commerce_builder:actionButtons
+
+Modified files:
+- sfdc_cms__view/Home/content.json
+- sfdc_cms__view/Product_Detail/content.json
+- sfdc_cms__themeLayout/DefaultTheme/content.json
+
+Next Steps:
+1. Deploy: sf project deploy start -d force-app/main/default/digitalExperiences/site/My_B2B_Store1
+2. Test the store thoroughly in Experience Builder
+```
+
+---
+
+## Rules
+
+1. **Always explain in chat before executing.** Before every Bash or Write tool call, send a plain-text reply in the conversation that says what the command will do and why. The explanation MUST appear as a normal chat message preceding the tool call. Do NOT embed it inside the command itself (no `echo` lines, no `#` comments), do NOT prefix it to the command, and do NOT rely solely on the tool's `description` parameter — that field is not guaranteed to be visible to the user. After the explanation, issue the tool call and wait for the user to approve it before continuing.
+2. **`assets/ootb-to-open-code-mapping.json` is the only source of truth.** Every OOTB → open-code mapping comes from that file; never guess, infer, or hallucinate component names. Each replacement's new `"definition"` MUST be the exact mapped value from the file, which always uses the `site:` namespace (e.g. `site:productHeading`). Before writing, verify the mapped target exists in the cloned open code components repo (under `.tmp/b2b-commerce-open-source-components/force-app/main/default/sfdc_cms__lwc/`); if it is not present, skip the replacement and report it under "not in repo".
+3. **Use Read and Write tools for JSON files.** Use the Read tool to parse `content.json` files and the Write tool to update them. Do NOT use bash to parse or edit JSON — no sed, awk, perl, or regex on JSON content. Bash is only for **simple file discovery** (`grep -rl`, `find`, `ls`) — never for extracting or modifying JSON values.
+4. **Minimize commands.** Batch work into as few commands as possible. Use a single grep to scan all files, a single ls to verify the repo, and one Read/Write pass per file. Do NOT run a separate command for every component or every directory.
+
+---
+
+## Error Handling
+
+| Error | Message | Action |
+|-------|---------|--------|
+| Prerequisites not met | "Open code components are not integrated yet." | Run integrating skill first |
+| No mapping found | "No mapping found for '{component}'." | Show available mappings, report as unmapped |
+| Component not in repo | "Open code component '{name}' not found in cloned repo." | Skip and inform user |
+| No OOTB components in site | "No OOTB commerce components found in site metadata." | Inform user, nothing to replace |
+| No replaceable components | "All OOTB components found are unmapped — none can be replaced." | Show the unmapped list, suggest checking for updated mappings |
+| content.json parse error | "Failed to parse content.json: {file}" | Show error, skip file, continue with remaining files |
+
+---
+
+## Verification Checklist
+
+- [ ] Prerequisites verified via integrating skill (repo, store, components)
+- [ ] Site scanned + repo verified + mapping cross-referenced in minimal commands (Step 1)
+- [ ] Each replacement uses the exact mapped `site:` definition and was verified present in the open code repo before write
+- [ ] Breakdown shown to user with three categories before proceeding
+- [ ] User selected components to replace (or provided names)
+- [ ] Each `content.json` file updated in a single Read → modify → Write pass
+- [ ] JSON structure preserved, no syntax errors introduced
+- [ ] User informed of skipped and unmapped components
+- [ ] Deployment command provided

package/skills/commerce-b2b-open-code-components-replace/assets/ootb-to-open-code-mapping.json

@@ -0,0 +1,66 @@
+{
+  "commerce_builder:actionButton": "site:commonButton",
+  "commerce_builder:b2bCartContents": "site:cartB2bCartContents",
+  "commerce_builder:cartAppliedPromotion": "site:cartPromotionApplied",
+  "commerce_builder:cartApplyCoupon": "site:cartApplyCoupon",
+  "commerce_builder:cartBadge": "site:cartBadge",
+  "commerce_builder:cartPromotions": "site:cartPromotions",
+  "commerce_builder:cartSummary": "site:cartSummary",
+  "commerce_builder:checkoutButton": "site:checkoutButton",
+  "commerce_builder:checkoutDeliveryAddress": "site:checkoutDeliveryAddress",
+  "commerce_builder:checkoutDeliveryMethod": "site:checkoutDeliverymethod",
+  "commerce_builder:checkoutGiftOptions": "site:checkoutGiftOptions",
+  "commerce_builder:checkoutNotification": "site:checkoutNotification",
+  "commerce_builder:checkoutPurchaseOrder": "site:checkoutPurchaseOrder",
+  "commerce_builder:checkoutShippingInstructions": "site:checkoutShippingInstructions",
+  "commerce_builder:checkoutSubscriptionPolicyDisclaimer": "site:checkoutSubscriptionPolicyDisclaimer",
+  "commerce_builder:consentBlanket": "site:legalConsentBlanket",
+  "commerce_builder:countryPickerV2": "site:commonCountryPicker",
+  "commerce_builder:drilldownNavigation": "site:commonDrilldownNavigation",
+  "commerce_builder:formattedCurrency": "site:commonFormattedCurrency",
+  "commerce_builder:heading": "site:productHeading",
+  "commerce_builder:layoutFooter": "site:layoutFooter",
+  "commerce_builder:layoutHeaderSimple": "site:layoutHeaderSimple",
+  "commerce_builder:linkList": "site:commonLinksList",
+  "commerce_builder:myAccountAddressContainer": "site:myaccountAddress",
+  "commerce_builder:navigationMenuItemList": "site:myaccountNavigationMenuItems",
+  "commerce_builder:orderConfirmationBillingDetails": "site:orderConfirmationDetailsBilling",
+  "commerce_builder:orderConfirmationDeliveryGroup": "site:orderConfirmationDeliverygroup",
+  "commerce_builder:orderConfirmationErrorMessage": "site:orderConfirmationMessageError",
+  "commerce_builder:orderConfirmationSuccessMessage": "site:orderConfirmationMessageSuccess",
+  "commerce_builder:orderDetails": "site:orderDetails",
+  "commerce_builder:orderList": "site:orderList",
+  "commerce_builder:orderListDateFilter": "site:orderListDateFilter",
+  "commerce_builder:orderProductsInfo": "site:orderProducts",
+  "commerce_builder:orderPromotionsSummary": "site:orderPromotions",
+  "commerce_builder:orderShipmentTracker": "site:orderShipmentTracker",
+  "commerce_builder:paymentByExpress": "site:paymentByExpress",
+  "commerce_builder:productAttachments": "site:productAttachments",
+  "commerce_builder:productBundle": "site:productBundle",
+  "commerce_builder:productBundleItem": "site:productBundleItem",
+  "commerce_builder:productFieldsTable": "site:productFieldsTable",
+  "commerce_builder:productFrequentlyBoughtTogether": "site:productFrequentlyBoughtTogether",
+  "commerce_builder:productMediaGallery": "site:productMediaGallery",
+  "commerce_builder:productPricingDetails": "site:productPricingDetails",
+  "commerce_builder:productSellingModelSelector": "site:productSellingmodelSelector",
+  "commerce_builder:productSet": "site:productSet",
+  "commerce_builder:promotionDiscountsApproaching": "site:promotionDiscountsApproaching",
+  "commerce_builder:purchaseOptions": "site:productPurchaseOptions",
+  "commerce_builder:purchasedProducts": "site:productListPurchased",
+  "commerce_builder:quickOrder": "site:orderQuickOrder",
+  "commerce_builder:quoteSummary": "site:quoteSummary",
+  "commerce_builder:searchFilters": "site:searchFilters",
+  "commerce_builder:searchInput": "site:searchInput",
+  "commerce_builder:searchNoResultsLayout": "site:searchResultsLayoutEmpty",
+  "commerce_builder:searchResults": "site:searchResults",
+  "commerce_builder:searchResultsLayout": "site:searchResultsLayout",
+  "commerce_builder:searchSortMenu": "site:searchSortMenu",
+  "commerce_builder:socialLinks": "site:commonLinksSocial",
+  "commerce_builder:splitShipmentHeader": "site:cartSplitshipmentHeader",
+  "commerce_builder:stickyContainer": "site:commonContainerSticky",
+  "commerce_builder:subscriptions": "site:productSubscriptions",
+  "commerce_builder:userProfileMenu": "site:myAccountUserProfileMenu",
+  "commerce_builder:variantSelector": "site:productVariantSelector",
+  "commerce_builder:wishlist": "site:productWishlist",
+  "commerce_builder:wishlistShortcut": "site:productWishlistShortcut"
+}

package/skills/{developing-datacloud-code-extension → data360-code-extension-generate}/SKILL.md

@@ -1,11 +1,11 @@
 ---
-name: developing-datacloud-code-extension
+name: data360-code-extension-generate
 description: "Develop and deploy Data Cloud Code Extensions using SF CLI plugin. Use this skill when creating custom Python transformations for Data Cloud, deploying code extensions, or testing data transformations. Supports init, run, scan, and deploy operations."
 metadata:
   version: "1.0"
 ---
 
-# developing-datacloud-code-extension Skill
+# data360-code-extension-generate Skill
 
 ## Overview
 
@@ -79,7 +79,7 @@ sf data-code-extension function init --package-dir <directory>
 - `--package-dir, -p` - Directory path where the package will be created
 
 **What it creates:**
-```
+```text
 my-transform/              # Project root
 ├── payload/               # CRITICAL: This is what --package-dir must point to for deploy
 │   ├── entrypoint.py      # Main transformation code
@@ -172,7 +172,7 @@ cat payload/config.json
 
 #### Step 4b: Validate Each DLO Schema
 
-**Use the `getting-datacloud-schema` skill to verify DLOs exist and check field names.**
+**Use the `data360-schema-get` skill to verify DLOs exist and check field names.**
 
 For each DLO referenced in your code:
 
@@ -260,7 +260,7 @@ sf data-code-extension script deploy --target-org <org_alias> --name <name> --pa
 | `Cannot connect to Docker daemon` | Start Docker Desktop |
 | `No org found for alias` | `sf org login web --alias <org_alias>` |
 | `config.json not found` | `sf data-code-extension script scan --entrypoint ./payload/entrypoint.py` |
-| `DLO not found` | Verify DLO exists (use getting-datacloud-schema skill), check spelling and `__dll` suffix |
+| `DLO not found` | Verify DLO exists (use data360-schema-get skill), check spelling and `__dll` suffix |
 | `Permission denied writing` | Re-run scan, verify target DLO exists and is writable |
 | `Deploy fails - wrong directory` | Ensure `--package-dir` points to `payload/` directory, not project root |
 
@@ -285,9 +285,9 @@ sf data-code-extension script deploy --target-org <org_alias> --name <name> --pa
 
 ## Integration with Other Skills
 
-**Use with getting-datacloud-schema skill (CRITICAL for validation):**
+**Use with data360-schema-get skill (CRITICAL for validation):**
 
-The `getting-datacloud-schema` skill is **required** for validating DLOs before testing code extensions.
+The `data360-schema-get` skill is **required** for validating DLOs before testing code extensions.
 
 **Use with Datakit Workflow:**
 1. Create DLO via code extension

package/skills/{developing-datacloud-code-extension → data360-code-extension-generate}/references/README.md

@@ -1,4 +1,4 @@
-# developing-datacloud-code-extension Skill
+# data360-code-extension-generate Skill
 
 ## Overview
 
@@ -17,25 +17,25 @@ This skill helps you create Data Cloud Code Extensions through a complete workfl
 ## Usage
 
 **Initialize a project:**
-```
+```text
 "Create a new Data Cloud code extension project called employee-transform"
 "Initialize a code extension to transform employee data"
 ```
 
 **Test locally:**
-```
+```text
 "Run the code extension in my-transform directory against afvibe org"
 "Test the entrypoint.py file locally"
 ```
 
 **Scan for permissions:**
-```
+```text
 "Scan the entrypoint.py to generate config"
 "Update permissions in config.json"
 ```
 
 **Deploy:**
-```
+```text
 "Deploy Employee_Upper code extension to afvibe"
 "Deploy this transform with package-version 1.0.0"
 ```
@@ -135,7 +135,7 @@ print(f"Processed {len(output)} employee records")
 
 After `init`, you'll have:
 
-```
+```text
 my-transform/
 ├── payload/
 │   ├── entrypoint.py      # Your transformation code
@@ -173,7 +173,7 @@ client.write_to_dmo('EmployeeDMO', df, 'upsert')
 | Wrong Python version | Use pyenv to install 3.11.0 |
 | Org not connected | `sf org login web --alias <alias>` |
 | Config missing | Run scan command |
-| DLO not found | Check DLO name, use getting-datacloud-schema skill |
+| DLO not found | Check DLO name, use data360-schema-get skill |
 | Docker error | Start Docker Desktop |
 
 ## CPU Size Selection

package/skills/{developing-datacloud-code-extension → data360-code-extension-generate}/references/quick-reference.md

@@ -215,7 +215,7 @@ sf data-code-extension script scan --entrypoint ./payload/entrypoint.py
 
 ## File Structure
 
-```
+```text
 my-project/
 ├── payload/
 │   ├── entrypoint.py      # Main code
@@ -248,7 +248,7 @@ my-project/
 | Wrong Python version | Use pyenv to install 3.11.0 |
 | Org not connected | `sf org login web --alias <alias>` |
 | Config missing | Run scan command |
-| DLO not found | Check DLO name, use getting-datacloud-schema skill |
+| DLO not found | Check DLO name, use data360-schema-get skill |
 | Docker error | Start Docker Desktop |
 
 ## Deployment Checklist

package/skills/{getting-datacloud-schema → data360-schema-get}/SKILL.md

@@ -1,11 +1,11 @@
 ---
-name: getting-datacloud-schema
+name: data360-schema-get
 description: "Retrieve Data Lake Object (DLO) and Data Model Object (DMO) schema information from Salesforce Data Cloud using REST APIs. Use this skill when you need to inspect DLO or DMO field definitions, data types, or metadata. Takes org alias and optional DLO/DMO name as parameters."
 metadata:
   version: "1.0"
 ---
 
-# getting-datacloud-schema Skill
+# data360-schema-get Skill
 
 
 ## Overview
@@ -42,7 +42,7 @@ sf org list
 ```
 
 Example output:
-```
+```text
 ┌────┬───────┬──────────────────────────┬────────────────────┬───────────┐
 │    │ Alias │ Username                 │ Org Id             │ Status    │
 ├────┼───────┼──────────────────────────┼────────────────────┼───────────┤
@@ -67,28 +67,28 @@ sf org login web --alias <org_alias>
 
 ### Step 3a: Execute DLO Schema Script
 
-The Python scripts are bundled with this skill. They live in the `scripts/` subdirectory of the same directory that contains this SKILL.md file. Use the absolute path to that directory — do NOT use `./scripts/` as that resolves relative to the current working directory, not the skill directory.
+The Python scripts are bundled with this skill in the `scripts/` subdirectory.
 
 **To list all DLOs:**
 ```bash
-python3 <skill_dir>/scripts/get_dlo_schema.py <org_alias>
+python3 ./scripts/get_dlo_schema.py <org_alias>
 ```
 
 **To get specific DLO schema:**
 ```bash
-python3 <skill_dir>/scripts/get_dlo_schema.py <org_alias> <dlo_name>
+python3 ./scripts/get_dlo_schema.py <org_alias> <dlo_name>
 ```
 
 ### Step 3b: Execute DMO Schema Script
 
 **To list all DMOs:**
 ```bash
-python3 <skill_dir>/scripts/get_dmo_schema.py <org_alias>
+python3 ./scripts/get_dmo_schema.py <org_alias>
 ```
 
 **To get specific DMO schema:**
 ```bash
-python3 <skill_dir>/scripts/get_dmo_schema.py <org_alias> <dmo_name>
+python3 ./scripts/get_dmo_schema.py <org_alias> <dmo_name>
 ```
 
 ### Step 4: Present Results
@@ -135,7 +135,7 @@ After displaying results, suggest relevant follow-up actions:
 ## API Endpoints Used
 
 ### List All DLOs
-```
+```text
 GET /services/data/v64.0/ssot/data-lake-objects
 ```
 
@@ -158,14 +158,14 @@ Response structure:
 ```
 
 ### Get DLO Schema
-```
+```text
 GET /services/data/v64.0/ssot/data-lake-objects/{dlo_name}
 ```
 
 Response structure (same as individual object in list response, but wrapped in paginated format).
 
 ### List All DMOs
-```
+```text
 GET /services/data/v64.0/ssot/data-model-objects
 ```
 
@@ -186,7 +186,7 @@ Response structure:
 ```
 
 ### Get DMO Schema
-```
+```text
 GET /services/data/v64.0/ssot/data-model-objects/{dmo_name}
 ```
 
@@ -219,29 +219,29 @@ Response structure (same as individual object in list response, but wrapped in p
 ## Example Usage
 
 **Example 1: List all DLOs**
-```
+```text
 User: "Show me all DLOs in afvibe org"
 
 Response:
 1. Run sf org list to discover connected org alias
 2. Authenticate to afvibe
-3. Run: python3 <skill_dir>/scripts/get_dlo_schema.py afvibe
+3. Run: python3 ./scripts/get_dlo_schema.py afvibe
 4. Display formatted list of DLOs
 ```
 
 **Example 2: Get specific DLO schema**
-```
+```text
 User: "Get the schema for Employee__dll in afvibe"
 
 Response:
 1. Run sf org list to discover connected org alias
 2. Authenticate to afvibe
-3. Run: python3 <skill_dir>/scripts/get_dlo_schema.py afvibe Employee__dll
+3. Run: python3 ./scripts/get_dlo_schema.py afvibe Employee__dll
 4. Display field schema with types and metadata
 ```
 
 **Example 3: Explore DLOs then get schema**
-```
+```text
 User: "What DLOs exist in myorg and show me the schema for the Employee one"
 
 Response:
@@ -253,29 +253,29 @@ Response:
 ```
 
 **Example 4: List all DMOs**
-```
+```text
 User: "Show me all DMOs in afvibe org"
 
 Response:
 1. Run sf org list to discover connected org alias
 2. Authenticate to afvibe
-3. Run: python3 <skill_dir>/scripts/get_dmo_schema.py afvibe
+3. Run: python3 ./scripts/get_dmo_schema.py afvibe
 4. Display formatted list of DMOs
 ```
 
 **Example 5: Get specific DMO schema**
-```
+```text
 User: "Get the schema for Individual__dlm in afvibe"
 
 Response:
 1. Run sf org list to discover connected org alias
 2. Authenticate to afvibe
-3. Run: python3 <skill_dir>/scripts/get_dmo_schema.py afvibe Individual__dlm
+3. Run: python3 ./scripts/get_dmo_schema.py afvibe Individual__dlm
 4. Display field schema with types and metadata
 ```
 
 **Example 6: Explore DMOs then get schema**
-```
+```text
 User: "What DMOs exist in myorg and show me the schema for the Individual one"
 
 Response:
@@ -289,7 +289,7 @@ Response:
 ## Output Format
 
 ### DLO List Output
-```
+```text
 Found 5 DLOs in org 'afvibe':
 
 1. DataCustomCodeLogs__dll
@@ -306,7 +306,7 @@ Found 5 DLOs in org 'afvibe':
 ```
 
 ### DLO Schema Output
-```
+```yaml
 DLO: Employee__dll
 Label: Employee
 Category: Profile
@@ -331,7 +331,7 @@ Next steps:
 ```
 
 ### DMO List Output
-```
+```text
 Found 10 DMOs in org 'afvibe':
 
 1. Individual__dlm
@@ -346,7 +346,7 @@ Found 10 DMOs in org 'afvibe':
 ```
 
 ### DMO Schema Output
-```
+```yaml
 DMO: Individual__dlm
 Label: Individual
 Category: Profile