Agent skill

Data360 Schema Get

Retrieve Data Lake Object (DLO) and Data Model Object (DMO) schema information from Salesforce Data Cloud using REST APIs.

Apache-2.0Auto-check passedBackend & APIs

Install Data360 Schema Get

skills CLI

$ npx skills add forcedotcom/sf-skills --skill data360-schema-get -a claude-code

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

GitHub CLI

$ gh skill install forcedotcom/sf-skills data360-schema-get --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/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/data360-schema-get .claude/skills/data360-schema-get && 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 "data360-schema-get" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/data360-schema-get into .claude/skills/data360-schema-get/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data360-schema-get", 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/forcedotcom/sf-skills/tree/main/skills/data360-schema-get

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 forcedotcom/sf-skills --skill data360-schema-get -a codex

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

GitHub CLI

$ gh skill install forcedotcom/sf-skills data360-schema-get --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/data360-schema-get .agents/skills/data360-schema-get && 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 "data360-schema-get" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/data360-schema-get into .agents/skills/data360-schema-get/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data360-schema-get", 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 forcedotcom/sf-skills --skill data360-schema-get -a cursor

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

GitHub CLI

$ gh skill install forcedotcom/sf-skills data360-schema-get --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/data360-schema-get .cursor/skills/data360-schema-get && 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 "data360-schema-get" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/data360-schema-get into .cursor/skills/data360-schema-get/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data360-schema-get", 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/forcedotcom/sf-skills.git --path skills/data360-schema-get

--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 forcedotcom/sf-skills --skill data360-schema-get -a gemini-cli

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

GitHub CLI

$ gh skill install forcedotcom/sf-skills data360-schema-get --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/forcedotcom/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/data360-schema-get .gemini/skills/data360-schema-get && 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 "data360-schema-get" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/data360-schema-get into .gemini/skills/data360-schema-get/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data360-schema-get", 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 forcedotcom/sf-skills data360-schema-get

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 forcedotcom/sf-skills --skill data360-schema-get -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/data360-schema-get .github/skills/data360-schema-get && 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 "data360-schema-get" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/data360-schema-get into .github/skills/data360-schema-get/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data360-schema-get", 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 forcedotcom/sf-skills --skill data360-schema-get -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 forcedotcom/sf-skills data360-schema-get --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/data360-schema-get .opencode/skills/data360-schema-get && 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 "data360-schema-get" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/data360-schema-get into .opencode/skills/data360-schema-get/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data360-schema-get", 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: data360-schema-get
GitHub stars: 1.1k
Token cost: ~2.3k tokens
SKILL.md length: 658 words
Files: 4 (incl. scripts, references)
Skills in repo: 251
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Retrieve Data Lake Object (DLO) and Data Model Object (DMO) schema information from Salesforce Data Cloud using REST APIs.

Works in 4 steps: Discover Connected Org → Validate SF CLI Authentication → Present Results → …
You need to inspect DLO
SKILL.md covers Overview, When to Use, Prerequisites and Skill Execution, plus 6 more sections
Runs Python scripts from its folder; calls sf and python3

What it does

