@salesforce/afv-skills 1.15.0 → 1.17.0

package/package.json

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

package/skills/activating-datacloud/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: activating-datacloud
 description: "Salesforce Data Cloud Act phase. Use this skill when the user manages activations, activation targets, data actions, or downstream delivery of Data Cloud audiences and data. TRIGGER when: user manages activations, activation targets, data actions, or downstream delivery of Data Cloud audiences and data. DO NOT TRIGGER when: the task is segment creation (use segmenting-datacloud), data retrieval/search work (use retrieving-datacloud), or STDM/session tracing (use observing-agentforce)."
-license: MIT
 compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
   version: "1.0"
@@ -41,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.
@@ -53,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

package/skills/analyzing-omnistudio-dependencies/SKILL.md

@@ -1,7 +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)."
-license: MIT
+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"
 ---

package/skills/building-mobile-apps/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: building-mobile-apps
 description: "The entry point for building any Salesforce native mobile app on iOS or Android. TRIGGER when the user says: \"build a Salesforce iOS app\", \"add Salesforce login to my Android app\", \"set up Mobile SDK\", \"add MobileSync / SmartStore offline storage\", \"embed an Agentforce agent in my mobile app\", \"add Agentforce chat to iOS/Android\", or otherwise asks to create, extend, or integrate a Salesforce mobile experience in Swift or Kotlin (MSDK, Agentforce SDK, or both). SKIP when the user is building a non-Salesforce mobile app, using React Native / Flutter / Ionic without Salesforce integration, asking about generic mobile UI design, or working on a Salesforce-adjacent web/desktop surface (LWC, Experience Cloud, Mobile Publisher branding-only)."
-license: Apache-2.0
 metadata:
   version: "1.0"
 ---

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

@@ -1,7 +1,6 @@
 ---
 name: building-omnistudio-callable-apex
 description: "Salesforce Industries Common Core (OmniStudio/Vlocity) Apex callable generation and review skill with 120-point scoring. Use when creating, reviewing, or migrating Industries callable Apex implementations. TRIGGER when: user creates or reviews System.Callable classes, migrates VlocityOpenInterface or VlocityOpenInterface2, or builds Industries callable extensions used by OmniStudio, Integration Procedures, or DataRaptors. DO NOT TRIGGER when: generic Apex classes or triggers (use generating-apex), building Integration Procedures (use building-omnistudio-integration-procedure), authoring OmniScripts (use building-omnistudio-omniscript), configuring Data Mappers (use building-omnistudio-datamapper), or analyzing namespace/dependency issues (use analyzing-omnistudio-dependencies)."
-license: MIT
 metadata:
   version: "1.0"
 ---

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

@@ -1,7 +1,6 @@
 ---
 name: building-omnistudio-datamapper
 description: "OmniStudio Data Mapper (formerly DataRaptor) creation and validation with 100-point scoring. Use when building Extract, Transform, Load, or Turbo Extract Data Mappers, mapping Salesforce object fields, or reviewing existing Data Mapper configurations. TRIGGER when: user creates Data Mappers, configures field mappings, works with OmniDataTransform metadata, or asks about DataRaptor/Data Mapper patterns. DO NOT TRIGGER when: building Integration Procedures (use building-omnistudio-integration-procedure), authoring OmniScripts (use building-omnistudio-omniscript), or analyzing cross-component dependencies (use analyzing-omnistudio-dependencies)."
-license: MIT
 metadata:
   version: "1.0"
 ---

package/skills/building-omnistudio-flexcard/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: building-omnistudio-flexcard
 description: "OmniStudio FlexCard creation and validation with 130-point scoring. Use when building at-a-glance UI cards, configuring data source bindings to Integration Procedures, or reviewing existing FlexCard definitions for accessibility and performance. TRIGGER when: user creates FlexCards, configures data sources, designs card layouts, or asks about OmniUiCard metadata. DO NOT TRIGGER when: building OmniScripts (use building-omnistudio-omniscript), creating Integration Procedures (use building-omnistudio-integration-procedure), or analyzing dependencies (use analyzing-omnistudio-dependencies)."
