mcpField
S
sf-datacloud-act

sf-datacloud-act

github.com/jaganproData & databases424971 installsUpdated 26w ago
Repository

About sf-datacloud-act

sf-datacloud-act is a skill for downstream delivery in Salesforce Data Cloud, covering segment activations, targets, and data actions. It guides users to inspect upstream segments and destinations before setup, then verify delivery readiness.

Key features

  1. 01Inspect activation platforms and targets
  2. 02Create activation and data-action targets
  3. 03Create activations and data actions
  4. 04Verify downstream delivery status
  5. 05Check readiness before changes

Use cases

  1. 01Set up downstream activation for a published segment
  2. 02Configure a destination for an activation
  3. 03Send Data Cloud outputs to downstream systems
  4. 04Check activation or data-action delivery status

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jaganpro/sf-skills --skill sf-datacloud-act

After installing, type/sf-datacloud-actin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

CREDITS.md
LICENSE
README.md

Details

From the project README

sf-datacloud-act: 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 sf-datacloud-act 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:

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 ~/.claude/skills/sf-datacloud/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 ~/.claude/skills/sf-datacloud/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

Comments

Markdown supported