Data Cloud skills

Agentforce Observability

forcedotcom

Enhance your Agentforce agents with session data insights.

D

Data Cloud Orchestrator

forcedotcom

Manage multi-phase Salesforce Data Cloud workflows.

Data Cloud Preparation

forcedotcom

Streamline your data ingestion and lake preparation.

Data Cloud Connect

forcedotcom

Manage and configure Data Cloud connections seamlessly.

Data Cloud Code Extensions

forcedotcom

Efficiently develop and deploy Python transformations for Salesforce Data Cloud.

Agentforce Platform Tracing

forcedotcom

Manage Agentforce agent tracing settings for Data Cloud.

Data Cloud Segment

forcedotcom

Manage segments and insights in Salesforce Data Cloud.

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 platform-soql-query), segment creation or calculated insight design (use data360-segment), or STDM/session tracing/parquet analysis (use agentforce-observe).

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).

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 agentforce-architecture-analyze instead) or for runtime perf/latency/SLO questions that require platform telemetry beyond Data Cloud.