-license: MIT
 metadata:
   version: "1.0"
 ---

package/skills/building-omnistudio-integration-procedure/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: building-omnistudio-integration-procedure
 description: "OmniStudio Integration Procedure creation and validation with 110-point scoring. Use this skill when building server-side process orchestrations that combine Data Mapper actions, Apex Remote Actions, HTTP callouts, and conditional logic. TRIGGER when: user creates Integration Procedures, adds Data Mapper steps, configures Remote Actions, or reviews existing IP configurations. DO NOT TRIGGER when: building OmniScripts (use building-omnistudio-omniscript), creating Data Mappers directly (use building-omnistudio-datamapper), or analyzing cross-component dependencies (use analyzing-omnistudio-dependencies)."
-license: MIT
 metadata:
   version: "1.0"
 ---

package/skills/building-omnistudio-omniscript/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: building-omnistudio-omniscript
 description: "OmniStudio OmniScript creation and validation with 120-point scoring. Use when building guided digital experiences, multi-step forms, or interactive processes that orchestrate Integration Procedures and Data Mappers. TRIGGER when: user creates OmniScripts, designs step flows, configures element types, or reviews existing OmniScript configurations. DO NOT TRIGGER when: building FlexCards (use building-omnistudio-flexcard), creating Integration Procedures directly (use building-omnistudio-integration-procedure), or analyzing dependencies (use analyzing-omnistudio-dependencies)."
-license: MIT
 metadata:
   version: "1.0"
 ---

package/skills/building-sf-integrations/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: building-sf-integrations
 description: "Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data)."
-license: MIT
 metadata:
   version: "1.1"
 ---

package/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

package/skills/configuring-connected-apps/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: configuring-connected-apps
 description: "Salesforce Connected Apps and External Client Apps OAuth configuration with 120-point scoring. Use this skill to configure OAuth flows, JWT bearer auth, Connected Apps, and External Client Apps in Salesforce. TRIGGER when: user configures OAuth flows, JWT bearer auth, Connected Apps, ECAs, or touches .connectedApp-meta.xml / .eca-meta.xml files. DO NOT TRIGGER when: configuring Named Credentials for callouts (use building-sf-integrations), reviewing permission policies (use deploying-metadata), or writing Apex token-handling code (use generating-apex)."
-license: MIT
 allowed-tools: Bash Read Write Edit Glob Grep WebFetch AskUserQuestion TodoWrite
 metadata:
   version: "1.1"

package/skills/connecting-datacloud/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: connecting-datacloud
 description: "Salesforce Data Cloud Connect phase. Use this skill when the user manages Data Cloud connections, connectors, or sets up a new source system. TRIGGER when: user manages Data Cloud connections, connectors, connector metadata, tests a connection, browses source objects or databases, or sets up a new source system. DO NOT TRIGGER when: the task is about data streams or DLOs (use preparing-datacloud), DMOs or identity resolution (use harmonizing-datacloud), retrieval/search (use retrieving-datacloud), or STDM telemetry (use observing-agentforce)."
-license: MIT
 compatibility: "Requires the sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
   version: "1.0"
