@salesforce/afv-skills 1.28.0 → 1.30.0

package/skills/external-diagram-mermaid-generate/assets/integration/api-sequence.md

@@ -217,7 +217,7 @@ sequenceDiagram
 
 ## ASCII Fallback Template - Outbound Integration
 
-```
+```text
 ┌───────────────┐  ┌───────────────┐  ┌───────────────┐  ┌───────────────┐
 │    Trigger    │  │   Queueable   │  │     Named     │  │   External    │
 │               │  │               │  │   Credential  │  │     API       │

package/skills/external-diagram-mermaid-generate/assets/oauth/authorization-code-pkce.md

@@ -80,7 +80,7 @@ sequenceDiagram
 
 ## ASCII Fallback Template
 
-```
+```text
 ┌──────────┐     ┌───────────────┐     ┌────────────────────┐
 │  User    │     │  Mobile App   │     │     Salesforce     │
 │          │     │   or SPA      │     │   (Auth Server)    │

package/skills/external-diagram-mermaid-generate/assets/oauth/authorization-code.md

@@ -83,7 +83,7 @@ sequenceDiagram
 
 ## ASCII Fallback Template
 
-```
+```text
 ┌──────────┐     ┌───────────────┐     ┌────────────────────┐
 │  User/   │     │  Application  │     │     Salesforce     │
 │  Browser │     │    Server     │     │  (Auth Server)     │

package/skills/external-diagram-mermaid-generate/assets/oauth/client-credentials.md

@@ -71,7 +71,7 @@ sequenceDiagram
 
 ## ASCII Fallback Template
 
-```
+```text
 ┌───────────────────────┐     ┌────────────────────┐
 │    Service/Backend    │     │     Salesforce     │
 │   (client_id/secret)  │     │   (Auth Server)    │

package/skills/external-diagram-mermaid-generate/assets/oauth/device-authorization.md

@@ -94,7 +94,7 @@ sequenceDiagram
 
 ## ASCII Fallback Template
 
-```
+```text
 ┌──────────┐  ┌───────────┐  ┌────────────┐  ┌────────────────┐
 │  User    │  │  Browser  │  │   Device   │  │   Salesforce   │
 │          │  │(phone/PC) │  │ (CLI/TV)   │  │  (Auth Server) │
@@ -166,7 +166,7 @@ curl -X POST https://login.salesforce.com/services/oauth2/device/code \
 
 ## Step 2: Display to User
 
-```
+```text
 ═══════════════════════════════════════════════════════════════
   To authorize this device, please:
 

package/skills/external-diagram-mermaid-generate/assets/oauth/jwt-bearer.md

@@ -82,7 +82,7 @@ sequenceDiagram
 
 ## ASCII Fallback Template
 
-```
+```text
 ┌───────────────────────┐     ┌────────────────────┐
 │     Server/CI/CD      │     │     Salesforce     │
 │    (Private Key)      │     │   (Certificate)    │
@@ -145,7 +145,7 @@ sequenceDiagram
 ```
 
 ### Signature
-```
+```text
 RS256(
   base64URLEncode(header) + "." + base64URLEncode(payload),
   privateKey

package/skills/external-diagram-mermaid-generate/assets/oauth/refresh-token.md

@@ -66,7 +66,7 @@ sequenceDiagram
 
 ## ASCII Fallback Template
 
-```
+```text
 ┌───────────────────────┐     ┌────────────────────┐
 │     Application       │     │     Salesforce     │
 │   (stored tokens)     │     │   (Auth Server)    │

package/skills/external-diagram-mermaid-generate/assets/oauth/user-agent-social-sign-on.md

@@ -115,7 +115,7 @@ sequenceDiagram
 
 ## ASCII Fallback Template
 
-```
+```text
 ┌────────────────┐     ┌────────────────────┐     ┌─────────────────────┐
 │     Client     │     │    Salesforce      │     │   OIDC Provider     │
 │  (Mobile App)  │     │ (Auth/RP Server)   │     │  (Google/Facebook)  │
@@ -221,7 +221,7 @@ sequenceDiagram
 
 ### Auth. Provider Setup
 
-```
+```text
 Setup → Auth. Providers → New
 ├── Provider Type: OpenID Connect (or specific: Google, Facebook)
 ├── Consumer Key: [From OP Developer Console]

package/skills/external-diagram-mermaid-generate/assets/role-hierarchy/user-hierarchy.md

@@ -211,7 +211,7 @@ flowchart TB
 
 ## ASCII Fallback Template
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │                           ROLE HIERARCHY                                    │
 └─────────────────────────────────────────────────────────────────────────────┘

package/skills/external-diagram-mermaid-generate/references/color-palette.md

@@ -5,7 +5,7 @@ Soft pastel color palette (Tailwind 200-level) with dark borders for clear defin
 
 ## Primary Palette (Tailwind 200 + Dark Borders)
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  COMPONENT                │  FILL (200)  │  STROKE (700+) │  TEXT COLOR    │
 ├───────────────────────────┼──────────────┼────────────────┼────────────────┤
@@ -24,7 +24,7 @@ Soft pastel color palette (Tailwind 200-level) with dark borders for clear defin
 
 ## Subgraph Background Colors (Tailwind 50-level)
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  SUBGRAPH                 │  FILL (50)   │  STROKE (700+) │  STYLE         │
 ├───────────────────────────┼──────────────┼────────────────┼────────────────┤
@@ -45,7 +45,7 @@ Soft pastel color palette (Tailwind 200-level) with dark borders for clear defin
 
 ## Salesforce-Specific Colors
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  SALESFORCE COMPONENT     │  FILL (200)  │  STROKE (700+) │  TEXT COLOR    │
 ├───────────────────────────┼──────────────┼────────────────┼────────────────┤
@@ -62,7 +62,7 @@ Soft pastel color palette (Tailwind 200-level) with dark borders for clear defin
 
 Color coding for data model diagrams by object type:
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  OBJECT TYPE              │  FILL (200)  │  STROKE (700+) │  TEXT COLOR    │
 ├───────────────────────────┼──────────────┼────────────────┼────────────────┤
@@ -114,7 +114,7 @@ style ext fill:#ecfdf5,stroke:#047857,stroke-dasharray:5
 
 ## Status Colors
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  STATUS                   │  FILL (200)  │  STROKE (700+) │  ICON          │
 ├───────────────────────────┼──────────────┼────────────────┼────────────────┤
@@ -132,7 +132,7 @@ style ext fill:#ecfdf5,stroke:#047857,stroke-dasharray:5
 
 Mermaid supports custom fonts via `%%{init}`:
 
-```
+```text
 %%{init: { "fontFamily": "Inter, sans-serif", "fontSize": "14px" }}%%
 ```
 
