@salesforce/afv-skills 1.28.0 → 1.30.0

package/skills/integration-connectivity-generate/references/event-driven-architecture-guide.md

@@ -60,7 +60,7 @@ The Pub/Sub API is the **recommended mechanism for external consumers** subscrib
 
 ### External Consumer Architecture
 
-```
+```text
 Salesforce Org
   └── Platform Event / CDC Event
         └── Pub/Sub API (gRPC endpoint)
@@ -106,7 +106,7 @@ Salesforce Event Relays forward Platform Events to AWS EventBridge, enabling clo
 
 ### Architecture
 
-```
+```text
 Salesforce Platform Event
   └── Event Relay Definition (Metadata)
         └── AWS EventBridge Partner Event Source
@@ -156,7 +156,7 @@ For organizations needing long-retention, high-throughput event streaming beyond
 
 ### Integration Pattern
 
-```
+```text
 Salesforce → Platform Event → Apex/Flow subscriber → Heroku Kafka producer
                                                         └── Consumer Group A (analytics)
                                                         └── Consumer Group B (data lake)
@@ -187,7 +187,7 @@ For scenarios requiring high-volume data push to external systems:
 
 ### Recommended Pattern: Middleware + Platform Events
 
-```
+```text
 Salesforce Record Change
   └── After-Save Flow / Trigger
         └── Publish Platform Event (lightweight payload)