@@ -44,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`.
@@ -60,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

package/skills/creating-b2b-commerce-store/SKILL.md

@@ -1,8 +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."
-license: Apache-2.0
 compatibility: "Requires Commerce licenses, Experience Cloud, Salesforce CLI"
 metadata:
   version: "1.0"

package/skills/debugging-apex-logs/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: debugging-apex-logs
 description: "Salesforce debug log analysis and troubleshooting with 100-point scoring. TRIGGER when: user analyzes debug logs, hits governor limits, reads stack traces, or touches .log files from Salesforce orgs. DO NOT TRIGGER when: running Apex tests (use running-apex-tests), generating or fixing Apex code (use generating-apex), or Agentforce session tracing (use observing-agentforce)."
-license: MIT
 metadata:
   version: "1.1"
 ---

package/skills/deploying-metadata/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: deploying-metadata
 description: "Salesforce DevOps automation using sf CLI v2. TRIGGER when: user deploys metadata, creates/manages scratch orgs or sandboxes, sets up CI/CD pipelines, or troubleshoots deployment errors with sf project deploy. DO NOT TRIGGER when: writing Apex code (use generating-apex), building LWC components (use generating-lwc-components), creating metadata definitions (use generating-custom-object or generating-custom-field), or querying org data (use handling-sf-data)."
-license: MIT
 metadata:
   version: "1.1"
 ---

package/skills/deploying-omnistudio-datapacks/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: deploying-omnistudio-datapacks
 description: "Salesforce Industries DataPack deployment automation using Vlocity Build. TRIGGER when: user deploys or validates OmniStudio/Vlocity DataPacks with vlocity commands (packDeploy/packRetry/packExport/packGetDiffs), sets up DataPack CI/CD pipelines, or troubleshoots DataPack migration errors. DO NOT TRIGGER when: deploying Salesforce metadata with sf project deploy (use deploying-metadata), authoring OmniStudio artifacts (use building-omnistudio-*), or writing Apex/LWC business logic (use generating-apex/generating-lwc-components)."
-license: MIT
 metadata:
   version: "1.0"
 ---

package/skills/developing-agentforce/SKILL.md

@@ -1,11 +1,9 @@
 ---
 name: developing-agentforce
 description: "Build, modify, debug, and deploy agents with Agentforce Agent Script. TRIGGER when: user creates, modifies, or asks about .agent files or aiAuthoringBundle metadata; changes agent behavior, responses, or conversation logic; designs agent actions, tools, subagents, or flow control; writes or reviews an Agent Spec; previews, debugs, deploys, publishes, or tests agents; uses Agent Script CLI commands (sf agent generate/preview/publish/test). DO NOT TRIGGER when: Apex development, Flow building, Prompt Template authoring, Experience Cloud configuration, or general Salesforce CLI tasks unrelated to Agent Script."
-license: Apache-2.0
 compatibility: "Requires Agentforce license, API v66.0+, Einstein Agent User"
 metadata:
   version: "1.0"
-  last_updated: "2026-04-08"
 ---
 
 # Agent Script Skill

package/skills/fetching-salesforce-docs/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: fetching-salesforce-docs
 description: "Official Salesforce documentation retrieval skill. Use when you need authoritative Salesforce docs from developer.salesforce.com, help.salesforce.com, architect.salesforce.com, admin.salesforce.com, or lightningdesignsystem.com, especially when pages are JS-heavy, shell-rendered, or hard to extract with naive fetching. Use to ground answers in official Salesforce sources instead of third-party blogs or summaries. TRIGGER when: user asks for official Salesforce documentation, Apex or API reference, LWC docs, Agentforce docs, setup or help articles, or any doc from a Salesforce-owned domain. DO NOT TRIGGER when: user is asking for a code change, deployment task, or anything not requiring documentation retrieval — use the appropriate sf-* skill instead."
-license: MIT
 metadata:
   version: "1.1"
 ---

package/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

package/skills/generating-lwc-components/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: generating-lwc-components
 description: "Lightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce."
-license: MIT
 metadata:
   version: "1.1"
 ---

package/skills/generating-mermaid-diagrams/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: generating-mermaid-diagrams
 description: "Salesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says \"diagram\", \"visualize\", \"ERD\", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG/SVG image output (use generating-visual-diagrams), or asks about non-Salesforce systems."
-license: MIT
 compatibility: "Requires Mermaid-capable renderer for diagram previews"
 metadata:
   version: "1.0"

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

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

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

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

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

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

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

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

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

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

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

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

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

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

package/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

package/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

package/skills/generating-visual-diagrams/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: generating-visual-diagrams
 description: "AI-powered image generation for Salesforce visuals via Nano Banana Pro. Use this skill when the user needs rendered PNG/SVG output such as visual ERDs (Entity Relationship Diagrams), UI mockups, wireframes, or architecture illustrations. TRIGGER when: user asks for PNG/SVG output, UI mockups, wireframes, visual ERDs, or says \"generate image\" / \"create mockup\". DO NOT TRIGGER when: text-based Mermaid diagrams (use generating-mermaid-diagrams), or non-visual documentation tasks."
-license: MIT
 metadata:
   version: "1.0"
 ---

package/skills/handling-sf-data/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: handling-sf-data
 description: "Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata)."
-license: MIT
 metadata:
   version: "1.1"
 ---

package/skills/harmonizing-datacloud/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: harmonizing-datacloud
 description: "Salesforce Data Cloud Harmonize phase. Use this skill when the user works with DMOs, mappings, relationships, identity resolution, unified profiles, data graphs, or universal IDs. TRIGGER when: user works with DMOs, mappings, relationships, identity resolution, unified profiles, data graphs, or universal IDs. DO NOT TRIGGER when: the task is only about streams/DLOs (use preparing-datacloud), segments/insights (use segmenting-datacloud), retrieval/search (use retrieving-datacloud), or STDM/session tracing (use observing-agentforce)."
-license: MIT
 compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
   version: "1.0"
@@ -41,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.
@@ -53,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

package/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"

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

@@ -1,7 +1,6 @@
 ---
 name: integrating-b2b-commerce-open-code-components
 description: "Integrate Salesforce B2B Commerce open source components from GitHub into B2B Commerce stores. Use when users mention \"integrate open code components\", \"open source B2B commerce\", \"add open code components\", \"forcedotcom/b2b-commerce-open-source-components\", or want to add open source commerce components to their store. Copies all components and labels so they become available in Experience Builder."
-license: LICENSE.txt has complete terms
 allowed-tools: Bash(git clone:*) Bash(cp:*) Read
 metadata:
   version: "1.0"

package/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"
 ---

package/skills/modeling-omnistudio-epc-catalog/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: modeling-omnistudio-epc-catalog
 description: "Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata)."
-license: MIT
 metadata:
   version: "1.0"
 ---

package/skills/observing-agentforce/SKILL.md

@@ -2,10 +2,8 @@
 name: observing-agentforce
 description: "Analyze production Agentforce agent behavior using session traces and Data Cloud. TRIGGER when: user queries STDM session data or Data Cloud trace records; investigates production agent failures, regressions, or performance issues; asks about session traces, conversation logs, or agent metrics; wants to reproduce a reported production issue in preview; runs findSessions or trace analysis queries. DO NOT TRIGGER when: user creates, modifies, or debugs .agent files during development (use developing-agentforce); writes or runs test specs (use testing-agentforce); uses sf agent preview for local development iteration; deploys or publishes agents."
 allowed-tools: Bash Read Write Edit Glob Grep
-license: Apache-2.0
 metadata:
   version: "1.0"
-  last_updated: "2026-04-08"
   argument-hint: "<org-alias> [--agent-file <path>] [--session-id <id>] [--days <n>]"
   compatibility: claude-code
 ---

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

package/skills/orchestrating-datacloud/README.md

@@ -63,14 +63,12 @@ These are intentionally generic and should be adapted to the target org.
 
 ## Quick start
 
-> The script examples below assume the skill is installed under `~/.claude/skills/` via the full Claude Code installer. If you are working from a repo checkout, run the same scripts from that checkout path.
-
 ### 1. Verify the runtime
 
 ```bash
