LogoAwesome Skills
  • Search
  • Category
  • Tag
  • Blog
LogoAwesome Skills
LogoAwesome Skills

Discover Open-Source Agent Skills for AI Coding Assistants

Product

  • Search
  • Category
  • Tag
  • Blog

Resources

  • Claude Skill Docs
  • Antigravity Skills Docs

Tools

  • Claude Code
  • OpenCode
  • Cursor
  • Codex
  • Antigravity

Company

  • Privacy Policy
  • Terms of Service
  • Sitemap

©2026 Awesome Skills. All rights reserved.

Privacy PolicyTerms
Back to Skills

data360-segment

Salesforce Data Cloud Segment phase. Use this skill when the user creates or publishes segments, manages calculated insights, or troubleshoots audience SQL in Data Cloud. TRIGGER when: user creates or publishes segments, manages calculated insights, inspects segment counts or membership, or troubleshoots audience SQL in Data Cloud. DO NOT TRIGGER when: the task is DMO/mapping/identity-resolution work (use data360-harmonize), activation work (use data360-activate), query/search-index work (use da

753stars278forksUpdated 7/25/2026
Database Management#audiences#sql#cli#data-cloud#salesforce#segmentation

Security Assessment

Safe(93/100)
Security Score93/100

About data360-segment

This skill covers the Segment phase of Salesforce Data Cloud, focused on audience and insight work: creating and publishing segments, managing calculated insights, checking member counts, and troubleshooting audience SQL. It solves the problem of building and validating Data Cloud audiences reliably by giving the assistant clear task ownership, a repeatable workflow, and guidance on the quirks that make segment work fail silently — such as asynchronous publish steps and segment SQL not being the same as CRM SOQL.

It operates through the external community sf data360 CLI plugin against a Data Cloud-enabled org. The documented workflow runs a shared readiness classifier from the companion data360-orchestrate skill, inspects existing segments and calculated insights, creates them from reusable JSON definitions (using an explicit API version when creation behavior is unstable on newer defaults), publishes or runs them explicitly, and then verifies success with member counts or SQL queries rather than assuming completion. It captures high-signal gotchas: segment creation sometimes requiring api-version 64.0, segment members returning opaque IDs (so SQL joins are preferred for readable details), publish/run kicking off asynchronous work, and an empty list usually meaning unconfigured rather than unavailable. It delegates DMO/mapping/identity-resolution work to data360-harmonize, activation to data360-activate, and read-only SQL/search-index queries to data360-query. These are standard, org-scoped administrative operations on the authenticated org.

The target users are Salesforce Data Cloud administrators, marketers, and consultants building audiences. Use cases include creating a high-value customer segment, diagnosing why a segment returns zero members, running and verifying a calculated insight, and getting member counts.

FAQ

What is this skill for?

Creating and publishing Data Cloud segments, managing calculated insights, checking segment member counts, and troubleshooting audience SQL. It does not handle DMO/mapping, activation, or read-only query work — those route to sibling data360 skills.

What are the prerequisites?

The external community sf data360 CLI plugin and a Data Cloud-enabled org authenticated via the SF CLI. The workflow also relies on the shared readiness classifier script from the data360-orchestrate skill.

Why might segment creation fail on the default API version?

Segment creation behavior can be unstable on newer defaults, so the skill recommends passing --api-version 64.0 when creation is failing.

How do I confirm a segment or insight actually succeeded?

Because publish and run steps kick off asynchronous work even when the command returns quickly, the skill advises verifying with segment count or a SQL COUNT query rather than assuming success.

Why does my segment return only opaque member IDs?

The segment members command returns opaque IDs; when human-readable member details are needed the skill recommends using SQL joins instead. Note that Data Cloud segment SQL is not the same as CRM SOQL.

All Files

2 files
README.md1.1 KB
View
SKILL.md4.6 KB
View

Install data360-segment

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

forcedotcom/sf-skills

Related Skills

import-on-interaction

256

radon-mcp

296

investigating-incidents-with-aws-devops-agent

2,945

mantis-structural-index

2,518