feat: Skills cleanup: remove internal markers, fix paths, trim descriptions @W-22989405@

actions-user · actions-user · commit c8d3030bb4ce · 2026-06-19T11:04:53.000Z
diff --git a/skills/activating-datacloud/SKILL.md b/skills/activating-datacloud/SKILL.md
@@ -40,7 +40,7 @@ Ask for or infer:
 ## Core Operating Rules
 
 - Verify the upstream segment or insight is healthy before creating downstream delivery assets.
-- Run the shared readiness classifier before mutating activation assets: `node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase act --json`.
+- Run the shared readiness classifier before mutating activation assets: `node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase act --json`.
 - Inspect available platforms and targets before mutating activation setup.
 - Keep destination definitions deterministic and reusable where possible.
 - Treat downstream credential and platform constraints as separate validation concerns.
@@ -52,7 +52,7 @@ Ask for or infer:
 
 ### 1. Classify readiness for act work
 ```bash
-node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase act --json
+node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase act --json
 ```
 
 ### 2. Inspect destinations first
diff --git a/skills/analyzing-omnistudio-dependencies/SKILL.md b/skills/analyzing-omnistudio-dependencies/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: analyzing-omnistudio-dependencies
-description: "Cross-cutting OmniStudio analysis skill for namespace detection, dependency visualization, and impact analysis across OmniScripts, FlexCards, Integration Procedures, and Data Mappers. Use this skill to detect which OmniStudio namespace an org uses, build directed dependency graphs, perform impact analysis, and generate Mermaid diagrams of component relationships. TRIGGER when: user asks about OmniStudio dependencies, wants namespace detection (Core vs vlocity_cmt vs vlocity_ins), needs impact analysis, requests dependency diagrams, or asks which components are affected by a change. DO NOT TRIGGER when: authoring OmniScripts (use building-omnistudio-omniscript), building FlexCards (use building-omnistudio-flexcard), creating Integration Procedures (use building-omnistudio-integration-procedure), or configuring Data Mappers (use building-omnistudio-datamapper)."
+description: "Cross-cutting OmniStudio analysis skill for namespace detection, dependency visualization, and impact analysis across OmniScripts, FlexCards, Integration Procedures, and Data Mappers. TRIGGER when: user asks about OmniStudio dependencies, wants namespace detection (Core vs vlocity_cmt vs vlocity_ins), needs impact analysis, requests dependency graphs or Mermaid diagrams, or asks which components are affected by a change. DO NOT TRIGGER when: authoring OmniScripts (use building-omnistudio-omniscript), building FlexCards (use building-omnistudio-flexcard), creating Integration Procedures (use building-omnistudio-integration-procedure), or configuring Data Mappers (use building-omnistudio-datamapper)."
 metadata:
   version: "1.0"
 ---
diff --git a/skills/building-ui-bundle-app/SKILL.md b/skills/building-ui-bundle-app/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: building-ui-bundle-app
-description: "MUST activate when the user wants to build, create, or generate a React application, React app, web application, single-page application (SPA), or frontend application — even if no project files exist yet. MUST also activate when the project contains a uiBundles/*/src/ directory or sfdx-project.json and the prompt says create, build, construct, or generate a new app, site, or page from scratch — even if the prompt also describes visual styling. MUST also activate when the task spans more than one ui-bundle skill. Use this skill when building a complete app end-to-end. This is the orchestrator that coordinates scaffolding, features, data access, frontend UI, integrations, and deployment in the correct dependency order. Without it, phases execute out of order and the app breaks. Do NOT use for Lightning Experience apps with custom objects (use generating-lightning-app). Do NOT use for single-concern edits to an existing page (use building-ui-bundle-frontend)."
+description: "MUST activate when the user wants to build, create, or generate a React application, React app, web application, single-page application (SPA), or frontend application — even if no project files exist yet. MUST also activate when the project contains a uiBundles/*/src/ directory or sfdx-project.json and the prompt says create, build, construct, or generate a new app, site, or page from scratch — even if the prompt also describes visual styling. MUST also activate when the task spans more than one ui-bundle skill. Use this skill when building a complete app end-to-end. Do NOT use for Lightning Experience apps with custom objects (use generating-lightning-app). Do NOT use for single-concern edits to an existing page (use building-ui-bundle-frontend)."
 metadata:
   version: "1.0"
   related-skills: generating-ui-bundle-metadata, generating-ui-bundle-features, using-ui-bundle-salesforce-data, building-ui-bundle-frontend, implementing-ui-bundle-agentforce-conversation-client, implementing-ui-bundle-file-upload, deploying-ui-bundle, generating-ui-bundle-site, generating-ui-bundle-custom-app
