@salesforce/afv-skills 1.29.0 → 1.30.0

package/skills/integration-connectivity-connected-app-configure/README.md

@@ -23,21 +23,21 @@ This skill helps you create and manage:
 
 ### Create a Connected App
 
-```
+```text
 Use the integration-connectivity-connected-app-configure skill to create a Connected App named "MyIntegration"
 with API and RefreshToken scopes for server-to-server integration.
 ```
 
 ### Create an External Client App
 
-```
+```text
 Use the integration-connectivity-connected-app-configure skill to create an External Client App named
 "MobileApp" for a mobile application with PKCE enabled.
 ```
 
 ### Review Existing Apps
 
-```
+```text
 Use the integration-connectivity-connected-app-configure skill to review and score my existing Connected Apps
 for security best practices.
 ```
@@ -70,7 +70,7 @@ for security best practices.
 
 ## Directory Structure
 
-```
+```text
 integration-connectivity-connected-app-configure/
 ├── skills/
 │   └── integration-connectivity-connected-app-configure/
@@ -96,4 +96,3 @@ integration-connectivity-connected-app-configure/
 ## Dependencies
 
 - **platform-metadata-deploy**: For deploying apps to orgs
-- **sf-metadata**: For creating related metadata (Named Credentials)

package/skills/integration-connectivity-connected-app-configure/SKILL.md

@@ -85,7 +85,7 @@ Read the appropriate template before generating — do not build from scratch:
 | `assets/eca-policies.xml` | ECA configurable policies |
 
 If you need source-controlled ECA OAuth security metadata, retrieve it from an org first and treat the retrieved file as the schema source of truth:
-```
+```sh
 sf project retrieve start --metadata ExtlClntAppOauthSecuritySettings:<AppName> --target-org <alias>
 ```
 
@@ -172,7 +172,7 @@ When finishing, confirm and report in this order:
 5. **Next deployment / testing step**
 
 Suggested output shape:
-```
+```text
 App: <name>
 Type: Connected App | External Client App
 Flow: <oauth flow>

package/skills/integration-connectivity-connected-app-configure/references/example-usage.md

@@ -6,7 +6,7 @@ Real-world examples of using the integration-connectivity-connected-app-configur
 ## Example 1: Create a Basic API Integration Connected App
 
 **Request**:
-```
+```text
 Use the integration-connectivity-connected-app-configure skill to create a Connected App named "DataSyncIntegration"
 for syncing data with our external ERP system. It needs API access and refresh tokens.
 Contact email: admin@company.com
@@ -42,7 +42,7 @@ Contact email: admin@company.com
 ## Example 2: Create a JWT Bearer App for CI/CD
 
 **Request**:
-```
+```text
 Create a Connected App for our CI/CD pipeline using JWT Bearer flow.
 Name it "GitHubActionsDeployment" and use certificate "GH_Actions_Cert".
 ```
@@ -77,7 +77,7 @@ Name it "GitHubActionsDeployment" and use certificate "GH_Actions_Cert".
 ## Example 3: Create a Mobile App with External Client App
 
 **Request**:
-```
+```text
 Create an External Client App for our mobile app "FieldServiceMobile".
 It needs PKCE enabled, refresh tokens, and should be packageable for distribution.
 ```
@@ -134,7 +134,7 @@ sf project retrieve start \
 ## Example 4: Review Existing Connected Apps
 
 **Request**:
-```
+```text
 Review and score my existing Connected Apps for security best practices.
 ```
 
@@ -145,7 +145,7 @@ Review and score my existing Connected Apps for security best practices.
 4. Generate report
 
 **Sample Report**:
-```
+```text
 📊 CONNECTED APP SECURITY REVIEW
 ════════════════════════════════════════════════════════════════
 
@@ -180,7 +180,7 @@ LegacyERPConnector:
 ## Example 5: Migrate Connected App to External Client App
 
 **Request**:
-```
+```text
 Migrate our "SalesPortal" Connected App to an External Client App for better security.
 ```
 
@@ -191,7 +191,7 @@ Migrate our "SalesPortal" Connected App to an External Client App for better sec
 4. Provide migration checklist
 
 **Output**:
-```
+```text
 📦 MIGRATION PLAN: SalesPortal → External Client App
 ════════════════════════════════════════════════════════════════
 

package/skills/integration-connectivity-connected-app-configure/references/migration-guide.md

@@ -72,7 +72,7 @@ List all systems using each Connected App:
 
 #### 2.2 Plan Credential Rollover
 
-```
+```text
 Timeline Example:
 Week 1: Create ECA, deploy to DevHub
 Week 2: Update integration systems with new credentials

package/skills/integration-connectivity-connected-app-configure/references/oauth-flows-reference.md

