Agent skill

Sf Datacloud Act

Salesforce Data Cloud Act phase. An agent skill from Jaganpro/sf-skills.

Install Sf Datacloud Act

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-datacloud-act -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-datacloud-act --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sf-datacloud-act .claude/skills/sf-datacloud-act && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "sf-datacloud-act" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-datacloud-act into .claude/skills/sf-datacloud-act/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-datacloud-act", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-datacloud-act

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-datacloud-act -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-datacloud-act --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sf-datacloud-act .agents/skills/sf-datacloud-act && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "sf-datacloud-act" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-datacloud-act into .agents/skills/sf-datacloud-act/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-datacloud-act", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-datacloud-act -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-datacloud-act --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sf-datacloud-act .cursor/skills/sf-datacloud-act && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "sf-datacloud-act" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-datacloud-act into .cursor/skills/sf-datacloud-act/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-datacloud-act", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Jaganpro/sf-skills.git --path skills/sf-datacloud-act

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-datacloud-act -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-datacloud-act --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sf-datacloud-act .gemini/skills/sf-datacloud-act && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "sf-datacloud-act" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-datacloud-act into .gemini/skills/sf-datacloud-act/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-datacloud-act", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-datacloud-act

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-datacloud-act -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sf-datacloud-act .github/skills/sf-datacloud-act && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "sf-datacloud-act" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-datacloud-act into .github/skills/sf-datacloud-act/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-datacloud-act", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-datacloud-act -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-datacloud-act --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sf-datacloud-act .opencode/skills/sf-datacloud-act && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "sf-datacloud-act" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-datacloud-act into .opencode/skills/sf-datacloud-act/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-datacloud-act", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: sf-datacloud-act
GitHub stars: 424
Token cost: ~1.3k tokens
SKILL.md length: 305 words
Files: 4
Skills in repo: 36
Repo updated: Apr 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Salesforce Data Cloud Act phase. An agent skill from Jaganpro/sf-skills.

Works in 5 steps: Classify readiness for act work → Inspect destinations first → Create the destination before the… → …
: user manages activations
SKILL.md covers When This Skill Owns the Task, Required Context to Gather First, Core Operating Rules and Recommended Workflow, plus 3 more sections
Calls sf and node

What it does

Sf Datacloud Act is an agent skill from Jaganpro/sf-skills. Salesforce Data Cloud Act phase. 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 sf-datacloud-segment), data retrieval/search work (use sf-datacloud-retrieve), or STDM/session tracing (use sf-ai-agentforce-observability).

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `CREDITS.md` and `README.md`). Compatibility notes: Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org

It sits in Sales & Support, covering CRM management and Observability. It works with Salesforce. The repository describes itself as: [ARCHIVED — migrated to forcedotcom/afv-library] Salesforce Skills for Agentic Coding Tools — Apex, Flow, LWC, SOQL, Agentforce, Data Cloud, OmniStudio. Read-only archive; active… The licence is MIT.

When your agent uses it

: user manages activations
Activation targets
Downstream delivery of Data Cloud audiences and data
: the task is segment creation (use sf-datacloud-segment)

Example prompts

“/sf-datacloud-act”

Requirements

Compatibility (from SKILL.md): Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Classify readiness for act work
Inspect destinations first
Create the destination before the activation
Create the activation or data action
Verify downstream readiness

What it can do on your machine

Read from SKILL.md and the folder at commit 53c9956. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- sf
- node
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org
From compatibility in the SKILL.md frontmatter.

Context cost

Sf Datacloud Act loads about 1.3k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 305 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~94
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Jaganpro/sf-skills at commit 53c9956, republished under its MIT licence (© Jaganpro). 305 words, ~1,260 tokens.

Download SKILL.mdSave it as .claude/skills/sf-datacloud-act/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: sf-datacloud-act
description: Salesforce Data Cloud Act phase. 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 sf-datacloud-segment), data retrieval/search work (use sf-datacloud-retrieve), or STDM/session tracing (use sf-ai-agentforce-observability).
compatibility: Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org
license: MIT
metadata.version: 1.0.0
metadata.author: Gnanasekaran Thoppae
metadata.phase: Act

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:

still building the audience or insight → sf-datacloud-segment
exploring query/search or search indexes → sf-datacloud-retrieve
setting up base connections or ingestion → sf-datacloud-connect, sf-datacloud-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 ~/.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

bash

node ~/.claude/skills/sf-datacloud/scripts/diagnose-org.mjs -o <org> --phase act --json

2. Inspect destinations first

bash

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

bash

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

bash

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

bash

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

text

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

Files

SKILL.md and 3 other files in skills/sf-datacloud-act of Jaganpro/sf-skills.

SKILL.md
CREDITS.md
LICENSE
README.md

Open the folder on GitHubat commit 53c9956

Compare with similar skills