diff --git a/skills/connecting-datacloud/SKILL.md b/skills/connecting-datacloud/SKILL.md
@@ -43,7 +43,7 @@ Ask for or infer:
 ## Core Operating Rules
 
 - Verify the plugin runtime first; see [../orchestrating-datacloud/references/plugin-setup.md](../orchestrating-datacloud/references/plugin-setup.md).
-- Run the shared readiness classifier before mutating connections: `node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase connect --json`.
+- Run the shared readiness classifier before mutating connections: `node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase connect --json`.
 - Prefer read-only discovery before connection creation.
 - Suppress linked-plugin warning noise with `2>/dev/null` for standard usage.
 - Remember that `connection list` requires `--connector-type`.
@@ -59,7 +59,7 @@ Ask for or infer:
 
 ### 1. Classify readiness for connect work
 ```bash
-node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase connect --json
+node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase connect --json
 ```
 
 ### 2. Discover connector types
diff --git a/skills/creating-b2b-commerce-store/SKILL.md b/skills/creating-b2b-commerce-store/SKILL.md
@@ -1,7 +1,6 @@
 ---
 name: creating-b2b-commerce-store
 description: "Interactive workflow to create Commerce B2B Stores and retrieve storefront metadata. Use when users want to: create B2B Commerce stores, build Commerce storefronts, set up B2B stores from Vibes, retrieve Commerce metadata, deploy Commerce experiences, work with DigitalExperienceBundle for Commerce."
-Critical: "Agents must follow the interactive flow and NEVER create storefront metadata from scratch."
 compatibility: "Requires Commerce licenses, Experience Cloud, Salesforce CLI"
 metadata:
   version: "1.0"
diff --git a/skills/developing-agentforce/SKILL.md b/skills/developing-agentforce/SKILL.md
@@ -4,7 +4,6 @@ description: "Build, modify, debug, and deploy agents with Agentforce Agent Scri
 compatibility: "Requires Agentforce license, API v66.0+, Einstein Agent User"
 metadata:
   version: "1.0"
-  last_updated: "2026-04-08"
 ---
 
 # Agent Script Skill
diff --git a/skills/generating-apex/SKILL.md b/skills/generating-apex/SKILL.md
@@ -3,6 +3,7 @@ name: generating-apex
 description: "Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill for requests involving SObject CRUD, mapping collections, fetching related records, scheduled jobs, batch jobs, trigger design, @AuraEnabled controllers, @RestResource endpoints, custom REST APIs, or code review of existing Apex."
 metadata:
   version: "1.0"
+  minApiVersion: "66.0"
 ---
 
 # Generating Apex
diff --git a/skills/generating-mermaid-diagrams/assets/datamodel/b2b-commerce-erd.md b/skills/generating-mermaid-diagrams/assets/datamodel/b2b-commerce-erd.md
@@ -22,7 +22,7 @@ Pre-built data model for Salesforce B2B Commerce using `flowchart LR` format wit
 Enrich diagram with live org data:
 
 ```bash
-python3 ~/.claude/skills/generating-mermaid-diagrams/scripts/query-org-metadata.py \
+python3 ../../scripts/query-org-metadata.py \
     --objects WebStore,WebCart,CartItem,BuyerGroup,BuyerAccount \
     --target-org myorg
 ```
diff --git a/skills/generating-mermaid-diagrams/assets/datamodel/campaigns-erd.md b/skills/generating-mermaid-diagrams/assets/datamodel/campaigns-erd.md
@@ -21,7 +21,7 @@ Pre-built data model for Salesforce Campaigns using `flowchart LR` format with c
 Enrich diagram with live org data:
 
 ```bash
-python3 ~/.claude/skills/generating-mermaid-diagrams/scripts/query-org-metadata.py \
+python3 ../../scripts/query-org-metadata.py \
     --objects Campaign,CampaignMember,CampaignInfluence,Lead,Contact,Opportunity \
     --target-org myorg
 ```
