@salesforce/afv-skills 1.21.0 → 1.22.0

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

@@ -0,0 +1,165 @@
+---
+name: commerce-b2b-open-code-components-integrate
+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."
+allowed-tools: Bash(git clone:*) Bash(cp:*) Read
+metadata:
+  version: "1.0"
+---
+
+## When to Use This Skill
+
+Use this skill when you need to:
+- Integrate all open source B2B Commerce components into a store
+- Add open source components to a new or existing B2B Commerce store
+- Make open code components available in Experience Builder
+
+## Rules
+
+1. **Always explain before executing.** Before running any command, you MUST tell the user what the command does and why you are running it. Never just show a raw command and ask for permission. The user should be able to read your explanation and understand the purpose before approving.
+
+## Overview
+
+This skill copies all open source B2B Commerce components from the official Salesforce repository (https://github.com/forcedotcom/b2b-commerce-open-source-components) into a B2B Commerce store's site metadata. After integration, the components appear in the Experience Builder component palette.
+
+---
+
+## Startup Flow
+
+When this skill is triggered, perform these checks automatically before copying.
+
+### Check 0: Resolve Package Directory
+
+Read `sfdx-project.json` and pick the active package directory. Extract `packageDirectories[]` and use the entry with `"default": true`; if no entry is flagged default, use the first entry. Use this value as `<package-dir>` everywhere below. If `sfdx-project.json` is missing or has no `packageDirectories`, tell the user and abort.
+
+### Check 1: Open Source Repository
+
+Verify the repo is cloned at `.tmp/b2b-commerce-open-source-components`:
+
+1. **If directory does not exist:** Tell user: "I'm cloning the official B2B Commerce open source components repository from GitHub into a local `.tmp/` folder. This gives us access to all the open code components."
+   Then run: `git clone https://github.com/forcedotcom/b2b-commerce-open-source-components .tmp/b2b-commerce-open-source-components`
+2. **If directory exists** and contains `force-app/main/default/sfdc_cms__lwc` and `sfdc_cms__label`, present options:
+   > "Open source repository is already cloned. How would you like to proceed?"
+   > 1. **Reuse existing** — Use the already cloned repository
+   > 2. **Re-clone** — Remove and clone fresh from GitHub
+3. **If directory exists but structure is invalid:** Tell user: "The cloned repository has an unexpected structure. I'll remove it and clone a fresh copy."
+   Then remove and re-clone.
+4. **If clone fails:** inform user and abort
+
+### Check 2: Store and Site Metadata
+
+Verify a store is selected and site metadata is available locally:
+
+1. Tell user: "I'm checking if your project already has B2B store metadata locally."
+   Check if `<package-dir>/main/default/digitalExperiences/site/` contains any store directories.
+2. **If store metadata exists:** use it. If multiple stores found, ask user to select one.
+3. **If no store metadata found:** Try retrieving from the connected org before delegating:
+   1. Run `sf org list` (or check `sf config get target-org`) to find a connected org. Ask the user to confirm or pick one if more than one.
+   2. List `DigitalExperienceBundle` site bundles in that org with `sf org list metadata --metadata-type DigitalExperienceBundle --target-org <alias>`. Filter to `site/*` entries.
+   3. If at least one site bundle exists, ask the user which to use, then run:
+      `sf project retrieve start --metadata "DigitalExperienceBundle:site/<storeName>" --target-org <alias>`
+      The bundle lands at `<package-dir>/main/default/digitalExperiences/site/<storeName>/`.
+   4. **Only if no connected org is available, or no site bundles are found, or retrieve fails:** delegate to the **commerce-b2b-store-create** skill.
+
+**Required state** after all checks:
+- **Package dir** — the value resolved in Check 0 (e.g., `force-app`)
+- **Store name** — the selected `fullName` value (e.g., `My_B2B_Store1`)
+- **Site metadata path** — `<package-dir>/main/default/digitalExperiences/site/<store-name>/`
+- **Repo path** — `.tmp/b2b-commerce-open-source-components/`
+
+---
+
+## Integration Task
+
+Copy all components and labels from cloned repo to site directory:
+
+- **Source:** `.tmp/b2b-commerce-open-source-components/force-app/main/default/sfdc_cms__lwc/*` and `sfdc_cms__label/*` (the open source repo's own layout — always `force-app`)
+- **Destination:** `<package-dir>/main/default/digitalExperiences/site/<store-name>/sfdc_cms__lwc/` and `sfdc_cms__label/` (`<package-dir>` resolved in Check 0)
+
+**Steps:**
+
+1. Tell user: "I'm checking if open code components already exist in your store's site metadata."
+   Check if destination directories already contain files.
+2. If files exist, present options:
+   > "Components already exist in **{store-name}**. How would you like to proceed?"
+   > 1. **Overwrite all** — Replace all existing components with latest from repo
+   > 2. **Copy only new** — Skip existing components, copy only ones not yet present
+3. Tell user: "I'm now copying all open code LWC components from the cloned repository into your store's site metadata directory."
+   Copy all component directories from source to destination.
+4. Tell user: "I'm copying the associated label files that these components need."
+   Copy all label directories from source to destination.
+5. Report: "Copied X components and Y label sets"
+
+**Output:**
+```
+✅ Integration Complete!
+
+Copied: X components and Y label sets to <store-name>
+
+Next Steps:
+1. Deploy: sf project deploy start -d <package-dir>/main/default/digitalExperiences/site/<store-name>
+2. Open Experience Builder and use new components from the palette
+3. Publish your site when ready
+```
+
+---
+
+## Example Interaction
+
+**User:** "Integrate open code components to my store"
+
+**Agent:** "I'm checking if the open source components repository is already cloned locally..."
+
+**Agent:** _(repo exists)_
+> "Open source repository is already cloned. How would you like to proceed?"
+> 1. **Reuse existing** — Use the already cloned repository
+> 2. **Re-clone** — Remove and clone fresh from GitHub
+
+**User:** "1"
+
+**Agent:** "I'm checking if your project already has B2B store metadata locally..."
+- ✓ Found store metadata for My_B2B_Store1
+
+**Agent:** "I'm checking if open code components already exist in your store's site metadata..."
+
+**Agent:** _(files exist)_
+> "Components already exist in **My_B2B_Store1**. How would you like to proceed?"
+> 1. **Overwrite all** — Replace all existing components with latest from repo
+> 2. **Copy only new** — Skip existing components, copy only ones not yet present
+
+**User:** "1"
+
+**Agent:** "I'm now copying all open code LWC components from the cloned repository into your store's site metadata directory..."
+**Agent:** "I'm copying the associated label files that these components need..."
+- ✓ Copied 45 components and 38 label sets
+
+```
+✅ Integration Complete!
+
+Copied: 45 components and 38 label sets to My_B2B_Store1
+
+Next Steps:
+1. Deploy: sf project deploy start -d force-app/main/default/digitalExperiences/site/My_B2B_Store1
+2. Open Experience Builder and use new components from the palette
+3. Publish your site when ready
+```
+
+---
+
+## Error Handling
+
+| Error | Message | Action |
+|-------|---------|--------|
+| Store not found | "Store '{name}' not found in org." | List stores again |
+| Git clone failed | "Failed to clone repository. Check internet connection." | Retry or abort |
+| Invalid repo structure | "Repository structure has changed. Expected sfdc_cms__lwc and sfdc_cms__label." | Warn user, abort |
+| File copy failed | "Failed to copy files. Check file permissions." | Show error details |
+
+---
+
+## Verification Checklist
+
+- [ ] Startup Flow completed: repo cloned, store metadata available
+- [ ] Components copied to correct destination path (`sfdc_cms__lwc/`)
+- [ ] Labels copied to correct destination path (`sfdc_cms__label/`)
+- [ ] No file permission errors during copy
+- [ ] Deployment command provided and user informed about testing

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

@@ -0,0 +1,167 @@
+---
+name: commerce-b2b-store-create
+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."
+compatibility: "Requires Commerce licenses, Experience Cloud, Salesforce CLI"
+metadata:
+  version: "1.0"
+  category: "commerce"
+---
+
+# Commerce B2B Storefront Creation
+
+Interactive workflow to create a Commerce B2B Store in Salesforce and retrieve the auto-generated storefront metadata to your repository.
+
+## Critical Concepts
+
+Commerce B2B = Store (backend data) + Storefront (frontend metadata). **Store must be created first** in the org to auto-generate the Storefront. Never create storefront metadata manually.
+
+> See [Store vs Storefront Reference](references/store-vs-storefront.md)
+
+## When to Use This Skill
+
+Trigger when users request:
+- "Create a B2B Commerce store"
+- "Build a Commerce storefront"
+- "Set up Commerce B2B"
+- "Create B2B Commerce"
+- "Retrieve Commerce storefront metadata"
+- "Deploy B2B storefront"
+
+## Rules That Always Apply
+
+1. **Always follow the interactive flow.** Do NOT skip steps. Each step requires user confirmation before proceeding.
+
+2. **Never create storefront metadata manually.** The Commerce setup wizard generates hundreds of configuration values. Manual creation will fail.
+
+3. **Always list sites before retrieval.** Store names get underscores and number suffixes (e.g., "My B2B Store" → "My_B2B_Store1"). Let the user select from the actual list.
+
+4. **Always use `--json` flag.** Include `--json` on all Salesforce CLI commands for parseable output.
+
+## Interactive Workflow: 7 Steps
+
+### Step 1: Explain Commerce B2B Concept
+
+**Agent explains:** Commerce has Store (data) + Storefront (metadata). Store must be created first.
+
+> See: [Store vs Storefront Reference](references/store-vs-storefront.md)
+
+---
+
+### Step 2: Guide User to Create B2B Store
+
+**Agent provides these steps:**
+
+1. Navigate to **Setup → Commerce → Stores**
+   - Or: **App Launcher → Commerce → Create Store**
+
+2. Click **"Create Store"** or **"Setup New Store"**
+
+3. Select **"Commerce Store"** as the store type
+
+4. Follow the wizard:
+   - **Store Name**: Choose descriptive name (e.g., "My B2B Store")
+     - Important: Spaces become underscores in folder names
+   - **Site URL**: Unique URL name for the site 
+
+5. Complete wizard - it creates:
+   - WebStore record
+   - Default buyer group and entitlement policies
+   - Associated Digital Experience (LWR site)
+
+6. Optional: Configure payment gateway, tax provider, shipping
+
+**Agent then asks:**
+"Have you completed creating the B2B Store in your org? Reply 'yes' when ready and provide the store name you used."
+
+---
+
+### Step 3: Get User Confirmation
+
+**Agent waits for:** User confirmation and store name
+
+**Agent validates:** Store name format (no special characters, spaces will appear as underscores)
+
+**Agent acknowledges:** "Great! Let me list the available storefronts in your org..."
+
+---
+
+### Step 4: List Available LWR Sites
+
+**Agent executes:**
+```bash
+sf org list metadata --metadata-type DigitalExperienceConfig --json
+```
+
+**Agent should:**
+- Parse JSON output to extract site names
+- Display as numbered list
+- Explain naming (underscores, number suffixes)
+
+**Example output:**
+```
+Available Digital Experience sites:
+1. My_B2B_Store1
+2. Partner_Portal
+3. Customer_Community
+```
+
+---
+
+### Step 5: Let User Select Storefront
+
+**Agent asks:**
+"Which site corresponds to your B2B Store? Select the site name:"
+
+**Agent validates:** Selection matches available sites
+
+**Agent confirms:** "Got it! I'll retrieve metadata for [site-name]..."
+
+---
+
+### Step 6: Retrieve Storefront Metadata
+
+**Agent executes:**
+```bash
+sf project retrieve start -m DigitalExperienceBundle:site/<selected-store-name> --json
+```
+
+**Agent should:**
+- Show retrieval progress
+- Confirm successful retrieval
+- List retrieved directory structure
+
+**Expected output:**
+```
+Retrieved: force-app/main/default/digitalExperiences/site/My_B2B_Store1/
+├── My_B2B_Store1.digitalExperience-meta.xml
+├── sfdc_cms__view/ (home, current_cart, detail_*, list_*, etc.)
+├── sfdc_cms__site/
+├── sfdc_cms__route/
+└── [other sfdc_cms__* directories]
+```
+
+---
+
+### Step 7: Provide Next Steps
+
+**Agent provides:**
+
+✅ **Metadata retrieved successfully!**
+
+**Next steps:**
+- Customize with custom LWCs or branding changes
+- Deploy: `sf project deploy start --source-dir force-app/main/default/digitalExperiences/site/My_B2B_Store1/ --json`
+
+**Resources:** [DigitalExperienceBundle Docs](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_digitalexperiencebundle.htm), [B2B Commerce Guide](https://developer.salesforce.com/docs/atlas.en-us.b2b_commerce_dev_guide.meta/b2b_commerce_dev_guide/)
+
+---
+
+## Reference
+
+- **[store-vs-storefront.md](references/store-vs-storefront.md)** - Technical details on Store vs Storefront, source control, and why manual creation fails
+
+---
+
+## Remember
+
+**Store first (creates storefront) → Retrieve → Customize**

package/skills/commerce-b2b-store-create/references/store-vs-storefront.md

@@ -0,0 +1,169 @@
+# Commerce Store vs Storefront: Technical Reference
+
+## Overview
+
+Understanding the distinction between Commerce Store and Storefront is critical for successful Commerce B2B development. This document provides technical details about these two components and explains why they must be created in a specific order.
+
+---
+
+## The Two Components
+
+### 1. Commerce Store (Backend Data)
+
+**What it is:**
+- Runtime data and configuration created in the Salesforce org
+- NOT source-controllable metadata
+- Created through Commerce app UI
+
+**What it includes:**
+- Store configuration and settings
+- Default buyer groups (associated with Accounts)
+- Entitlement policies (who can see which products)
+- Pricing policies and price book mappings
+- Payment gateway configuration (Stripe, Adyen, etc.)
+- Tax provider configuration (Avalara, Vertex, manual)
+- Shipping methods and configurations
+- Product catalog associations
+- Inventory locations
+- Search index configurations
+
+**Where it lives:**
+- Data records in standard Commerce objects:
+  - `WebStore` - Store settings and configuration
+  - `BuyerGroup` - Account-based buyer segments
+  - `EntitlementPolicy` - Product visibility rules
+  - `CommerceEntitlementProduct` - Product-policy associations
+  - `ProductCatalog` - Catalog definitions
+  - `Pricebook2` - Price books
+  - Additional payment, tax, shipping records
+
+**How to create:**
+- Via UI: Setup → Commerce → Stores
+- Cannot be created via Metadata API
+- Cannot be deployed via `sf project deploy`
+
+---
+
+### 2. Storefront (Frontend Metadata)
+
+**What it is:**
+- Digital Experience (LWR site) for buyer-facing shopping experience
+- Source-controllable as ExperienceBundle metadata
+- Created automatically when you create a Commerce Store
+
+**What it includes:**
+- ExperienceBundle metadata (`StorefrontName.digitalExperience-meta.xml`)
+- URL routing configuration (`sfdc_cms__route`)
+- Page definitions (`sfdc_cms__view`)
+  - Homepage
+  - Product List Pages (PLP)
+  - Product Detail Pages (PDP)
+  - Shopping cart
+  - Checkout flow
+  - Order confirmation
+  - Search results
+- Lightning Web Components (product cards, cart components, checkout)
+- Branding and theme configuration (`sfdc_cms__brandingSet`, `sfdc_cms__theme`)
+- Page layouts (`sfdc_cms__themeLayout`)
+- Navigation structure
+- Custom LWCs for extensions
+
+**Where it lives:**
+- `force-app/main/default/digitalExperiences/site/StorefrontName/`
+- Example: `force-app/main/default/digitalExperiences/site/My_B2B_Store1/`
+
+**How to create:**
+- Automatically generated by Commerce Store setup wizard
+- Retrieved from org using Salesforce CLI
+- Cannot be manually created from scratch
+
+**How to deploy:**
+- Retrievable: `sf project retrieve start -m DigitalExperienceBundle:site/<name>`
+- Deployable: `sf project deploy start -m DigitalExperienceBundle`
+- Source-controllable in Git
+
+---
+
+## Why You Cannot Create Storefront Metadata from Scratch
+
+### Technical Reasons
+
+1. **Complex Dependency Chain**
+   - Create merchandisers store
+   - Create DigitalExperienceBundle
+   - Integrate both together
+
+2. **Hundreds of Auto-Generated Configurations**
+   - Component IDs and region IDs (UUIDs)
+   - WebStore associations
+   - Commerce-managed component configurations
+   - Default routing rules
+   - Search configurations
+   - Cart and checkout flow definitions
+   - Payment integration settings
+
+3. **Commerce-Managed Components**
+   - Product List Page (PLP) components
+   - Product Detail Page (PDP) components
+   - Cart components
+   - Checkout components
+   - Search components
+   - These require specific configurations from Store data
+
+4. **Metadata API Limitation**
+   - Metadata API deploys metadata types (Apex, LWCs, objects)
+   - Metadata API CANNOT create SObject data (WebStore records)
+   - Store creation requires data operations, not metadata operations
+
+---
+
+## The Required Creation Order
+
+### Step 1: Create Commerce Store (Must Be First)
+
+```
+User Interface (Commerce App)
+     ↓
+WebStore Record Created
+     ↓
+BuyerGroup Records Created
+     ↓
+EntitlementPolicy Records Created
+     ↓
+Digital Experience Auto-Generated
+     ↓
+Commerce Components Configured
+```
+
+**Why this must be first:**
+- Generates WebStore record with unique ID
+- Creates default configurations
+- Auto-generates associated Digital Experience
+- Configures Commerce component relationships
+- Sets up default buyer access rules
+
+### Step 2: Retrieve Storefront Metadata
+
+```
+sf org list metadata --metadata-type DigitalExperienceConfig
+     ↓
+Select Store from List
+     ↓
+sf project retrieve start -m DigitalExperienceBundle:site/<name>
+     ↓
+Metadata Saved to Local Repository
+     ↓
+Now Editable and Source-Controllable
+```
+
+---
+
+## Key Takeaway
+
+**Commerce B2B = Store (data) + Storefront (metadata)**
+
+1. Create Store → generates Storefront
+2. Retrieve Storefront → customize and version control if needed
+3. Deploy Storefront → only after creating Store in target org
+
+**Never skip the Store creation. Never create Storefront metadata from scratch.**

package/skills/creating-fix-work-item/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: creating-fix-work-item
-description: "Creates a DevOps Center WorkItem to track a fix for a test failure or Code Analyzer violation. Before creating anything, it shows a subject/assignee/project preview and requires explicit confirmation. Use this skill when you want to create a fix work item, track a remediation task, or assign a test or analysis failure to a developer. TRIGGER when: the user wants to create a fix work item, log a remediation, or assign a failure to a developer for resolution. DO NOT TRIGGER when: writing the fix code itself (use generating-apex)."
+description: "Creates a DevOps Center WorkItem to track a fix for a test failure or Code Analyzer violation. Before creating anything, it shows a subject/assignee/project preview and requires explicit confirmation. Use this skill when you want to create a fix work item, track a remediation task, or assign a test or analysis failure to a developer. TRIGGER when: the user wants to create a fix work item, log a remediation, or assign a failure to a developer for resolution. DO NOT TRIGGER when: writing the fix code itself (use platform-apex-generate)."
 metadata:
   version: "1.0"
   minApiVersion: "67.0"

package/skills/data360-activate/CREDITS.md

@@ -0,0 +1,5 @@
+# Credits & Acknowledgments
+
+This skill is part of the `*-datacloud` family. Shared attribution, upstream source mapping, and maintenance notes live in:
+- [../data360-orchestrate/CREDITS.md](../data360-orchestrate/CREDITS.md)
+- [../data360-orchestrate/UPSTREAM.md](../data360-orchestrate/UPSTREAM.md)

package/skills/data360-activate/README.md

@@ -0,0 +1,39 @@
+# data360-activate
+
+Activation and downstream delivery workflows for Salesforce Data Cloud.
+
+## Use this skill for
+
+- activations
+- activation targets
+- data actions
+- data action targets
+- downstream platform inspection before push
+
+## Example requests
+
+```text
+"Activate this segment to the downstream platform"
+"Show me what activation targets already exist"
+"Create a data action target for this integration"
+"Help me inspect why this activation is not ready"
+```
+
+## Common commands
+
+```bash
+sf data360 activation platforms -o myorg 2>/dev/null
+sf data360 activation-target list -o myorg 2>/dev/null
+sf data360 activation list -o myorg 2>/dev/null
+sf data360 data-action-target list -o myorg 2>/dev/null
+```
+
+## References
+
+- [SKILL.md](SKILL.md)
+- [../data360-orchestrate/assets/definitions/activation-target.template.json](../data360-orchestrate/assets/definitions/activation-target.template.json)
+- [../data360-orchestrate/assets/definitions/activation.template.json](../data360-orchestrate/assets/definitions/activation.template.json)
+- [../data360-orchestrate/assets/definitions/data-action-target.template.json](../data360-orchestrate/assets/definitions/data-action-target.template.json)
+- [../data360-orchestrate/assets/definitions/data-action.template.json](../data360-orchestrate/assets/definitions/data-action.template.json)
+- [../data360-orchestrate/references/plugin-setup.md](../data360-orchestrate/references/plugin-setup.md)
+- [CREDITS.md](CREDITS.md)

package/skills/data360-activate/SKILL.md

@@ -0,0 +1,117 @@
+---
+name: data360-activate
+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 data360-segment), data retrieval/search work (use data360-query), or STDM/session tracing (use agentforce-observe)."
+compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
+metadata:
+  version: "1.0"
+---
+
+# data360-activate: Data Cloud Act Phase
+
+Use this skill when the user needs **downstream delivery work**: activations, activation targets, data actions, or pushing Data Cloud outputs into other systems.
+
+## When This Skill Owns the Task
+
+Use `data360-activate` when the work involves:
+- `sf data360 activation *`
+- `sf data360 activation-target *`
+- `sf data360 data-action *`
+- `sf data360 data-action-target *`
+- verifying downstream delivery setup
+
+Delegate elsewhere when the user is:
+- still building the audience or insight → [data360-segment](../data360-segment/SKILL.md)
+- exploring query/search or search indexes → [data360-query](../data360-query/SKILL.md)
+- setting up base connections or ingestion → [data360-connect](../data360-connect/SKILL.md), [data360-prepare](../data360-prepare/SKILL.md)
+
+---
+
+## Required Context to Gather First
+
+Ask for or infer:
+- target org alias
+- destination platform or downstream system
+- whether the segment already exists and is published
+- whether the user needs create, inspect, update, or delete
+- whether the task is activation-focused or data-action-focused
+
+---
+
+## 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 ../data360-orchestrate/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.
+- Prefer read-only inspection first when the destination state is unclear.
+
+---
+
+## Recommended Workflow
+
+### 1. Classify readiness for act work
+```bash
+node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase act --json
+```
+
+### 2. Inspect destinations first
+```bash
+sf data360 activation platforms -o <org> 2>/dev/null
+sf data360 activation-target list -o <org> 2>/dev/null
+sf data360 data-action-target list -o <org> 2>/dev/null
+```
+
+### 3. Create the destination before the activation
+```bash
+sf data360 activation-target create -o <org> -f target.json 2>/dev/null
+sf data360 data-action-target create -o <org> -f target.json 2>/dev/null
+```
+
+### 4. Create the activation or data action
+```bash
+sf data360 activation create -o <org> -f activation.json 2>/dev/null
+sf data360 data-action create -o <org> -f action.json 2>/dev/null
+```
+
+### 5. Verify downstream readiness
+```bash
+sf data360 activation list -o <org> 2>/dev/null
+sf data360 activation data -o <org> --name <activation> 2>/dev/null
+```
+
+---
+
+## High-Signal Gotchas
+
+- Activation design depends on a healthy published upstream segment.
+- Destination configuration usually comes before activation creation.
+- Downstream credential and platform constraints may live outside the Data Cloud CLI alone.
+- Read-only inspection is the safest first move when the destination setup is unclear.
+- `CdpActivationTarget` or `CdpActivationExternalPlatform` means the activation surface is gated for the current org/user; guide the user toward activation setup, permissions, and destination configuration instead of retrying blindly.
+
+---
+
+## Output Format
+
+```text
+Act task: <activation / activation-target / data-action / data-action-target>
+Destination: <platform or target>
+Target org: <alias>
+Artifacts: <definition files / commands>
+Verification: <listed / created / blocked>
+Next step: <destination validation or downstream testing>
+```
+
+---
+
+## References
+
+- [README.md](README.md)
+- [../data360-orchestrate/assets/definitions/activation-target.template.json](../data360-orchestrate/assets/definitions/activation-target.template.json)
+- [../data360-orchestrate/assets/definitions/activation.template.json](../data360-orchestrate/assets/definitions/activation.template.json)
+- [../data360-orchestrate/assets/definitions/data-action-target.template.json](../data360-orchestrate/assets/definitions/data-action-target.template.json)
+- [../data360-orchestrate/assets/definitions/data-action.template.json](../data360-orchestrate/assets/definitions/data-action.template.json)
+- [../data360-orchestrate/UPSTREAM.md](../data360-orchestrate/UPSTREAM.md)
+- [../data360-orchestrate/references/plugin-setup.md](../data360-orchestrate/references/plugin-setup.md)
+- [../data360-orchestrate/references/feature-readiness.md](../data360-orchestrate/references/feature-readiness.md)

package/skills/data360-connect/CREDITS.md

@@ -0,0 +1,5 @@
+# Credits & Acknowledgments
+
+This skill is part of the `*-datacloud` family of skills covering the full Data Cloud workflow lifecycle. Shared upstream source mapping and maintenance notes live in:
+- [../data360-orchestrate/CREDITS.md](../data360-orchestrate/CREDITS.md)
+- [../data360-orchestrate/UPSTREAM.md](../data360-orchestrate/UPSTREAM.md)