-bash ~/.claude/skills/orchestrating-datacloud/scripts/verify-plugin.sh
+bash ./scripts/verify-plugin.sh
 # or with an org alias
-bash ~/.claude/skills/orchestrating-datacloud/scripts/verify-plugin.sh myorg
+bash ./scripts/verify-plugin.sh myorg
 ```
 
 The helper treats `sf data360 doctor` as advisory and falls back to additional read-only smoke checks when an org is only partially provisioned.
@@ -78,9 +76,9 @@ The helper treats `sf data360 doctor` as advisory and falls back to additional r
 ### 2. Diagnose feature readiness before mutating
 
 ```bash
-node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o myorg --json
+node ./scripts/diagnose-org.mjs -o myorg --json
 # optional retrieve-plane probe, only when you know the table is real
-node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o myorg --phase retrieve --describe-table MyDMO__dlm --json
+node ./scripts/diagnose-org.mjs -o myorg --phase retrieve --describe-table MyDMO__dlm --json
 ```
 
 Use the diagnose helper to distinguish between:
@@ -94,7 +92,7 @@ Use the diagnose helper to distinguish between:
 ```bash
 python3 ~/.claude/sf-skills-install.py --with-datacloud-runtime
 # or run the helper script directly
-bash ~/.claude/skills/orchestrating-datacloud/scripts/bootstrap-plugin.sh
+bash ./scripts/bootstrap-plugin.sh
 ```
 
 ### 4. Start with read-only inspection

package/skills/orchestrating-datacloud/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: orchestrating-datacloud
 description: "Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex)."
-license: MIT
 compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
   version: "1.0"
@@ -93,7 +92,7 @@ Recommended checks:
 ```bash
 sf data360 man
 sf org display -o <alias>
