data360-orchestrate

Orchestrates multi-phase Salesforce Data Cloud pipelines using the sf data360 CLI runtime.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/padjei/SF_Build --skill data360-orchestrate-padjei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: data360-orchestrate
Source: https://github.com/padjei/SF_Build/tree/main/.claude/skills/data360-orchestrate
Command: npx skills add https://github.com/padjei/SF_Build --skill data360-orchestrate-padjei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Setting up or troubleshooting Salesforce Data Cloud spans many phases—connections, ingestion, harmonization, segmentation, activation—and it is hard to know which command family or readiness check applies when something fails. This Skill provides cross-phase orchestration, readiness classification, and routing to the right phase-specific workflow. ## Core Features & Use Cases - Cross-Phase Orchestration: Coordinates connect, prepare, harmonize, segment, act, and retrieve workflows through the external sf data360 CLI plugin, delegating to phase-specific skills once a problem is localized. - Readiness Diagnosis: Classifies org readiness per phase with scripts/diagnose-org.mjs, distinguishing feature-gated modules, empty-but-enabled modules, query-plane issues, and runtime/auth failures before any mutation. - Deterministic Templates: Ships generic JSON definition templates for data streams, DMOs, mappings, identity resolution, segments, activations, and search indexes. - Use Case: When unified profile counts stop growing, run the readiness classifier to determine whether the root cause sits in mappings, identity resolution, or segment SQL, then hand off to the matching phase skill. ## Quick Start Ask the assistant to diagnose Data Cloud readiness for your org alias and plan a Customer 360 pipeline across ingestion, harmonization, and segmentation.

Frequently Asked Questions about data360-orchestrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a Salesforce Data Cloud pipeline from the CLI?▼

Verify the sf data360 plugin with scripts/verify-plugin.sh, classify org readiness with scripts/diagnose-org.mjs, then inspect existing state with read-only commands like data-space list and dmo list before creating streams, mappings, and segments from the JSON templates.

How do I troubleshoot Data Cloud when unified profiles are not increasing?▼

Run the diagnose-org.mjs classifier to check each phase, then localize the issue: ingestion problems belong to Prepare, mapping or identity resolution issues belong to Harmonize, and segment SQL issues belong to Segment. The orchestrator routes you to the right phase-specific skill.

Does sf data360 doctor check whether all of Data Cloud is enabled?▼

No. The doctor command only checks the search-index endpoint, so it can fail on partially provisioned orgs while other read-only commands still work. Treat it as advisory and confirm readiness with data-space list, dmo list, and segment list probes.

What does the 'Couldn't find CDP tenant ID' error mean in Data Cloud?▼

It means the query plane could not resolve a CDP tenant for that request, not that the whole product is disabled. Re-check broader readiness with data-space list, dmo list, and doctor, then retry query describe only with a known DMO or DLO table name.

Can Data Cloud provisioning be fully automated from the CLI?▼

No. Initial tenant provisioning, license assignment, and some org-wide enablement steps require Setup UI or account-level activation. Once provisioned, many workflows like data spaces, segments, activation targets, and search indexes are programmatic through sf data360.

When should I use a phase-specific Data Cloud skill instead of the orchestrator?▼

Use a phase-specific skill once the task is isolated to one area: data360-connect for connections, data360-prepare for streams and DLOs, data360-harmonize for mappings and identity resolution, data360-segment, data360-activate, or data360-query for SQL and search indexes.