Data360 Schema Get is an agent skill from forcedotcom/sf-skills. Retrieve Data Lake Object (DLO) and Data Model Object (DMO) schema information from Salesforce Data Cloud using REST APIs. Use this skill when you need to inspect DLO or DMO field definitions, data types, or metadata. Takes org alias and optional DLO/DMO name as parameters.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/README.md`, `scripts/get_dlo_schema.py` and `scripts/get_dmo_schema.py`).

It sits in Backend & APIs, covering REST APIs and CRM management. It works with Salesforce. The repository describes itself as: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.

When your agent uses it

You need to inspect DLO
DMO field definitions

Example prompts

“/data360-schema-get”

Requirements

Python 3

Workflow steps

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

Discover Connected Org
Validate SF CLI Authentication
Present Results
Offer Next Steps

What it can do on your machine

Read from SKILL.md and the folder at commit e5164d9. 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
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
- sf
- python3
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.

Context cost

Data360 Schema Get loads about 2.3k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 658 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~73
When it runs · the whole SKILL.md, loaded when a task matches: ~2.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~3.4k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from forcedotcom/sf-skills at commit e5164d9, republished under its Apache-2.0 licence (© forcedotcom). 658 words, ~2,340 tokens.

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

name: data360-schema-get
description: Retrieve Data Lake Object (DLO) and Data Model Object (DMO) schema information from Salesforce Data Cloud using REST APIs. Use this skill when you need to inspect DLO or DMO field definitions, data types, or metadata. Takes org alias and optional DLO/DMO name as parameters.
metadata.version: 1.0
metadata.domains: Data 360

data360-schema-get Skill

Overview

This skill retrieves Data Lake Object (DLO) and Data Model Object (DMO) schema information from Salesforce Data Cloud using the SSOT REST API. It can list all DLOs or DMOs in an org, or retrieve detailed schema for a specific DLO or DMO.

When to Use

User wants to see all DLOs or DMOs in a Data Cloud org
User needs field schema for a specific DLO or DMO
User is exploring Data Cloud data structures
User needs to understand DLO or DMO field types and metadata

Prerequisites

SF CLI installed and authenticated to target org
Org has Data Cloud enabled
User has appropriate Data Cloud permissions

Skill Execution

Parameters

org_alias (required): The SF CLI org alias (e.g., 'afvibe', 'myorg')
dlo_name (optional): Specific DLO developer name (e.g., 'Employee__dll')
dmo_name (optional): Specific DMO developer name (e.g., 'Individual__dlm')

Step 1: Discover Connected Org

First, run sf org list to find out which org is connected and extract the alias to use for all subsequent calls:

bash

sf org list

Example output:

text

┌────┬───────┬──────────────────────────┬────────────────────┬───────────┐
│    │ Alias │ Username                 │ Org Id             │ Status    │
├────┼───────┼──────────────────────────┼────────────────────┼───────────┤
│    │ myorg │ chandresh@afvidedemo.org │ 00DKZ00000b80NT2AY │ Connected │
└────┴───────┴──────────────────────────┴────────────────────┴───────────┘

Extract the Alias value (e.g., myorg) from the output and use it as the <org_alias> for all subsequent calls. Use --all to see expired and deleted scratch orgs as well.

Step 2: Validate SF CLI Authentication

Before making API calls, verify the org is connected:

bash

sf org display --target-org <org_alias> --json

If not connected, inform user to run:

bash

sf org login web --alias <org_alias>

Step 3a: Execute DLO Schema Script

The Python scripts are bundled with this skill in the scripts/ subdirectory.

To list all DLOs:

bash

python3 ./scripts/get_dlo_schema.py <org_alias>

To get specific DLO schema:

bash

python3 ./scripts/get_dlo_schema.py <org_alias> <dlo_name>

Step 3b: Execute DMO Schema Script

To list all DMOs:

bash

python3 ./scripts/get_dmo_schema.py <org_alias>

To get specific DMO schema:

bash

python3 ./scripts/get_dmo_schema.py <org_alias> <dmo_name>

Step 4: Present Results

Parse and present the results in a user-friendly format:

For DLO List:

Show DLO name, label, category, and ID
Indicate total count
Highlight DLOs with data (totalRecords > 0)

For DLO Schema:

Show basic info (name, label, category, status)
List all fields with:
- Field name
- Data type
- Primary key indicator
- Nullable status
Highlight custom fields (exclude system fields like DataSource__c, cdp_sys_*)
Show record count if available

For DMO List:

Show DMO name, label, category, and ID
Indicate total count

For DMO Schema:

Show basic info (name, label, category, description)
List all fields with:
- Field name
- Data type
- Primary key indicator
- Nullable status
Show dataspace information if available

Step 5: Offer Next Steps

After displaying results, suggest relevant follow-up actions:

Query data from the DLO
Create calculated insights
Build segments
Set up data streams
Create DMO mappings

Show full SKILL.md (254 more words)Show less

API Endpoints Used

List All DLOs

text

GET /services/data/v64.0/ssot/data-lake-objects

Response structure:

json

{
  "dataLakeObjects": [
    {
      "name": "Employee__dll",
      "label": "Employee",
      "category": "Profile",
      "id": "1dlXXXXXXXXXXXXXXX",
      "status": "ACTIVE",
      "totalRecords": 12,
      "fields": [...]
    }
  ],
  "totalSize": 5
}

Get DLO Schema

text

GET /services/data/v64.0/ssot/data-lake-objects/{dlo_name}

Response structure (same as individual object in list response, but wrapped in paginated format).

List All DMOs

text

GET /services/data/v64.0/ssot/data-model-objects

Response structure:

json

{
  "dataModelObjects": [
    {
      "name": "Individual__dlm",
      "label": "Individual",
      "category": "Profile",
      "id": "0dmXXXXXXXXXXXXXXX",
      "fields": [...]
    }
  ],
  "totalSize": 10
}

Get DMO Schema

text

GET /services/data/v64.0/ssot/data-model-objects/{dmo_name}

Response structure (same as individual object in list response, but wrapped in paginated format).

Error Handling

Common Issues:

Org not connected
- Message: "Org not connected"
- Solution: Ask user to authenticate via SF CLI
DLO not found
- Message: "DLO 'XYZ__dll' not found"
- Solution: List all DLOs first to verify name
DMO not found
- Message: "DMO 'XYZ__dlm' not found"
- Solution: List all DMOs first to verify name
Permission issues
- Message: HTTP 403 errors
- Solution: Verify user has Data Cloud permissions
API version mismatch
- Current: v64.0
- Solution: Script can be updated for newer API versions

Example Usage

Example 1: List all DLOs

text

User: "Show me all DLOs in afvibe org"

Response:
1. Run sf org list to discover connected org alias
2. Authenticate to afvibe
3. Run: python3 ./scripts/get_dlo_schema.py afvibe
4. Display formatted list of DLOs

Example 2: Get specific DLO schema

text

User: "Get the schema for Employee__dll in afvibe"

Response:
1. Run sf org list to discover connected org alias
2. Authenticate to afvibe
3. Run: python3 ./scripts/get_dlo_schema.py afvibe Employee__dll
4. Display field schema with types and metadata

Example 3: Explore DLOs then get schema

text

User: "What DLOs exist in myorg and show me the schema for the Employee one"

Response:
1. Run sf org list to discover connected org alias
2. List all DLOs in myorg
3. Identify Employee__dll
4. Get detailed schema for Employee__dll
5. Present both results

Example 4: List all DMOs

text

User: "Show me all DMOs in afvibe org"

Response:
1. Run sf org list to discover connected org alias
2. Authenticate to afvibe
3. Run: python3 ./scripts/get_dmo_schema.py afvibe
4. Display formatted list of DMOs

Example 5: Get specific DMO schema

text

User: "Get the schema for Individual__dlm in afvibe"

Response:
1. Run sf org list to discover connected org alias
2. Authenticate to afvibe
3. Run: python3 ./scripts/get_dmo_schema.py afvibe Individual__dlm
4. Display field schema with types and metadata

Example 6: Explore DMOs then get schema

text

User: "What DMOs exist in myorg and show me the schema for the Individual one"

Response:
1. Run sf org list to discover connected org alias
2. List all DMOs in myorg
3. Identify Individual__dlm
4. Get detailed schema for Individual__dlm
5. Present both results

Output Format

DLO List Output

text

Found 5 DLOs in org 'afvibe':

1. DataCustomCodeLogs__dll
   Label: DataCustomCodeLogs
   Category: Engagement
   Records: 233

2. Employee__dll
   Label: Employee
   Category: Profile
   Records: 12

[...]

DLO Schema Output

yaml

DLO: Employee__dll
Label: Employee
Category: Profile
Status: ACTIVE
Records: 12

Custom Fields:
  • id__c (Text) - Primary Key
  • name__c (Text)
  • position__c (Text)
  • manager_id__c (Number)

System Fields:
  • DataSource__c (Text)
  • InternalOrganization__c (Text)
  • cdp_sys_SourceVersion__c (Text)

Next steps:
- Query data: SELECT * FROM Employee__dll LIMIT 10
- Create segment based on position field
- Set up data stream for real-time updates

DMO List Output

text

Found 10 DMOs in org 'afvibe':

1. Individual__dlm
   Label: Individual
   Category: Profile

2. ContactPointEmail__dlm
   Label: Contact Point Email
   Category: Profile

[...]

DMO Schema Output

yaml

DMO: Individual__dlm
Label: Individual
Category: Profile
Description: Represents an individual person

Fields:
  • Id__c (Text) - Primary Key
  • FirstName__c (Text)
  • LastName__c (Text)
  • BirthDate__c (DateTime)

Next steps:
- Query data: SELECT * FROM Individual__dlm LIMIT 10
- View DLO mappings to this DMO
- Create calculated insights

Notes

DLO names always end with __dll suffix
DMO names always end with __dlm suffix
Field names always end with __c suffix
System fields (DataSource__c, KQ_*, cdp_sys_*) are automatically added
Primary key fields are required for DLO and DMO queries
API supports pagination (limit/offset) for large result sets

datakit_workflow: For DMO mapping operations
datakit_validation: For validating datakit configurations
Use this skill before creating DMO mappings to understand source DLO structure

Files

SKILL.md and 3 other files (scripts, references) in skills/data360-schema-get of forcedotcom/sf-skills.

SKILL.md
references/README.md
scripts/get_dlo_schema.py
scripts/get_dmo_schema.py

Open the folder on GitHubat commit e5164d9

Compare with similar skills

Data360 Schema Get 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.

Data360 Schema Get compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Data360 Schema Get this skillforcedotcom/sf-skills	1.1k	—	~2.3k	Automated safety check: Pass	Apache-2.0	today
Sf Connected AppsJaganpro/sf-skills	424	—	~1.9k	Automated safety check: Notes	MIT	5 mo ago
Sf IntegrationJaganpro/sf-skills	424	—	~1.5k	Automated safety check: Pass	MIT	5 mo ago
Implementing Zero Trust For SaaS Applicationsmukul975/Anthropic-Cybersecurity-Skills	34k	—	~2.9k	Automated safety check: Pass	Apache-2.0	1 mo ago
Salesforce Webhooks Eventsjeremylongshore/tons-of-skills-marketplace	2.8k	—	~1.1k	Automated safety check: Pass	MIT	today
Databricks Lakeflow Connectdatabricks/databricks-agent-skills	345	—	~3.8k	Automated safety check: Pass	Custom licence	today

Similar skills

Sf Connected Apps
Jaganpro/sf-skills
Salesforce Connected Apps and OAuth configuration with 120-point scoring.
424 GitHub stars~1.9k tokensUpdated 5 mo ago
Backend & APIsAuto-check: notes
Sf Integration
Jaganpro/sf-skills
Salesforce integration architecture with 120-point scoring. An agent skill from Jaganpro/sf-skills.
424 GitHub stars~1.5k tokensUpdated 5 mo ago
Backend & APIsAuto-check passed
Implementing Zero Trust For SaaS Applications
mukul975/Anthropic-Cybersecurity-Skills
Secures SaaS apps (Microsoft 365, Google Workspace, Salesforce, Slack) via CASB/SSPM deployment, conditional access policies, OAuth app governance, and session-level DLP controls enforcing identity…
34k GitHub stars~2.9k tokensUpdated 1 mo ago
Backend & APIsAuto-check passed
Salesforce Webhooks Events
jeremylongshore/tons-of-skills-marketplace
Select and govern Salesforce change delivery across Pub/Sub API, Change Data Capture, Platform Events, event relay, Streaming API, Outbound Messages, or polling.
2.8k GitHub stars~1.1k tokensUpdated today
Backend & APIsAuto-check passed
Databricks Lakeflow Connect
databricks/databricks-agent-skills
Official
Build managed ingestion pipelines into Databricks using Lakeflow Connect.
345 GitHub stars~3.8k tokensUpdated today
Sales & SupportAuto-check passed
Agentforce Generate
SalesforceAIResearch/agentforce-adlc
Build, modify, audit, repair, optimize, debug, and deploy agents with Agentforce Agent Script.
114 GitHub starsUsed in 1 repo~7.4k tokens
Agent WorkflowsAuto-check passed

Questions about Data360 Schema Get

What does Data360 Schema Get do?

Retrieve Data Lake Object (DLO) and Data Model Object (DMO) schema information from Salesforce Data Cloud using REST APIs. Data360 Schema Get is an agent skill from forcedotcom/sf-skills. Retrieve Data Lake Object (DLO) and Data Model Object (DMO) schema information from Salesforce Data Cloud using REST APIs.

When should I use Data360 Schema Get?

Data360 Schema Get fits situations like: you need to inspect DLO; DMO field definitions.

How do I install Data360 Schema Get in Claude Code?

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

How do I install Data360 Schema Get in Codex?

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

Can I use Data360 Schema Get 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 forcedotcom/sf-skills --skill data360-schema-get -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/data360-schema-get, .gemini/skills/data360-schema-get, .github/skills/data360-schema-get and .opencode/skills/data360-schema-get in your project.

What does Data360 Schema Get need to run?

Going by SKILL.md and its folder, Data360 Schema Get needs Python for the scripts in its folder and the command-line tools its instructions call (sf and python3). Our summary lists: Python 3.

Does Data360 Schema Get 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 Data360 Schema Get 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Data360 Schema Get use?

Data360 Schema Get is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Data360 Schema Get use?

About 2.3k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.

What are the alternatives to Data360 Schema Get?

Skills that share tags, products or a category with Data360 Schema Get: Sf Connected Apps (Jaganpro/sf-skills, 424 stars), Sf Integration (Jaganpro/sf-skills, 424 stars), Implementing Zero Trust For SaaS Applications (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Salesforce Webhooks Events (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Data360 Schema Get?

forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,060 GitHub stars. The repository holds 251 skills in this directory. The repository was last updated on October 7, 2026.

Source: forcedotcom/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 Data360 Schema Get

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

Context cost

Safety

SKILL.md

data360-schema-get Skill

Overview

When to Use

Prerequisites

Skill Execution

Parameters

Step 1: Discover Connected Org

Step 2: Validate SF CLI Authentication

Step 3a: Execute DLO Schema Script

Step 3b: Execute DMO Schema Script

Step 4: Present Results

Step 5: Offer Next Steps

API Endpoints Used

List All DLOs

Get DLO Schema

List All DMOs

Get DMO Schema

Error Handling

Example Usage

Output Format

DLO List Output

DLO Schema Output

DMO List Output

DMO Schema Output

Notes

Related Skills

Files

Compare with similar skills

Similar skills

More from forcedotcom/sf-skills

Related

Questions about Data360 Schema Get