@@ -187,7 +187,7 @@ Control diagram density with `%%{init}` configuration:
 
 For clean, readable diagrams:
 
-```
+```text
 %%{init: {"flowchart": {"nodeSpacing": 80, "rankSpacing": 70}} }%%
 ```
 
@@ -248,7 +248,7 @@ flowchart TB
 
 ### Simple Label (Recommended)
 
-```
+```json
 ["🤖 agentforce-generate"]
 ```
 
@@ -256,7 +256,7 @@ Keep labels short for consistent rendering.
 
 ### Database/Cylinder
 
-```
+```json
 [(💾 Database)]
 ```
 
@@ -344,7 +344,7 @@ flowchart TB
 ### Detailed Guidelines
 
 #### Node Labels: lowercase (Recommended)
-```
+```text
 ["🤖 agentforce-generate"]    ✅ Preferred
 ["🤖 agentforce-generate"]    ❌ Avoid
 ["🤖 agentforce-generate"]    ❌ Avoid
@@ -357,7 +357,7 @@ flowchart TB
 - Easier to read in compact diagram nodes
 
 #### Subgraph Titles: UPPERCASE
-```
+```text
 subgraph ai["🤖 AI & AGENTS"]           ✅ UPPERCASE
 subgraph ai["🤖 ai & agents"]           ❌ lowercase
 subgraph ai["🤖 Ai & Agents"]           ❌ Title Case
@@ -370,7 +370,7 @@ subgraph ai["🤖 Ai & Agents"]           ❌ Title Case
 - Maximum contrast between group titles and contents
 
 #### Edge Labels: lowercase
-```
+```text
 -->|"schema"|              ✅ lowercase
 -->|"Schema"|              ❌ Title Case
 -->|"SCHEMA"|              ❌ ALL CAPS
@@ -382,7 +382,7 @@ subgraph ai["🤖 Ai & Agents"]           ❌ Title Case
 - Consistent with node label style
 
 #### ASCII Diagrams: UPPERCASE for Headers
-```
+```text
 ┌─────────────────────────────────────┐
 │         SYSTEM LANDSCAPE            │   ✅ UPPERCASE header
 └─────────────────────────────────────┘

package/skills/external-diagram-mermaid-generate/references/diagram-conventions.md

@@ -48,7 +48,7 @@ Consistency guidelines for all sf-diagram generated diagrams.
 
 ### Example Structure
 
-```
+```text
 %%{init: {...}}%%
 sequenceDiagram
     autonumber
@@ -85,7 +85,7 @@ sequenceDiagram
 
 ### Field Representation
 
-```
+```text
 OBJECT {
     Type FieldName Annotation "Comment"
 }
@@ -198,7 +198,7 @@ flowchart LR
 
 ### Box Drawing Characters
 
-```
+```text
 Standard Box:
 ┌─────────────────┐
 │                 │
@@ -228,7 +228,7 @@ Rounded corners (optional):
 
 ### Arrow Characters
 
-```
+```yaml
 Right:  ───>  or  ──▶  or  ────────────────>
 Left:   <───  or  ◀──
 Up:     ▲
@@ -244,7 +244,7 @@ Bidirectional: <──>
 
 ### Example ASCII Sequence
 
-```
+```text
 ┌──────────┐     ┌───────────────┐     ┌────────────────┐
 │  Client  │     │    Server     │     │    Database    │
 └────┬─────┘     └───────┬───────┘     └───────┬────────┘

package/skills/external-diagram-mermaid-generate/references/erd-conventions.md

@@ -13,7 +13,7 @@ Standardized conventions for Salesforce data model diagrams with object type ind
 
 ### Examples
 
-```
+```text
 Account [STD]         → Standard Salesforce object
 Invoice__c [CUST]     → Custom object
 SAP_Product__x [EXT]  → External object via Salesforce Connect

package/skills/external-diagram-mermaid-generate/references/mermaid-styling.md

@@ -7,7 +7,7 @@ Use individual `style` declarations with **Tailwind 200-level pastel fills** and
 
 Add this init directive at the start of every flowchart for optimal readability:
 
-```
+```text
 %%{init: {"flowchart": {"nodeSpacing": 80, "rankSpacing": 70}} }%%
 ```
 