-bash ~/.claude/skills/orchestrating-datacloud/scripts/verify-plugin.sh <alias>
+bash ./scripts/verify-plugin.sh <alias>
 ```
 
 Treat `sf data360 doctor` as a broad health signal, not the sole gate. On partially provisioned orgs it can fail even when read-only command families like connectors, DMOs, or segments still work.
@@ -101,12 +100,12 @@ Treat `sf data360 doctor` as a broad health signal, not the sole gate. On partia
 ### 2. Classify readiness before changing anything
 Run the shared classifier first:
 ```bash
-node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --json
+node ./scripts/diagnose-org.mjs -o <org> --json
 ```
 
 Only use a query-plane probe after you know the table name is real:
 ```bash
-node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase retrieve --describe-table MyDMO__dlm --json
+node ./scripts/diagnose-org.mjs -o <org> --phase retrieve --describe-table MyDMO__dlm --json
 ```
 
 Use the classifier to distinguish:

package/skills/orchestrating-datacloud/references/feature-readiness.md

@@ -27,13 +27,13 @@ Examples:
 Run the shared readiness classifier before mutation-heavy work:
 
 ```bash
-node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o myorg --json
+node ../scripts/diagnose-org.mjs -o myorg --json
 ```
 
 For retrieve/query work, only add a table probe when you already know the table name is real:
 
 ```bash
-node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o myorg --phase retrieve --describe-table MyDMO__dlm --json
+node ../scripts/diagnose-org.mjs -o myorg --phase retrieve --describe-table MyDMO__dlm --json
 ```
 
 ## Signal matrix

package/skills/orchestrating-datacloud/references/plugin-setup.md

@@ -18,8 +18,6 @@ The orchestrating-datacloud family uses a **community `sf data360` CLI runtime**
 
 ## Recommended setup path
 
-The command examples below assume the skill is installed under `~/.claude/skills/` via the full Claude Code installer. If you are working from a cloned sf-skills repo instead, run the same scripts from that checkout path.
-
 If you use the Python installer, it can install this optional runtime for you:
 
 ```bash