diff --git a/skills/generating-mermaid-diagrams/assets/datamodel/consent-erd.md b/skills/generating-mermaid-diagrams/assets/datamodel/consent-erd.md
@@ -24,7 +24,7 @@ Pre-built data model for Salesforce Consent Management (GDPR/Privacy) using `flo
 Enrich diagram with live org data:
 
 ```bash
-python3 ~/.claude/skills/generating-mermaid-diagrams/scripts/query-org-metadata.py \
+python3 ../../scripts/query-org-metadata.py \
     --objects Individual,ContactPointEmail,ContactPointPhone,DataUsePurpose,ContactPointConsent \
     --target-org myorg
 ```
diff --git a/skills/generating-mermaid-diagrams/assets/datamodel/files-erd.md b/skills/generating-mermaid-diagrams/assets/datamodel/files-erd.md
@@ -21,7 +21,7 @@ Pre-built data model for Salesforce Files (Content) using `flowchart LR` format
 Enrich diagram with live org data:
 
 ```bash
-python3 ~/.claude/skills/generating-mermaid-diagrams/scripts/query-org-metadata.py \
+python3 ../../scripts/query-org-metadata.py \
     --objects ContentDocument,ContentVersion,ContentDocumentLink,ContentWorkspace \
     --target-org myorg
 ```
diff --git a/skills/generating-mermaid-diagrams/assets/datamodel/forecasting-erd.md b/skills/generating-mermaid-diagrams/assets/datamodel/forecasting-erd.md
@@ -21,7 +21,7 @@ Pre-built data model for Salesforce Collaborative Forecasts using `flowchart LR`
 Enrich diagram with live org data:
 
 ```bash
-python3 ~/.claude/skills/generating-mermaid-diagrams/scripts/query-org-metadata.py \
+python3 ../../scripts/query-org-metadata.py \
     --objects ForecastingItem,ForecastingQuota,Opportunity,OpportunitySplit \
     --target-org myorg
 ```
diff --git a/skills/generating-mermaid-diagrams/assets/datamodel/fsl-erd.md b/skills/generating-mermaid-diagrams/assets/datamodel/fsl-erd.md
@@ -25,7 +25,7 @@ Pre-built data model for Salesforce Field Service (formerly Field Service Lightn
 Enrich diagram with live org data:
 
 ```bash
-python3 ~/.claude/skills/generating-mermaid-diagrams/scripts/query-org-metadata.py \
+python3 ../../scripts/query-org-metadata.py \
     --objects WorkOrder,WorkOrderLineItem,ServiceAppointment,ServiceResource,ServiceTerritory \
     --target-org myorg
 ```
diff --git a/skills/generating-mermaid-diagrams/assets/datamodel/party-model-erd.md b/skills/generating-mermaid-diagrams/assets/datamodel/party-model-erd.md
@@ -20,7 +20,7 @@ Pre-built data model for Salesforce Party Model used in Industry Clouds (Financi
 Enrich diagram with live org data:
 
 ```bash
-python3 ~/.claude/skills/generating-mermaid-diagrams/scripts/query-org-metadata.py \
+python3 ../../scripts/query-org-metadata.py \
     --objects Account,Contact,AccountContactRelation,AccountContactRole \
     --target-org myorg
 ```
diff --git a/skills/generating-mermaid-diagrams/assets/datamodel/quote-order-erd.md b/skills/generating-mermaid-diagrams/assets/datamodel/quote-order-erd.md
@@ -23,7 +23,7 @@ Pre-built data model for Salesforce Quotes and Orders using `flowchart LR` forma
 Enrich diagram with live org data:
 
 ```bash
-python3 ~/.claude/skills/generating-mermaid-diagrams/scripts/query-org-metadata.py \
+python3 ../../scripts/query-org-metadata.py \
     --objects Opportunity,Quote,QuoteLineItem,Order,OrderItem,Product2,Contract \
     --target-org myorg
 ```
diff --git a/skills/generating-mermaid-diagrams/assets/datamodel/revenue-cloud-erd.md b/skills/generating-mermaid-diagrams/assets/datamodel/revenue-cloud-erd.md
@@ -22,7 +22,7 @@ Pre-built data model for Salesforce Revenue Cloud (CPQ, Billing, Subscription Ma
 Enrich diagram with live org data:
 
 ```bash