Sf Datacloud Act next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sf Datacloud Act compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Sf Datacloud Act this skillJaganpro/sf-skills	424	—	~1.3k	Automated safety check: Pass	MIT	5 mo ago
Salesforce Observabilityjeremylongshore/tons-of-skills-marketplace	2.8k	—	~1.1k	Automated safety check: Pass	MIT	today
Consumer Goods Accruals Datakit Deployforcedotcom/sf-skills	1.1k	—	~4.8k	Automated safety check: Pass	Apache-2.0	today
Salesforce Incident Runbookjeremylongshore/tons-of-skills-marketplace	2.8k	—	~1.1k	Automated safety check: Pass	MIT	today
Platform Trust Archive Manageforcedotcom/sf-skills	1.1k	—	~3k	Automated safety check: Pass	Apache-2.0	today
Service Itsm Incident Mgmt Configureforcedotcom/sf-skills	1.1k	—	~3.7k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Salesforce Observability
jeremylongshore/tons-of-skills-marketplace
Build Salesforce integration observability across application traces, platform status, limits, async jobs, events, logs, and business reconciliation.
2.8k GitHub stars~1.1k tokensUpdated today
Sales & SupportAuto-check passed
Consumer Goods Accruals Datakit Deploy
forcedotcom/sf-skills
A skill your agent uses to deploy the TPM Liability Accruals data kit end to end to a Salesforce org.
1.1k GitHub stars~4.8k tokensUpdated today
Sales & SupportAuto-check passed
Salesforce Incident Runbook
jeremylongshore/tons-of-skills-marketplace
Run evidence-led Salesforce integration incident response from detection through containment, recovery, reconciliation, and prevention.
2.8k GitHub stars~1.1k tokensUpdated today
Sales & SupportAuto-check passed
Platform Trust Archive Manage
forcedotcom/sf-skills
ALWAYS USE THIS SKILL for anything involving Salesforce Archive (also called Trusted Services Archive) — search, view, unarchive, analyze, mask, and erase (RTBF) archived records via the Archive…
1.1k GitHub stars~3k tokensUpdated today
Sales & SupportAuto-check passed
Service Itsm Incident Mgmt Configure
forcedotcom/sf-skills
Reads and toggles the master Incident Management setting on a Salesforce ITSM org — the org-level switch that turns Incident Management on or off.
1.1k GitHub stars~3.7k tokensUpdated today
Sales & SupportAuto-check passed
Service Itsm Agentic Setup Configure
forcedotcom/sf-skills
Top-level orchestrator for setting up IT Service Management (ITSM) in Salesforce Service Cloud.
1.1k GitHub stars~3.2k tokensUpdated today
Sales & SupportAuto-check passed

Questions about Sf Datacloud Act

What does Sf Datacloud Act do?

Salesforce Data Cloud Act phase. An agent skill from Jaganpro/sf-skills. Sf Datacloud Act is an agent skill from Jaganpro/sf-skills. Salesforce Data Cloud Act phase.

When should I use Sf Datacloud Act?

Sf Datacloud Act fits situations like: : user manages activations; activation targets; downstream delivery of Data Cloud audiences and data; : the task is segment creation (use sf-datacloud-segment).

How do I install Sf Datacloud Act in Claude Code?

Run `npx skills add Jaganpro/sf-skills --skill sf-datacloud-act -a claude-code`. Or copy the skill folder (skills/sf-datacloud-act in Jaganpro/sf-skills) into .claude/skills/sf-datacloud-act in your project. Claude Code loads it when a task matches its description.

How do I install Sf Datacloud Act in Codex?

Run `npx skills add Jaganpro/sf-skills --skill sf-datacloud-act -a codex`. Or copy the skill folder (skills/sf-datacloud-act in Jaganpro/sf-skills) into .agents/skills/sf-datacloud-act in your project. Codex loads it when a task matches its description.

Can I use Sf Datacloud Act in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jaganpro/sf-skills --skill sf-datacloud-act -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sf-datacloud-act, .gemini/skills/sf-datacloud-act, .github/skills/sf-datacloud-act and .opencode/skills/sf-datacloud-act in your project.

What does Sf Datacloud Act need to run?

Going by SKILL.md and its folder, Sf Datacloud Act needs the command-line tools its instructions call (sf and node). Compatibility (from SKILL.md): Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org.

Does Sf Datacloud Act access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sf Datacloud Act safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sf Datacloud Act use?

Sf Datacloud Act is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sf Datacloud Act use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Sf Datacloud Act?

Skills that share tags, products or a category with Sf Datacloud Act: Salesforce Observability (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Consumer Goods Accruals Datakit Deploy (forcedotcom/sf-skills, 1.1k stars), Salesforce Incident Runbook (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Platform Trust Archive Manage (forcedotcom/sf-skills, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sf Datacloud Act?

Jaganpro (a GitHub user) maintains it in Jaganpro/sf-skills, which has 424 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on April 27, 2026.

Source: Jaganpro/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Sf Datacloud Act

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

sf-datacloud-act: Data Cloud Act Phase

When This Skill Owns the Task

Required Context to Gather First

Core Operating Rules

Recommended Workflow

1. Classify readiness for act work

2. Inspect destinations first

3. Create the destination before the activation

4. Create the activation or data action

5. Verify downstream readiness

High-Signal Gotchas

Output Format

References

Files

Compare with similar skills

Similar skills

More from Jaganpro/sf-skills

Related

Questions about Sf Datacloud Act