@@ -29,7 +27,7 @@ python3 ~/.claude/sf-skills-install.py --with-datacloud-runtime
 Or use the helper script directly:
 
 ```bash
-bash ~/.claude/skills/orchestrating-datacloud/scripts/bootstrap-plugin.sh
+bash ../scripts/bootstrap-plugin.sh
 ```
 
 By default it clones the plugin into `~/.sf-community-tools/datacloud/sf-cli-plugin-data360`, installs dependencies, compiles it, and links it into the local Salesforce CLI.
@@ -41,7 +39,7 @@ git clone https://github.com/Jaganpro/sf-cli-plugin-data360.git
 cd sf-cli-plugin-data360
 yarn install
 npx tsc
-node ~/.claude/skills/orchestrating-datacloud/scripts/generate-manifest.mjs .
+node ../scripts/generate-manifest.mjs .
 sf plugins link .
 ```
 
@@ -49,9 +47,9 @@ sf plugins link .
 
 ```bash
 sf data360 man
-bash ~/.claude/skills/orchestrating-datacloud/scripts/verify-plugin.sh
-bash ~/.claude/skills/orchestrating-datacloud/scripts/verify-plugin.sh myorg
-node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o myorg --json
+bash ../scripts/verify-plugin.sh
+bash ../scripts/verify-plugin.sh myorg
+node ../scripts/diagnose-org.mjs -o myorg --json
 ```
 
 For newer command families such as `sf data360 query hybrid` and recent pagination fixes, update the community runtime to the latest upstream commit by re-running the bootstrap helper.
@@ -80,7 +78,7 @@ sf data360 segment list -o myorg 2>/dev/null
 If you see `Warning: @gthoppae/sf-cli-plugin-data360 is a linked ESM module and cannot be auto-transpiled`, generate the oclif command manifest:
 
 ```bash
-node ~/.claude/skills/orchestrating-datacloud/scripts/generate-manifest.mjs ~/.sf-community-tools/datacloud/sf-cli-plugin-data360
+node ../scripts/generate-manifest.mjs ~/.sf-community-tools/datacloud/sf-cli-plugin-data360
 ```
 
 This tells oclif to use pre-compiled output directly instead of attempting auto-transpilation. The `npx oclif manifest` alternative may fail on newer Node.js versions due to `@oclif/core` version mismatches.

package/skills/orchestrating-datacloud/scripts/diagnose-org.mjs

@@ -257,7 +257,7 @@ function guidanceFromProbe(scope, probe) {
   if (probe.state === 'runtime_missing') {
     return [
       'Install or relink the community sf data360 runtime before attempting Data Cloud work.',
-      'Use python3 ~/.claude/sf-skills-install.py --with-datacloud-runtime or bash ~/.claude/skills/orchestrating-datacloud/scripts/bootstrap-plugin.sh.',
+      'Use python3 ~/.claude/sf-skills-install.py --with-datacloud-runtime or bash ./scripts/bootstrap-plugin.sh.',
     ];
   }
 

package/skills/orchestrating-datacloud/scripts/verify-plugin.sh

@@ -10,7 +10,7 @@ fi
 
 if ! sf data360 man >/dev/null 2>&1; then
   echo "The community 'sf data360' runtime is not available." >&2
-  echo "Run bash ~/.claude/skills/orchestrating-datacloud/scripts/bootstrap-plugin.sh first." >&2
+  echo "Run bash ./scripts/bootstrap-plugin.sh first." >&2
   exit 1
 fi
 
@@ -54,5 +54,5 @@ fi
 
 echo "Verification complete."
 if [[ -n "${ORG}" ]]; then
-  echo "Next: node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o '${ORG}' --json"
+  echo "Next: node ./scripts/diagnose-org.mjs -o '${ORG}' --json"
 fi

package/skills/preparing-datacloud/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: preparing-datacloud
 description: "Salesforce Data Cloud Prepare phase. Use this skill when the user creates or manages Data Cloud data streams, DLOs, transforms, or Document AI configurations. TRIGGER when: user creates or manages Data Cloud data streams, DLOs, transforms, or Document AI configurations, or asks about ingestion into Data Cloud. DO NOT TRIGGER when: the task is connection setup only (use connecting-datacloud), DMOs and identity resolution (use harmonizing-datacloud), or query/search work (use retrieving-datacloud)."
-license: MIT
 compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
   version: "1.0"
@@ -45,7 +44,7 @@ Ask for or infer:
 ## Core Operating Rules
 
 - Verify the external plugin runtime before running Data Cloud commands.
-- Run the shared readiness classifier before mutating ingestion assets: `node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase prepare --json`.
+- Run the shared readiness classifier before mutating ingestion assets: `node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase prepare --json`.
 - Prefer inspecting existing streams and DLOs before creating new ingestion assets.
 - Suppress linked-plugin warning noise with `2>/dev/null` for normal usage.
 - Treat DLO naming and field naming as Data Cloud-specific, not CRM-native.
@@ -60,7 +59,7 @@ Ask for or infer:
 
 ### 1. Classify readiness for prepare work
 ```bash