@@ -74,7 +74,7 @@ flowchart TB
 ## Node Label Pattern
 
 Keep labels short (icon + name only). Avoid `<br/>` and `<small>` tags:
-```
+```json
 ["🔐 integration-connectivity-connected-app-configure"]
 ```
 

package/skills/external-diagram-mermaid-generate/references/preview-guide.md

@@ -6,7 +6,7 @@ After generating the diagram, offer the user a localhost preview for real-time i
 ## Start Preview
 
 1. Save Mermaid code to temporary file:
-   ```
+   ```text
    Write: /tmp/mermaid-preview.mmd
    [Mermaid code content]
    ```

package/skills/external-diagram-mermaid-generate/references/usage-examples.md

@@ -8,7 +8,7 @@ Real-world examples of using the sf-diagram skill.
 ## Example 1: OAuth Flow Diagram
 
 ### Request
-```
+```text
 "Create a JWT Bearer OAuth flow diagram for our CI/CD pipeline integration"
 ```
 
@@ -60,7 +60,7 @@ sequenceDiagram
 ```
 
 #### ASCII Fallback
-```
+```text
 ┌───────────────────────┐     ┌────────────────────┐
 │   GitHub Actions      │     │     Salesforce     │
 │   (Private Key)       │     │   (Certificate)    │
@@ -81,7 +81,7 @@ sequenceDiagram
 ```
 
 ### Score
-```
+```yaml
 Score: 72/80 ⭐⭐⭐⭐⭐ Excellent
 ├─ Accuracy: 20/20     ✓ All JWT Bearer steps correct
 ├─ Clarity: 18/20      ✓ Clear labels, good flow
@@ -95,7 +95,7 @@ Score: 72/80 ⭐⭐⭐⭐⭐ Excellent
 ## Example 2: Data Model ERD
 
 ### Request
-```
+```text
 "Create an ERD for our custom Invoice system with Invoice__c, Invoice_Line_Item__c, and relationships to Account and Product"
 ```
 
@@ -168,7 +168,7 @@ erDiagram
 ```
 
 #### ASCII Fallback
-```
+```text
 ┌─────────────────────────┐       ┌─────────────────────────┐
 │        ACCOUNT          │       │        CONTACT          │
 ├─────────────────────────┤       ├─────────────────────────┤
@@ -214,7 +214,7 @@ erDiagram
 ```
 
 ### Score
-```
+```yaml
 Score: 74/80 ⭐⭐⭐⭐⭐ Excellent
 ├─ Accuracy: 20/20     ✓ All relationships correct
 ├─ Clarity: 19/20      ✓ Clear field annotations
@@ -228,7 +228,7 @@ Score: 74/80 ⭐⭐⭐⭐⭐ Excellent
 ## Example 3: Integration Sequence
 
 ### Request
-```
+```text
 "Diagram our real-time Order sync from Salesforce to SAP using Platform Events"
 ```
 
@@ -302,7 +302,7 @@ sequenceDiagram
 ```
 
 ### Score
-```
+```yaml
 Score: 70/80 ⭐⭐⭐⭐ Very Good
 ├─ Accuracy: 19/20     ✓ Platform Event pattern correct
 ├─ Clarity: 18/20      ✓ Good error handling shown
@@ -316,7 +316,7 @@ Score: 70/80 ⭐⭐⭐⭐ Very Good
 ## Example 4: Combined Request
 
 ### Request
-```
+```text
 "I need to document our partner portal authentication.
 Create: 1) The OAuth flow for partner login, 2) The data model showing Partner Account, Portal User, and Opportunities they can see"
 ```

package/skills/external-diagram-mermaid-generate/scripts/README.md

@@ -53,7 +53,7 @@ python mermaid_preview.py status
 
 ## How It Works
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────┐
 │                    Browser Tab                               │
 │  ┌─────────────────────────────────────────────────────┐    │

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
 ```