@@ -255,7 +255,7 @@ List<EventBusSubscriber> subs = [
 
 ## Summary: EDA Decision Tree
 
-```
+```text
 Need real-time data sync?
   ├── YES → Is consumer external?
   │    ├── YES → Pub/Sub API + Platform Events (or CDC for record changes)

package/skills/integration-connectivity-generate/references/event-patterns.md

@@ -191,6 +191,7 @@ OrderStatusPublisher.publishEvents(events);
 ### Event Subscriber Trigger
 
 **Template**: `assets/platform-events/event-subscriber-trigger.trigger`
+**Template**: `assets/platform-events/event-subscriber-action.cls`
 
 #### Standard Volume Subscriber
 
@@ -534,7 +535,7 @@ public static void handleUpdate(OpportunityChangeEvent event, List<String> chang
 
 ### Decision Matrix
 
-```
+```text
 ┌───────────────────────────────────────────────────────────────────────┐
 │  WHEN TO USE PLATFORM EVENTS vs CHANGE DATA CAPTURE                   │
 ├───────────────────────────────────────────────────────────────────────┤
@@ -816,7 +817,7 @@ EventBus.publish(event);
 
 ### 3. Using Platform Events for Synchronous-Style Flow Orchestration
 
-```
+```javascript
 // ❌ WRONG: Using events to simulate synchronous request/response
 Flow A → Publish "Request" Event → Subscriber triggers Flow B → Publish "Response" Event → ???
 ```

package/skills/integration-connectivity-generate/references/external-services-guide.md

@@ -7,7 +7,7 @@ External Services in Salesforce automatically generate Apex classes from OpenAPI
 
 ## How It Works
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────┐
 │  EXTERNAL SERVICE FLOW                                          │
 ├─────────────────────────────────────────────────────────────────┤
@@ -43,6 +43,9 @@ External Services in Salesforce automatically generate Apex classes from OpenAPI
 
 ### Via Metadata API
 
+**Template**: `assets/external-services/openapi-registration.externalServiceRegistration-meta.xml`
+**Reference**: `assets/external-services/external-service-operations.md`
+
 ```xml
 <?xml version="1.0" encoding="UTF-8"?>
 <ExternalServiceRegistration xmlns="http://soap.sforce.com/2006/04/metadata">

package/skills/integration-connectivity-generate/references/messaging-api-v2.md

@@ -7,7 +7,7 @@ This guide covers building custom clients for Messaging for In-App and Web (MIAW
 
 ## Overview
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────┐
 │                    MIAW CUSTOM CLIENT ARCHITECTURE                       │
 ├─────────────────────────────────────────────────────────────────────────┤
@@ -47,7 +47,7 @@ This guide covers building custom clients for Messaging for In-App and Web (MIAW
 
 ### Embedded Service Deployment
 
-```
+```text
 Setup → Embedded Service Deployments → New Deployment
 ├─ Type: Messaging for In-App and Web
 ├─ Channel: Web

package/skills/integration-connectivity-generate/references/named-credentials-automation.md

@@ -11,7 +11,7 @@ This guide explains how to automate Named Credential configuration using the int
 
 Enhanced Named Credentials = **External Credential** + **Named Credential** + **Endpoint Security**
 
-```
+```text
 External Credential (stores the API key securely)
          ↓
 Named Credential (references the External Credential)

package/skills/integration-connectivity-generate/references/named-credentials-guide.md

@@ -20,7 +20,7 @@ Named Credentials provide secure storage of authentication credentials and endpo
 - Permission Set-based access control
 - More secure and flexible
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────┐
 │  CREDENTIAL ARCHITECTURE (API 61+)                              │
 ├─────────────────────────────────────────────────────────────────┤
@@ -46,6 +46,9 @@ Named Credentials provide secure storage of authentication credentials and endpo
 
 ### 1. OAuth 2.0 Client Credentials
 
+**Template**: `assets/named-credentials/oauth-client-credentials.namedCredential-meta.xml`
+**Template**: `assets/external-credentials/oauth-external-credential.externalCredential-meta.xml`
+
 **Use Case**: Server-to-server integration without user context
 
 ```apex
@@ -63,6 +66,9 @@ req.setMethod('GET');
 
 ### 2. OAuth 2.0 JWT Bearer
 
+**Template**: `assets/named-credentials/oauth-jwt-bearer.namedCredential-meta.xml`
+**Template**: `assets/external-credentials/jwt-external-credential.externalCredential-meta.xml`
+
 **Use Case**: Certificate-based server-to-server auth
 
 **Prerequisites**:
@@ -78,6 +84,8 @@ req.setMethod('GET');
 
 ### 3. Certificate-Based (Mutual TLS)
 
+**Template**: `assets/named-credentials/certificate-auth.namedCredential-meta.xml`
+
 **Use Case**: High-security integrations requiring client certificate
 
 **Setup**:
@@ -88,6 +96,8 @@ req.setMethod('GET');
 
 ### 4. Basic Auth / API Key
 
+**Template**: `assets/named-credentials/custom-auth.namedCredential-meta.xml`
+
 **Use Case**: Simple APIs, internal systems
 
 **Pattern for API Key**:
@@ -134,7 +144,7 @@ public class ExternalServiceCallout {
 
 ### Pattern 2: Multiple Environments
 
-```
+```text
 Named Credentials:
 ├── MyAPI_Dev     → https://api-dev.example.com
 ├── MyAPI_UAT     → https://api-uat.example.com

package/skills/integration-connectivity-generate/references/platform-events-guide.md

@@ -60,7 +60,7 @@ Platform Events enable event-driven architecture in Salesforce. They provide a s
 
 ### File Location
 
-```
+```text
 force-app/main/default/objects/Order_Update_Event__e/Order_Update_Event__e.object-meta.xml
 ```
 
@@ -125,7 +125,7 @@ trigger OrderUpdateSubscriber on Order_Update_Event__e (after insert) {
 
 External systems can subscribe using CometD streaming:
 
-```
+```text
 /event/Order_Update_Event__e
 ```
 
@@ -268,7 +268,7 @@ WHERE Topic = 'Order_Update_Event__e'
 
 Use CometD client to connect to Streaming API:
 
-```
+```text
 Endpoint: /cometd/62.0
 Channel: /event/Order_Update_Event__e
 ```

package/skills/integration-connectivity-generate/references/rest-callout-patterns.md

@@ -21,7 +21,7 @@ This guide covers patterns for making HTTP callouts from Salesforce Apex to exte
 - Background processing
 - Long-running operations
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────┐
 │  CALLOUT CONTEXT DECISION                                       │
 ├─────────────────────────────────────────────────────────────────┤

package/skills/integration-connectivity-generate/references/scoring-rubric.md

@@ -25,7 +25,7 @@
 
 ## Scoring Output Format
 
-```
+```text
 📊 INTEGRATION SCORE: XX/120 ⭐⭐⭐⭐ Rating
 ════════════════════════════════════════════════════
 

package/skills/integration-connectivity-generate/references/security-best-practices.md

@@ -38,7 +38,7 @@ req.setEndpoint('https://api.example.com');
 
 Request only necessary scopes:
 
-```
+```text
 ✅ read:orders write:orders
 ❌ admin:* read:* write:*
 ```
@@ -54,7 +54,7 @@ Request only necessary scopes:
 
 For mobile or SPA clients:
 
-```
+```text
 Use Authorization Code with PKCE, not Implicit flow
 ```
 
@@ -62,6 +62,9 @@ Use Authorization Code with PKCE, not Implicit flow
 
 ### Remote Site Settings
 
+**Template**: `assets/endpoint-security/example.remoteSite-meta.xml`
+**Template**: `assets/endpoint-security/example.cspTrustedSite-meta.xml`
+
 - Only allow necessary domains
 - Don't use wildcard domains
 - Review and audit regularly

package/skills/integration-connectivity-generate/scripts/configure-named-credential.sh

@@ -72,6 +72,12 @@ EXTERNAL_CREDENTIAL_NAME=$1
 PRINCIPAL_NAME=$2
 ORG_ALIAS=$3
 
+# Validate EXTERNAL_CREDENTIAL_NAME for SOQL safety
+if [[ ! "$EXTERNAL_CREDENTIAL_NAME" =~ ^[a-zA-Z0-9_]+$ ]]; then
+  echo -e "${RED}ERROR: Invalid credential name '$EXTERNAL_CREDENTIAL_NAME'. Only alphanumeric and underscores allowed.${NC}" >&2
+  exit 1
+fi
+
 # Validate sf CLI is installed
 if ! command -v sf &> /dev/null; then
     echo -e "${RED}Error: Salesforce CLI (sf) is not installed${NC}"
@@ -138,10 +144,16 @@ fi
 echo -e "${GREEN}✓ API key received${NC}"
 echo ""
 
+# Escape single quotes to prevent Apex injection
+API_KEY_ESCAPED="${API_KEY//\'/\\\'}"
+EXTERNAL_CREDENTIAL_NAME_ESCAPED="${EXTERNAL_CREDENTIAL_NAME//\'/\\\'}"
+PRINCIPAL_NAME_ESCAPED="${PRINCIPAL_NAME//\'/\\\'}"
+
 # Generate Apex code to configure credential
 echo -e "${BLUE}► Generating Apex code to configure credential...${NC}"
 
 TEMP_APEX=$(mktemp /tmp/set-credential-XXXXXX.apex)
+trap 'rm -f "$TEMP_APEX"' EXIT
 
 cat > "$TEMP_APEX" << EOF
 // Auto-generated by configure-named-credential.sh
@@ -151,14 +163,14 @@ cat > "$TEMP_APEX" << EOF
 ConnectApi.CredentialInput newCredentials = new ConnectApi.CredentialInput();
 
 // Specify the External Credential
-newCredentials.externalCredential = '$EXTERNAL_CREDENTIAL_NAME';
+newCredentials.externalCredential = '$EXTERNAL_CREDENTIAL_NAME_ESCAPED';
 
 // Set authentication protocol
 newCredentials.authenticationProtocol = ConnectApi.CredentialAuthenticationProtocol.Custom;
 
 // Define the principal
 newCredentials.principalType = ConnectApi.CredentialPrincipalType.NamedPrincipal;
-newCredentials.principalName = '$PRINCIPAL_NAME';
+newCredentials.principalName = '$PRINCIPAL_NAME_ESCAPED';
 
 // Create credentials map
 Map<String, ConnectApi.CredentialValueInput> creds = new Map<String, ConnectApi.CredentialValueInput>();
@@ -166,7 +178,7 @@ Map<String, ConnectApi.CredentialValueInput> creds = new Map<String, ConnectApi.
 // Create API key parameter
 ConnectApi.CredentialValueInput apiKeyParam = new ConnectApi.CredentialValueInput();
 apiKeyParam.encrypted = true; // Required for security
-apiKeyParam.value = '$API_KEY';
+apiKeyParam.value = '$API_KEY_ESCAPED';
 
 // Add to credentials map
 creds.put('apiKey', apiKeyParam);
@@ -230,7 +242,6 @@ else
     echo -e "${YELLOW}Apex execution output:${NC}"
     echo "$APEX_RESULT"
     echo ""
-    echo -e "${YELLOW}Temp Apex file saved at: $TEMP_APEX${NC}"
-    echo "Review the file and run manually if needed"
+    echo -e "${YELLOW}Re-run this script to retry.${NC}"
     exit 1
 fi

package/skills/integration-connectivity-generate/scripts/set-api-credential.sh

@@ -45,6 +45,12 @@ SETTING_NAME=$1
 API_KEY=$2
 ORG_ALIAS=$3
 
+# Validate SETTING_NAME to prevent SOQL injection
+if [[ ! "$SETTING_NAME" =~ ^[a-zA-Z0-9_]+$ ]]; then
+    echo -e "${RED}Error: Invalid setting name '$SETTING_NAME'. Only alphanumeric and underscores allowed.${NC}" >&2
+    exit 1
+fi
+
 # If API key is "-", prompt securely
 if [ "$API_KEY" = "-" ]; then
     echo -e "${YELLOW}Enter API key (input hidden):${NC}"
@@ -58,6 +64,9 @@ if [ -z "$API_KEY" ]; then
     exit 1
 fi
 
+# Escape single quotes in API_KEY for safe interpolation
+API_KEY_ESCAPED="${API_KEY//\'/\\\'}"
+
 # Validate org
 echo -e "${BLUE}Validating org connection...${NC}"
 if ! sf org display --target-org "$ORG_ALIAS" &> /dev/null; then
@@ -120,7 +129,7 @@ if [ -z "$EXISTING_ID" ]; then
     echo -e "${BLUE}Creating new credential record...${NC}"
     sf data create record \
         --sobject API_Credentials__c \
-        --values "Name='$SETTING_NAME' API_Key__c='$API_KEY'" \
+        --values "Name='$SETTING_NAME' API_Key__c='$API_KEY_ESCAPED'" \
         --target-org "$ORG_ALIAS"
     echo -e "${GREEN}✓ Credential created${NC}"
 else
@@ -128,7 +137,7 @@ else
     sf data update record \
         --sobject API_Credentials__c \
         --record-id "$EXISTING_ID" \
-        --values "API_Key__c='$API_KEY'" \
+        --values "API_Key__c='$API_KEY_ESCAPED'" \
         --target-org "$ORG_ALIAS"
     echo -e "${GREEN}✓ Credential updated${NC}"
 fi

package/skills/integration-connectivity-generate/scripts/suggest_credential_setup.py

@@ -1,6 +1,6 @@
 #!/usr/bin/env python3
 """
-Credential Setup Suggestion Hook for building-sf-integrations
+Credential Setup Suggestion Hook for integration-connectivity-generate
 
 Detects when credential metadata files are created and suggests
 running the appropriate automation scripts.
@@ -19,6 +19,7 @@ import os
 import re
 import sys
 from pathlib import Path
+from typing import Optional
 
 # File pattern matchers
 PATTERNS = {
@@ -82,7 +83,7 @@ SCRIPT_RECOMMENDATIONS = {
 }
 
 
-def detect_file_type(file_path: str) -> str | None:
+def detect_file_type(file_path: str) -> Optional[str]:
     """Detect the credential file type from the file path."""
     filename = os.path.basename(file_path)
 
@@ -204,7 +205,7 @@ def generate_suggestion_message(file_type: str, cred_name: str, file_context: di
     if file_context.get('has_oauth'):
         lines.extend([
             '',
-            '⚠️  OAuth detected: Consider using /configuring-connected-apps to',
+            '⚠️  OAuth detected: Consider using /integration-connectivity-connected-app-configure to',
             '    create the Connected App for this credential.',
         ])
 

package/skills/integration-connectivity-generate/scripts/validate_integration.py

@@ -1,6 +1,6 @@
 #!/usr/bin/env python3
 """
-building-sf-integrations Validation Script
+integration-connectivity-generate Validation Script
 
 Validates integration-related files against best practices.
 Scoring: 120 points across 6 categories.

package/skills/mobile-platform-native-capabilities-integrate/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mobile-platform-native-capabilities-integrate
-description: "Build a Salesforce LWC that uses native mobile device capabilities — barcode scanner, biometrics, location, NFC, calendar, contacts, document scanner, geofencing, AR space capture, app review, and payments. Use this skill when the user asks for an LWC that scans a barcode, captures a photo of a document, reads location or geofences, prompts for biometrics, reads/writes the device calendar or contacts, taps NFC, takes a payment, prompts for an app review, or scans an AR space. Also triggers on \"lightning/mobileCapabilities\", \"mobile capability\", \"Nimbus\", \"device capability\". Do not use for mobile offline / Komaci priming reviews (use `mobile-platform-offline-validate`) or for picking generic Lightning base components (use a generic Lightning base components skill)."
+description: "Build a Salesforce LWC that uses native mobile device capabilities — barcode scanner, biometrics, location, NFC, calendar, contacts, document scanner, geofencing, AR space capture, app review, and payments. Use this skill when the user asks for an LWC that scans a barcode, captures a photo of a document, reads location or geofences, prompts for biometrics, reads/writes the device calendar or contacts, taps NFC, takes a payment, prompts for an app review, or scans an AR space. Also triggers on \"lightning/mobileCapabilities\", \"mobile capability\", \"Nimbus\", \"device capability\". Do not use for mobile offline / Komaci priming reviews (use `mobile-platform-offline-validate`) or for picking generic Lightning base components (use `design-systems-slds-apply`)."
 metadata:
   version: "1.0"
 ---
@@ -32,8 +32,8 @@ Do NOT use this skill for:
 
 - Mobile-offline review of an LWC (lwc:if, inline GraphQL, Komaci-priming
   violations) — use `mobile-platform-offline-validate`.
-- Picking generic Lightning Base Components — use
-  `using-lightning-base-components`.
+- Choosing or styling generic Lightning Base Components / SLDS blueprints —
+  use `design-systems-slds-apply`.
 
 ## Prerequisites
 

package/skills/omnistudio-callable-apex-generate/README.md

@@ -17,7 +17,7 @@ rubric and migration guidance from legacy `VlocityOpenInterface` implementations
 
 ### 1. Invoke the skill
 
-```
+```text
 Skill: omnistudio-callable-apex-generate
 Request: "Create a callable implementation for Order actions with createOrder and cancelOrder"
 ```
@@ -66,10 +66,6 @@ The skill generates:
 | platform-apex-test-run | Run tests and analyze coverage |
 | platform-metadata-deploy | Deploy callable classes to an org |
 
-## Documentation
-
-- [Skill Instructions](SKILL.md)
-
 ### VlocityOpenInterface / VlocityOpenInterface2
 
 The skill includes design (Phase 2) and implementation (Phase 3) guidance for the Open Interface signature `invokeMethod(String methodName, Map<String, Object> inputMap, Map<String, Object> outputMap, Map<String, Object> options)`. Use this when extending legacy OmniStudio/Vlocity integration points or building dual Callable + Open Interface implementations.

package/skills/omnistudio-callable-apex-generate/SKILL.md

@@ -53,7 +53,7 @@ Then:
 - Output schema (consistent response envelope)
 
 **Recommended response envelope**:
-```
+```json
 {
   "success": true|false,
   "data": {...},
@@ -70,7 +70,7 @@ Then:
 
 When designing for legacy Open Interface extensions (or dual Callable + Open Interface support), map the signature:
 
-```
+```text
 invokeMethod(String methodName, Map<String, Object> inputMap, Map<String, Object> outputMap, Map<String, Object> options)
 ```
 
@@ -171,7 +171,7 @@ action contract stable.
 | **Testing** | 15 | Positive/negative/contract/bulk tests |
 | **Documentation** | 10 | ApexDoc (`/** ... */` block comments — Salesforce Apex documentation standard) for class and action methods |
 
-**Thresholds**: ✅ 90+ (Ready) | ⚠️ 70-89 (Review) | ❌ <70 (Block)
+**Thresholds**: [PASS] 90+ (Ready) | [REVIEW] 70-89 (Review) | [BLOCK] <70 (Block)
 
 ---
 
@@ -266,10 +266,20 @@ Deliverables produced by this skill:
 | `examples/Test_VlocityOpenInterfaceConversion/MyCustomCallable.cls` | Phase 3 — migration pattern from legacy `VlocityOpenInterface` |
 | `examples/Test_VlocityOpenInterfaceConversion/MyCustomCallableTest.cls` | Phase 4 — test class for VlocityOpenInterface migration example |
 | `examples/Test_VlocityOpenInterfaceConversion/IndustriesCallableException.cls` | Phase 3 — custom exception class deployed alongside VlocityOpenInterface conversion |
-| `examples/Test_VlocityOpenInterfaceConversion/MyCustomVlocityOpenInterface2.cls` | Phase 3 — the original legacy VlocityOpenInterface2 class before migration |
+| `examples/Test_VlocityOpenInterfaceConversion/MyCustomClass.cls` | Phase 3 — the original legacy VlocityOpenInterface class before migration |
 | `examples/Test_VlocityOpenInterfaceConversion/TRANSCRIPT.md` | Reference — reasoning transcript for VlocityOpenInterface conversion |
 | `examples/Test_VlocityOpenInterface2Conversion/MyCustomCallable.cls` | Phase 3 — migration pattern from `VlocityOpenInterface2` |
 | `examples/Test_VlocityOpenInterface2Conversion/MyCustomCallableTest.cls` | Phase 4 — test class for VlocityOpenInterface2 migration example |
 | `examples/Test_VlocityOpenInterface2Conversion/IndustriesCallableException.cls` | Phase 3 — custom exception class deployed alongside VlocityOpenInterface2 conversion |
 | `examples/Test_VlocityOpenInterface2Conversion/MyCustomRemoteClass.cls` | Phase 3 — remote class used by the VlocityOpenInterface2 migration example |
 | `examples/Test_VlocityOpenInterface2Conversion/TRANSCRIPT.md` | Reference — reasoning transcript for VlocityOpenInterface2 conversion |
+
+---
+
+## Pre-Delivery Checklist
+
+- [ ] `call()` null-checks `args` before accessing keys
+- [ ] `IndustriesCallableException` class included in deployment package
+- [ ] Namespace qualified for `omnistudio.VlocityOpenInterface2` (if applicable)
+- [ ] `outputMap` keys documented per action (success and error cases)
+- [ ] Migrated callers read return value instead of `outputMap` by reference

package/skills/omnistudio-callable-apex-generate/assets/pattern_callable_vanilla.cls

@@ -20,7 +20,14 @@ public with sharing class Industries_XxxCallable implements System.Callable {
     }
 
     private Map<String, Object> actionOne(Map<String, Object> args) {
-        // 1. Validate required keys (e.g. args.get('requiredKey'))
+        // 1. Validate required keys
+        Map<String, Object> inputMap = (Map<String, Object>) args.get('inputMap');
+        if (inputMap == null || inputMap.isEmpty()) {
+            return new Map<String, Object>{
+                'success' => false,
+                'error'   => 'Missing required input in inputMap'
+            };
+        }
         // 2. Coerce types safely
         // 3. Run business logic (SOQL with WITH USER_MODE, DML with sharing)
         // 4. Return response envelope

package/skills/omnistudio-callable-apex-generate/examples/Test_VlocityOpenInterface2Conversion/TRANSCRIPT.md

@@ -43,7 +43,7 @@ Convert a VlocityOpenInterface2 implementation (`MyCustomRemoteClass`) to `Syste
   - `switch on action` with `when else` throwing `IndustriesCallableException`
 
 - **Response envelope:**
-  ```
+  ```json
   { success, data: { total }, errors }
   ```
 

package/skills/omnistudio-callable-apex-generate/examples/Test_VlocityOpenInterfaceConversion/TRANSCRIPT.md

@@ -2,7 +2,7 @@
 
 ## Task
 
-Convert `MyCustomVlocityOpenInterface2.cls` (VlocityOpenInterface) to System.Callable and create a test class. Keep a transcript of reasoning and skills used.
+Convert `MyCustomClass.cls` (VlocityOpenInterface) to System.Callable and create a test class. Keep a transcript of reasoning and skills used.
 
 ---
 

package/skills/omnistudio-datamapper-generate/SKILL.md

@@ -167,7 +167,7 @@ Use the **platform-metadata-deploy** skill: "Proceed with actual deployment to [
 | **Performance** | 15 | Bounded queries with LIMIT/filters; Turbo Extract for read-heavy scenarios; minimal relationship depth; indexed filter fields |
 | **Documentation** | 15 | Description on OmniDataTransform record; field mapping rationale documented; consuming components identified |
 
-**Thresholds**: ✅ 90+ (Deploy) | ⚠️ 67-89 (Review) | ❌ <67 (Block - fix required)
+**Thresholds**: [PASS] 90+ (Deploy) | [REVIEW] 67-89 (Review) | [BLOCK] <67 (Block - fix required)
 
 ---
 

package/skills/omnistudio-datamapper-generate/assets/completion-summary-template.md

@@ -4,7 +4,7 @@ Use these templates in Phase 3 (scoring output) and Phase 5 (completion summary)
 
 ## Scoring Output (Phase 3)
 
-```
+```text
 Score: XX/100 Rating
 |- Design & Naming: XX/20
 |- Field Mapping: XX/25
@@ -17,7 +17,7 @@ Score: XX/100 Rating
 
 ## Completion Summary (Phase 5)
 
-```
+```text
 Data Mapper Complete: [Name]
   Type: [Extract|Transform|Load|Turbo Extract]
   Target Object(s): [Object1, Object2]

package/skills/omnistudio-datamapper-generate/references/best-practices.md

@@ -65,7 +65,7 @@ Do NOT use Load when:
 
 Always specify fields explicitly. Never rely on wildcard or "all fields" selection.
 
-```
+```text
 Good:  Account.Name, Account.Industry, Account.BillingCity
 Bad:   Account.* (extracts all fields, wastes bandwidth and heap)
 ```
@@ -74,14 +74,14 @@ Bad:   Account.* (extracts all fields, wastes bandwidth and heap)
 
 Data Mapper fields use dot-notation paths for input and output:
 
-```
+```text
 Input Path:   AccountData.Name
 Output Path:  Account.Name
 ```
 
 For nested structures:
 
-```
+```text
 Input Path:   Response.data.accounts[0].name
 Output Path:  AccountList.Name
 ```
@@ -106,7 +106,7 @@ When loading records with lookup relationships:
 2. Specify the lookup object and match field (e.g., `Account.Name` to resolve `AccountId`)
 3. Handle cases where the lookup returns no match (set default or fail gracefully)
 
-```
+```text
 Field:         AccountId
 Lookup Object: Account
 Match Field:   Name
@@ -132,7 +132,7 @@ For Extract and Turbo Extract, filter on indexed fields whenever possible:
 
 Place the most selective filter first to reduce the result set early:
 
-```
+```text
 Good:  WHERE Id = :recordId AND Status = 'Active'
 Bad:   WHERE Status = 'Active' AND Id = :recordId
 ```
@@ -141,7 +141,7 @@ Bad:   WHERE Status = 'Active' AND Id = :recordId
 
 Limit relationship traversal to 2 levels for performance:
 
-```
+```text
 Good:  Account.Owner.Name (1 level)
 Bad:   Account.Parent.Parent.Parent.Owner.Name (3+ levels)
 ```
@@ -150,7 +150,7 @@ Bad:   Account.Parent.Parent.Parent.Owner.Name (3+ levels)
 
 Always set a LIMIT on Extract queries unless the consuming component guarantees a bounded input:
 
-```
+```text
 LIMIT 200    -- Standard batch size
 LIMIT 2000   -- Maximum for most UI scenarios
 LIMIT 10000  -- Absolute maximum, use only with pagination
@@ -189,7 +189,7 @@ When mapping fields that may be null:
 
 Extract supports parent-to-child relationship queries:
 
-```
+```text
 Object: Account
 Fields: Name, Industry
 Child Relationship: Contacts (Contact)
@@ -212,7 +212,7 @@ Output structure:
 
 Extract supports child-to-parent traversal via dot notation:
 
-```
+```text
 Object: Contact
 Fields: FirstName, LastName, Account.Name, Account.Industry
 ```