-node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase prepare --json
+node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase prepare --json
 ```
 
 ### 2. Inspect existing ingestion assets

package/skills/querying-soql/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: querying-soql
 description: "SOQL query generation, optimization, and analysis with 100-point scoring. Use this skill when the user needs SOQL/SOSL authoring or optimization: natural-language-to-query generation, relationship queries, aggregates, query-plan analysis, and performance or safety improvements for Salesforce queries. TRIGGER when: user writes, optimizes, or debugs SOQL/SOSL queries, touches .soql files, or asks about relationship queries, aggregates, or query performance. DO NOT TRIGGER when: bulk data operations (use handling-sf-data), Apex DML logic (use generating-apex), or report/dashboard queries."
-license: MIT
 metadata:
   version: "1.1"
 ---

package/skills/retrieving-datacloud/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: retrieving-datacloud
 description: "Salesforce Data Cloud Retrieve phase. Use this skill when the user runs Data Cloud SQL, async queries, vector search, search-index workflows, or metadata introspection for Data Cloud objects. TRIGGER when: user runs Data Cloud SQL, describe, async queries, vector search, search-index workflows, or metadata introspection for Data Cloud objects. DO NOT TRIGGER when: the task is standard CRM SOQL (use querying-soql), segment creation or calculated insight design (use segmenting-datacloud), or STDM/session tracing/parquet analysis (use observing-agentforce)."
-license: MIT
 compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
   version: "1.0"
@@ -40,7 +39,7 @@ Ask for or infer:
 ## Core Operating Rules
 
 - Treat Data Cloud SQL as its own query language, not SOQL.
-- Run the shared readiness classifier before relying on query/search surfaces: `node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase retrieve --json`.
+- Run the shared readiness classifier before relying on query/search surfaces: `node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase retrieve --json`.
 - Use describe before guessing columns.
 - Prefer `sqlv2` or async query flows for larger result sets.
 - Use vector search or hybrid search only when the search index lifecycle is healthy.
@@ -52,9 +51,9 @@ Ask for or infer:
 
 ### 1. Classify readiness for retrieve work
 ```bash
-node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase retrieve --json
+node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase retrieve --json
 # optional query-plane probe, only with a real table name