@@ -7,7 +7,7 @@ Detailed OAuth flow patterns, configuration examples, and implementation guidanc
 
 ## Flow Selection Decision Tree
 
-```
+```text
 START
 │
 ├─ Do you have a backend server?

package/skills/integration-connectivity-connected-app-configure/references/testing-validation-guide.md

@@ -234,7 +234,7 @@ Client Credentials flow still requires post-deployment admin validation. Even wi
 
 ### Minimal ECA (API Integration)
 
-```
+```text
 Files:
 ├── externalClientApps/MyApp.eca-meta.xml
 ├── extlClntAppOauthSettings/MyApp.ecaOauth-meta.xml
@@ -246,7 +246,7 @@ PKCE: false (confidential client)
 
 ### Mobile App ECA (PKCE)
 
-```
+```text
 Files:
 ├── externalClientApps/MobileApp.eca-meta.xml
 ├── extlClntAppOauthSettings/MobileApp.ecaOauth-meta.xml
@@ -259,7 +259,7 @@ Callback: com.example.app://oauth/callback
 
 ### Server-to-Server ECA
 
-```
+```text
 Files:
 ├── externalClientApps/ServiceApp.eca-meta.xml
 ├── extlClntAppOauthSettings/ServiceApp.ecaOauth-meta.xml

package/skills/integration-connectivity-generate/README.md

@@ -17,7 +17,7 @@ Creates comprehensive Salesforce integrations with 120-point scoring. Build secu
 
 ### 1. Invoke the skill
 
-```
+```text
 Skill: integration-connectivity-generate
 Request: "Create a Named Credential for Stripe API with OAuth"
 ```

package/skills/integration-connectivity-generate/SKILL.md

@@ -189,3 +189,9 @@ When this skill completes an integration task, it produces:
 | 90–107 | good design with some hardening left |
 | 72–89 | workable but needs architectural review |
 | < 72 | unsafe / incomplete for deployment |
+
+---
+
+## Pre-Delivery Checklist
+
+- [ ] Never hardcode credentials — all secrets stored in Named Credentials or External Credentials

package/skills/integration-connectivity-generate/assets/callouts/rest-queueable-callout.cls

@@ -182,7 +182,7 @@ public with sharing class {{ServiceName}}QueueableCallout implements Queueable,
      * @param recordId Salesforce record ID
      */
     private void deleteExternalRecord(Id recordId) {
-        // Query for external ID
+        // DELIBERATE: per-record query acceptable at BATCH_SIZE=10; refactor to bulk query if increasing batch size
         {{ObjectName}} record = [
             SELECT External_Id__c
             FROM {{ObjectName}}

package/skills/integration-connectivity-generate/assets/external-services/external-service-operations.md

@@ -8,7 +8,7 @@ External Services in Salesforce auto-generate Apex classes from OpenAPI specific
 
 When you register an External Service named `MyAPI`, Salesforce generates:
 
-```
+```text
 ExternalService.MyAPI                          - Main service class
 ExternalService.MyAPI_operationName_Request    - Request wrapper for each operation
 ExternalService.MyAPI_operationName_Response   - Response wrapper for each operation

package/skills/integration-connectivity-generate/assets/soap/wsdl2apex-guide.md

@@ -43,7 +43,7 @@ Salesforce WSDL2Apex has limitations. Check for:
 
 For a WSDL defining `CustomerService` with operation `getCustomer`:
 
-```
+```text
 AsyncCustomerService.cls         - Async version of service
 CustomerService.cls              - Main stub class with methods
 GetCustomerRequest.cls           - Request wrapper

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

@@ -409,6 +409,8 @@ Headers: Idempotency-Key: {{recordId}}-{{timestamp}}
 
 ### WSDL2Apex Process
 
+**Reference**: `assets/soap/wsdl2apex-guide.md`
+
 SOAP integrations in Salesforce use WSDL2Apex to auto-generate Apex classes from WSDL files.
 
 #### Step-by-Step Process
@@ -660,6 +662,8 @@ public with sharing class SoapQueueableCallout implements Queueable, Database.Al
 
 ### Error Handling Patterns
 
+**Template**: `assets/callouts/http-response-handler.cls`
+
 ```apex
 try {
     HttpResponse res = makeCallout();

package/skills/integration-connectivity-generate/references/cdc-guide.md

@@ -7,7 +7,7 @@ Change Data Capture publishes change events for Salesforce records, enabling nea
 
 ## How CDC Works
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────┐
 │  CHANGE DATA CAPTURE FLOW                                       │
 ├─────────────────────────────────────────────────────────────────┤
@@ -124,7 +124,7 @@ trigger AccountCDC on AccountChangeEvent (after insert) {
 
 ### External (CometD)
 
-```
+```text
 Channel: /data/AccountChangeEvent
 ```
 

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.