What is the primary function of the data360-activate skill?

The data360-activate skill is used to manage activations, activation targets, and data actions within the Salesforce Data Cloud.

When should I use this skill?

Use this skill when you need to perform downstream delivery tasks, such as creating or inspecting activation assets.

What tasks should I avoid with this skill?

Avoid using this skill for segment creation or data retrieval tasks; use the appropriate skills like data360-segment or data360-query instead.

How do I verify the readiness of my activation assets?

You can verify readiness by running a specific command that checks the health of your upstream segments before creating downstream assets.

What are the prerequisites for using this skill?

You need to gather context such as the target org alias, destination platform, and whether the segment exists before using this skill.

Data Cloud Activation

Name: Data Cloud Activation
Availability: InStock
Author: forcedotcom

OfficialFree

Manage activations and data actions for Salesforce Data Cloud.

by forcedotcom808 stars on forcedotcom/sf-skills

2 views

Updated Aug 10, 2026

Get this skill

Free · Opens the source repo

What Data Cloud Activation does

The data360-activate skill is designed for users who need to manage activations, activation targets, data actions, and the downstream delivery of audiences and data within the Salesforce Data Cloud environment. This skill is particularly useful for developers and data engineers who are involved in the operational aspects of data activation, ensuring that data flows seamlessly from the Data Cloud to various downstream systems. With this skill, users can efficiently create, inspect, update, and delete activation assets, all while adhering to best practices for data management.

To effectively use this skill, users must first ensure that the upstream segments or insights are healthy. This is achieved by running a readiness check using the provided command, which assesses the current state of the organization and its readiness for activation tasks. Once the readiness is confirmed, users can proceed to inspect available platforms and targets before creating any activation or data action assets. This structured approach minimizes the risk of errors and ensures that all necessary configurations are in place before proceeding with data delivery.

The data360-activate skill is not intended for tasks related to segment creation, data retrieval, or session tracing. For those tasks, users should refer to other skills such as data360-segment or data360-query. This clear delineation helps users select the right tool for their specific needs, streamlining their workflow and enhancing productivity.

Overall, data360-activate is a specialized tool for Salesforce Data Cloud users who require a focused solution for managing activation workflows and ensuring that data is delivered accurately and efficiently to downstream systems.

When to use it

Use this skill when you need to manage activations, targets, or data actions in Salesforce Data Cloud.

When not to use it

Do not use this skill for segment creation or data retrieval tasks; those should be handled by other specialized skills.

What you can build with it

Creating Activation Targets

Use the skill to create new activation targets in Salesforce Data Cloud, ensuring proper setup before downstream delivery.

Verifying Downstream Delivery

Check the readiness of downstream delivery setups to ensure that data actions and activations are configured correctly.

Managing Data Actions

Utilize this skill to create and manage data actions within the Salesforce Data Cloud environment.

How to install Data Cloud Activation

View source

1. Install with the skills CLI

npx skills add forcedotcom/sf-skills/data360-activate --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by forcedotcom

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
exploring query/search or search indexes → data360-query
setting up base connections or ingestion → data360-connect, data360-prepare

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

node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase act --json

2. Inspect destinations first

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

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

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

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

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

Frequently asked questions about Data Cloud Activation

Similar skills

Power BI Semantic Modeling

Optimize your Power BI data models with best practices.

Data Context Extractor

Tailor data analysis skills to your company's needs.

Power BI Performance Troubleshooting

Systematic guidance for optimizing Power BI performance.

Power BI Model Design Review

Optimize your Power BI data models with expert reviews.

Power BI DAX Formula Optimizer

Optimize your DAX formulas for better performance and clarity.

Fabric Lakehouse

Optimize your data solutions with Lakehouse best practices.