-node ~/.claude/skills/orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase retrieve --describe-table MyDMO__dlm --json
+node ../orchestrating-datacloud/scripts/diagnose-org.mjs -o <org> --phase retrieve --describe-table MyDMO__dlm --json
 ```
 
 ### 2. Choose the smallest correct query shape

package/skills/reviewing-lwc-mobile-offline/SKILL.md

@@ -4,7 +4,6 @@ description: "Review a Lightning Web Component for **mobile offline** compatibil
 metadata:
   version: "1.0"
 ---
-<!-- adk-managed-skill -->
 
 # Reviewing LWC Mobile Offline
 

package/skills/running-apex-tests/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: running-apex-tests
 description: "Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. Use when the user needs to run Apex tests, check code coverage, fix failing tests, or work with *Test.cls / *_Test.cls files. TRIGGER when: user runs Apex tests, checks code coverage, fixes failing tests, or touches *Test.cls / *_Test.cls files. DO NOT TRIGGER when: writing Apex production code (use generating-apex), Agentforce agent testing (use testing-agentforce), or Jest/LWC tests (use generating-lwc-components)."
-license: MIT
 metadata:
   version: "1.1"
 ---

package/skills/running-code-analyzer/SKILL.md

@@ -2,7 +2,6 @@
 name: running-code-analyzer
 description: "Run Salesforce Code Analyzer to scan code for security, performance, best practice, and code style violations. Supports all engines (PMD, ESLint, CPD, RetireJS, Flow, SFGE, ApexGuru), targets (files, folders, git diff), categories, and severities. TRIGGER when: user says 'scan my code', 'check for security issues', 'run PMD/ESLint', 'find duplicates', 'analyze Flows', 'check vulnerable libraries', 'AppExchange review', 'lint my LWC', 'static analysis', 'code quality', or mentions engines/file types (.cls, .trigger, .js, .flow-meta.xml). DO NOT TRIGGER when: user wants to fix code without scanning, or asks about installation/configuration."
 allowed-tools: Read, Bash(sf code-analyzer), Bash(node), Bash(git diff), Bash(date), Write, Edit
-license: LICENSE.txt has complete terms
 metadata:
   version: "1.0"
   argument-hint: "[target-path] [--engine pmd|eslint|cpd|retire-js|regex|flow|sfge|apexguru] [--category Security|Performance|BestPractices|...] [--severity 1-5] [--diff]"

package/skills/segmenting-datacloud/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: segmenting-datacloud
 description: "Salesforce Data Cloud Segment phase. Use this skill when the user creates or publishes segments, manages calculated insights, or troubleshoots audience SQL in Data Cloud. TRIGGER when: user creates or publishes segments, manages calculated insights, inspects segment counts or membership, or troubleshoots audience SQL in Data Cloud. DO NOT TRIGGER when: the task is DMO/mapping/identity-resolution work (use harmonizing-datacloud), activation work (use activating-datacloud), query/search-index work (use retrieving-datacloud), or Standard Data Model (STDM)/session tracing (use observing-agentforce)."
-license: MIT
 compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
   version: "1.0"

package/skills/testing-agentforce/SKILL.md

@@ -2,10 +2,8 @@
 name: testing-agentforce
 description: "Write, run, and analyze structured test suites for Agentforce agents. TRIGGER when: user writes or modifies test spec YAML (AiEvaluationDefinition); runs sf agent test create, run, run-eval, or results commands; asks about test coverage strategy, metric selection, or custom evaluations; interprets test results or diagnoses test failures; asks about batch testing, regression suites, or CI/CD test integration. DO NOT TRIGGER when: user creates, modifies, previews, or debugs .agent files (use developing-agentforce); deploys or publishes agents; writes Agent Script code; uses sf agent preview for development iteration; analyzes production session traces (use observing-agentforce)."
 allowed-tools: Bash Read Write Edit Glob Grep
-license: Apache-2.0
 metadata:
   version: "1.0"
-  last_updated: "2026-04-08"
   argument-hint: "<org-alias> --authoring-bundle <AgentName> [--utterances <file>] | run <org> --target <flow://Name>"
   compatibility: claude-code
 ---

package/skills/using-mobile-native-capabilities/SKILL.md

@@ -4,7 +4,6 @@ description: "Build a Salesforce LWC that uses native mobile device capabilities
 metadata:
   version: "1.0"
 ---
-<!-- adk-managed-skill -->
 
 # Using Mobile Native Capabilities