-python3 ~/.claude/skills/generating-mermaid-diagrams/scripts/query-org-metadata.py \
+python3 ../../scripts/query-org-metadata.py \
     --objects ProductCatalog,ProductCategory,ProductSellingModel,PriceAdjustmentSchedule \
     --target-org myorg
 ```
diff --git a/skills/generating-mermaid-diagrams/assets/datamodel/sales-cloud-erd.md b/skills/generating-mermaid-diagrams/assets/datamodel/sales-cloud-erd.md
@@ -22,7 +22,7 @@ Pre-built data model for Salesforce Sales Cloud using `flowchart LR` format with
 Enrich diagram with live org data:
 
 ```bash
-python3 ~/.claude/skills/generating-mermaid-diagrams/scripts/query-org-metadata.py \
+python3 ../../scripts/query-org-metadata.py \
     --objects Account,Contact,Lead,Opportunity,Product2,Campaign \
     --target-org myorg
 ```
diff --git a/skills/generating-mermaid-diagrams/assets/datamodel/salesforce-erd.md b/skills/generating-mermaid-diagrams/assets/datamodel/salesforce-erd.md
@@ -56,7 +56,7 @@ Use `flowchart LR` (left-to-right) for data model diagrams. This format supports
 Enrich diagrams with live org data:
 
 ```bash
-python3 ~/.claude/skills/generating-mermaid-diagrams/scripts/query-org-metadata.py \
+python3 ../../scripts/query-org-metadata.py \
     --objects Account,Contact,Opportunity,Case \
     --target-org myorg
 ```
diff --git a/skills/generating-mermaid-diagrams/assets/datamodel/scheduler-erd.md b/skills/generating-mermaid-diagrams/assets/datamodel/scheduler-erd.md
@@ -23,7 +23,7 @@ Pre-built data model for Salesforce Scheduler (Lightning Scheduler) using `flowc
 Enrich diagram with live org data:
 
 ```bash
-python3 ~/.claude/skills/generating-mermaid-diagrams/scripts/query-org-metadata.py \
+python3 ../../scripts/query-org-metadata.py \
     --objects ServiceAppointment,ServiceResource,ServiceTerritory,WorkType \
     --target-org myorg
 ```
diff --git a/skills/generating-mermaid-diagrams/assets/datamodel/service-cloud-erd.md b/skills/generating-mermaid-diagrams/assets/datamodel/service-cloud-erd.md
@@ -23,7 +23,7 @@ Pre-built data model for Salesforce Service Cloud using `flowchart LR` format wi
 Enrich diagram with live org data:
 
 ```bash
-python3 ~/.claude/skills/generating-mermaid-diagrams/scripts/query-org-metadata.py \
+python3 ../../scripts/query-org-metadata.py \
     --objects Account,Contact,Case,Entitlement,ServiceContract,Asset \
     --target-org myorg
 ```
diff --git a/skills/generating-mermaid-diagrams/assets/datamodel/territory-management-erd.md b/skills/generating-mermaid-diagrams/assets/datamodel/territory-management-erd.md
@@ -20,7 +20,7 @@ Pre-built data model for Salesforce Enterprise Territory Management (Territory2)
 Enrich diagram with live org data:
 
 ```bash
-python3 ~/.claude/skills/generating-mermaid-diagrams/scripts/query-org-metadata.py \
+python3 ../../scripts/query-org-metadata.py \
     --objects Territory2Model,Territory2,Territory2Type,UserTerritory2Association,ObjectTerritory2Association \
     --target-org myorg
 ```
diff --git a/skills/generating-mermaid-diagrams/references/erd-conventions.md b/skills/generating-mermaid-diagrams/references/erd-conventions.md
@@ -210,7 +210,7 @@ style std fill:#f0f9ff,stroke:#0369a1,stroke-dasharray:5
 Use the provided Python script for efficient metadata queries:
 
 ```bash
-python3 ~/.claude/skills/generating-mermaid-diagrams/scripts/query-org-metadata.py \
+python3 ../scripts/query-org-metadata.py \
     --objects Account,Contact,Lead,Opportunity,Case \
     --target-org myorg \
     --output table
diff --git a/skills/generating-mermaid-diagrams/references/preview-guide.md b/skills/generating-mermaid-diagrams/references/preview-guide.md
@@ -14,10 +14,7 @@ After generating the diagram, offer the user a localhost preview for real-time i
 2. Start preview server (runs in background):
    ```bash
    # From installed skill folder:
