/data360-orchestrate

name: data360-orchestrate
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 agentforce-observe), standard CRM SOQL (use platform-soql-query), or Apex implementation (use platform-apex-generate)."
compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
metadata:
  cliTools:
    - tool: ["curl"]
      semver: ">=7.0.0"
    - tool: ["git"]
      semver: ">=2.0.0"
    - tool: ["node"]
      semver: ">=18.0.0"
    - tool: ["npx"]
      semver: ">=9.0.0"
    - tool: ["python3"]
      semver: ">=3.10.0"
    - tool: ["sf"]
      semver: ">=2.0.0"
    - tool: ["yarn"]
      semver: ">=1.22.0"
  relatedSkills:
    - "agentforce-observe"
    - "automation-flow-generate"
    - "data360-activate"
    - "data360-connect"
    - "data360-harmonize"
    - "data360-prepare"
    - "data360-query"
    - "data360-segment"
    - "platform-apex-generate"
    - "platform-custom-field-generate"
    - "platform-custom-object-generate"
    - "platform-data-manage"
    - "platform-metadata-deploy"
    - "platform-soql-query"
  version: "1.0"

data360-orchestrate: Salesforce Data Cloud Orchestrator

Use this skill when the user needs **product-level Data Cloud workflow guidance** rather than a single isolated command family: pipeline setup, cross-phase troubleshooting, data spaces, data kits, or deciding whether a task belongs in Connect, Prepare, Harmonize, Segment, Act, or Retrieve.

This skill intentionally follows sf-skills house style while using the external `sf data360` command surface as the runtime. The plugin is **not vendored into this repo**.

---

When This Skill Owns the Task

Use `data360-orchestrate` when the work involves:

• multi-phase Data Cloud setup or remediation
• data spaces (`sf data360 data-space *`)
• data kits (`sf data360 data-kit *`)
• health checks (`sf data360 doctor`)
• CRM-to-unified-profile pipeline design
• deciding how to move from ingestion → harmonization → segmentation → activation
• cross-phase troubleshooting where the root cause is not yet clear

Delegate to a phase-specific skill when the user is focused on one area:

| Phase | Use this skill | Typical scope | |---|---|---| | Connect | [data360-connect](../data360-connect/SKILL.md) | connections, connectors, source discovery | | Prepare | [data360-prepare](../data360-prepare/SKILL.md) | data streams, DLOs, transforms, DocAI | | Harmonize | [data360-harmonize](../data360-harmonize/SKILL.md) | DMOs, mappings, identity resolution, data graphs | | Segment | [data360-segment](../data360-segment/SKILL.md) | segments, calculated insights | | Act | [data360-activate](../data360-activate/SKILL.md) | activations, activation targets, data actions | | Retrieve | [data360-query](../data360-query/SKILL.md) | SQL, search indexes, vector search, async query |

Delegate outside the family when the user is:

• extracting Session Tracing / STDM telemetry → [agentforce-observe](../agentforce-observe/SKILL.md)
• writing CRM SOQL only → [platform-soql-query](../platform-soql-query/SKILL.md)
• loading CRM source data → [platform-data-manage](../platform-data-manage/SKILL.md)
• creating missing CRM schema → [platform-custom-object-generate](../platform-custom-object-generate/SKILL.md) or [platform-custom-field-generate](../platform-custom-field-generate/SKILL.md)
• implementing downstream Apex or Flow logic → [platform-apex-generate](../platform-apex-generate/SKILL.md), [automation-flow-generate](../automation-flow-generate/SKILL.md)

---

Required Context to Gather First

Ask for or infer:

• target org alias
• whether the plugin is already installed and linked
• whether the user wants design guidance, read-only inspection, or live mutation
• data sources involved: CRM objects, external databases, file ingestion, knowledge, etc.
• desired outcome: unified profiles, segments, activations, vector search, analytics, or troubleshooting
• whether the user is working in the default data space or a custom one
• whether the org has already been classified with `scripts/diagnose-org.mjs`
• which command family is failing today, if any

If plugin availability or org readiness is uncertain, start with:

• [references/plugin-setup.md](references/plugin-setup.md)
• [references/feature-readiness.md](references/feature-readiness.md)
• `scripts/verify-plugin.sh`
• `scripts/diagnose-org.mjs`
• `scripts/bootstrap-plugin.sh`

---

Core Operating Rules

• Use the external `sf data360` plugin runtime; do **not** reimplement or vendor the command layer.
• Prefer the smallest phase-specific skill once the task is localized.
• Run readiness classification before mutation-heavy work. Prefer `scripts/diagnose-org.mjs` over guessing from one failing command.
• For `sf data360` commands, suppress linked-plugin warning noise with `2>/dev/null` unless the stderr output is needed for debugging.
• Distinguish **Data Cloud SQL** from CRM SOQL.
• Do **not** treat `sf data360 doctor` as a full-product readiness check; the current upstream command only checks the search-index surface.
• Do **not** treat `query describe` as a universal tenant probe; only use it with a known DMO/DLO table after broader readiness is confirmed.
• Preserve Data Cloud-specific API-version workarounds when they matter.
• Prefer generic, reusable JSON definition files over org-specific workshop payloads.

---

Recommended Workflow

1. Verify the runtime and auth

Confirm:

• `sf` is installed
• the community