-   python ~/.claude/skills/generating-mermaid-diagrams/scripts/mermaid_preview.py start --file /tmp/mermaid-preview.mmd
-
-   # Or from project folder (if working locally):
-   python [project-root]/skills/generating-mermaid-diagrams/scripts/mermaid_preview.py start --file /tmp/mermaid-preview.mmd
+   python ../scripts/mermaid_preview.py start --file /tmp/mermaid-preview.mmd
    ```
 
 3. Provide URL to user:
@@ -37,7 +34,7 @@ After generating the diagram, offer the user a localhost preview for real-time i
 
 When user is done:
 ```bash
-python ~/.claude/skills/generating-mermaid-diagrams/scripts/mermaid_preview.py stop
+python ../scripts/mermaid_preview.py stop
 ```
 
 ## Preview Server Features
diff --git a/skills/harmonizing-datacloud/SKILL.md b/skills/harmonizing-datacloud/SKILL.md
@@ -40,7 +40,7 @@ Ask for or infer:
 ## Core Operating Rules
 
 - Inspect DMO schema before creating mappings.
-- Run the shared readiness classifier before mutating harmonization assets: `node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase harmonize --json`.
+- Run the shared readiness classifier before mutating harmonization assets: `node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase harmonize --json`.
 - Prefer `dmo list --all` when browsing the catalog, but use first-page `dmo list` for fast readiness checks.
 - Use `query describe` or `dmo get --json` instead of inventing unsupported describe flows.
 - Treat identity resolution runs as asynchronous and verify results after execution.
@@ -52,7 +52,7 @@ Ask for or infer:
 
 ### 1. Classify readiness for harmonize work
 ```bash
-node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase harmonize --json
+node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase harmonize --json
 ```
 
 ### 2. Inspect the catalog
diff --git a/skills/implementing-ui-bundle-agentforce-conversation-client/SKILL.md b/skills/implementing-ui-bundle-agentforce-conversation-client/SKILL.md
@@ -1,8 +1,7 @@
 ---
 name: implementing-ui-bundle-agentforce-conversation-client
-description: "Use this skill when the user asks to add, embed, integrate, configure, style, or remove an agent, chatbot, chat widget, conversation client, or AI assistant in a UI Bundle project. Covers styling (colors, fonts, spacing, borders), layout (inline vs floating, width, height, dimensions), and props (agentId, agentLabel, headerEnabled, showHeaderIcon, showAvatar, styleTokens). TRIGGER when: project contains a uiBundles/*/src/ directory and the task involves adding or modifying a chat widget, chatbot, or conversational AI; files under uiBundles/*/src/ import AgentforceConversationClient; user asks to add any chat or agent functionality to a page. DO NOT TRIGGER when: user wants to create a custom agent, chatbot, or chat widget component from scratch; the project has no uiBundles directory."
+description: "Use this skill when the user asks to add, embed, integrate, configure, style, or remove an agent, chatbot, chat widget, conversation client, or AI assistant in a UI Bundle project. TRIGGER when: project contains a uiBundles/*/src/ directory and the task involves adding or modifying a chat widget, chatbot, or conversational AI; files under uiBundles/*/src/ import AgentforceConversationClient; user asks to add any chat or agent functionality to a page. DO NOT TRIGGER when: user wants to create a custom agent, chatbot, or chat widget component from scratch; the project has no uiBundles directory."
 metadata:
-  author: ACC Components
   version: "1.1"
   package: "@salesforce/ui-bundle-template-feature-react-agentforce-conversation-client"
   sdk-package: "@salesforce/agentforce-conversation-client"
diff --git a/skills/investigating-agentforce-d360/SKILL.md b/skills/investigating-agentforce-d360/SKILL.md
@@ -1,6 +1,6 @@
 ---
 name: investigating-agentforce-d360
-description: "Data Cloud 360° view of a single Agentforce session. Pulls 24 STDM + GenAI DMO rows via the DC Query REST API, assembles a hierarchical session tree (Interaction → Step → Generation → GatewayRequest), renders a human-readable summary with transcript + per-turn topic/action invocations + LLM generations + tool calls + audit chain. TRIGGER when user asks to trace, inspect, summarize, or describe a specific Agentforce session by session id (Agent Session UUID `019d…` or MessagingSession id `0Mw…`). Also triggers on session discovery — find/list/search sessions by time, agent, channel, outcome, or conversation text — when the user has no session id yet. DO NOT TRIGGER for design-time architecture questions (use investigating-agentforce-architecture instead) or for runtime perf/latency/SLO questions that require platform telemetry beyond Data Cloud."
+description: "Data Cloud 360° view of a single Agentforce session. TRIGGER when user asks to trace, inspect, summarize, or describe a specific Agentforce session by session id (Agent Session UUID `019d…` or MessagingSession id `0Mw…`). Also triggers on session discovery — find/list/search sessions by time, agent, channel, outcome, or conversation text — when the user has no session id yet. DO NOT TRIGGER for design-time architecture questions (use investigating-agentforce-architecture instead) or for runtime perf/latency/SLO questions that require platform telemetry beyond Data Cloud."
 metadata:
   version: "1.0"
 ---
diff --git a/skills/observing-agentforce/SKILL.md b/skills/observing-agentforce/SKILL.md
@@ -4,7 +4,6 @@ description: "Analyze production Agentforce agent behavior using session traces
 allowed-tools: Bash Read Write Edit Glob Grep
 metadata:
   version: "1.0"
-  last_updated: "2026-04-08"
   argument-hint: "<org-alias> [--agent-file <path>] [--session-id <id>] [--days <n>]"
   compatibility: claude-code
 ---
diff --git a/skills/observing-agentforce/references/stdm-queries.md b/skills/observing-agentforce/references/stdm-queries.md
@@ -23,18 +23,10 @@ Methods:
 # Ensure the classes directory exists
 mkdir -p <project-root>/force-app/main/default/classes
 
-# Copy from the installed skill location
-cp skills/observing-agentforce/apex/AgentforceOptimizeService.cls \
+# Copy from the skill's apex directory
+cp ../apex/AgentforceOptimizeService.cls \
    <project-root>/force-app/main/default/classes/
-cp skills/observing-agentforce/apex/AgentforceOptimizeService.cls-meta.xml \
-   <project-root>/force-app/main/default/classes/
-```
-
-If the skill is installed globally via the installer, use the installed path:
-```bash
-cp ~/.claude/skills/observing-agentforce/apex/AgentforceOptimizeService.cls \
-   <project-root>/force-app/main/default/classes/
-cp ~/.claude/skills/observing-agentforce/apex/AgentforceOptimizeService.cls-meta.xml \
+cp ../apex/AgentforceOptimizeService.cls-meta.xml \
    <project-root>/force-app/main/default/classes/
 ```
 
diff --git a/skills/orchestrating-datacloud/README.md b/skills/orchestrating-datacloud/README.md
diff --git a/skills/orchestrating-datacloud/SKILL.md b/skills/orchestrating-datacloud/SKILL.md
diff --git a/skills/orchestrating-datacloud/references/feature-readiness.md b/skills/orchestrating-datacloud/references/feature-readiness.md
diff --git a/skills/orchestrating-datacloud/references/plugin-setup.md b/skills/orchestrating-datacloud/references/plugin-setup.md
diff --git a/skills/orchestrating-datacloud/scripts/diagnose-org.mjs b/skills/orchestrating-datacloud/scripts/diagnose-org.mjs
diff --git a/skills/orchestrating-datacloud/scripts/verify-plugin.sh b/skills/orchestrating-datacloud/scripts/verify-plugin.sh
diff --git a/skills/preparing-datacloud/SKILL.md b/skills/preparing-datacloud/SKILL.md
diff --git a/skills/retrieving-datacloud/SKILL.md b/skills/retrieving-datacloud/SKILL.md
diff --git a/skills/reviewing-lwc-mobile-offline/SKILL.md b/skills/reviewing-lwc-mobile-offline/SKILL.md
diff --git a/skills/testing-agentforce/SKILL.md b/skills/testing-agentforce/SKILL.md
diff --git a/skills/using-mobile-native-capabilities/SKILL.md b/skills/using-mobile-native-capabilities/SKILL.md
