data360-connect

Name: data360-connect
Author: forcedotcom

744stars272forks

How to install data360-connect?

forcedotcom/sf-skills/data360-connect

$npx -y skills add forcedotcom/sf-skills --skill data360-connect

Installs into the current project.

Summary

Salesforce Data Cloud Connect phase. Use this skill when the user manages Data Cloud connections, connectors, or sets up a new source system. TRIGGER when: user manages Data Cloud connections, connectors, connector metadata, tests a connection, browses source objects or databases

Files · 1

View on GitHub

SKILL.md

1	# data360-connect: Data Cloud Connect Phase
2
3	Use this skill when the user needs source connection work: connector discovery, connection metadata, connection testing, source-object browsing, connector schema inspection, or connector-specific setup payloads for external sources.
4
5	## When This Skill Owns the Task
6
7	Use `data360-connect` when the work involves:
8	- `sf data360 connection *`
9	- connector catalog inspection
10	- connection creation, update, test, or delete
11	- browsing source objects, fields, databases, or schemas
12	- identifying connector types already in use
13	- preparing connector definitions for Snowflake, SharePoint Unstructured, or Ingestion API sources
14
15	Delegate elsewhere when the user is:
16	- creating data streams or DLOs → [data360-prepare](../data360-prepare/SKILL.md)
17	- creating DMOs, mappings, IR rulesets, or data graphs → [data360-harmonize](../data360-harmonize/SKILL.md)
18	- writing Data Cloud SQL or search-index workflows → [data360-query](../data360-query/SKILL.md)
19
20	---
21
22	## Required Context to Gather First
23
24	Ask for or infer:
25	- target org alias
26	- connector type or source system
27	- whether the user wants inspection only or live mutation
28	- connection name or ID if one already exists
29	- whether credentials are already configured outside the CLI
30	- whether the user also expects stream creation right after connection setup
31	- whether the source is a database, an unstructured document source, or an Ingestion API feed
32
33	---
34
35	## Core Operating Rules
36
37	- Verify the plugin runtime first; see [../data360-orchestrate/references/plugin-setup.md](../data360-orchestrate/references/plugin-setup.md).
38	- Run the shared readiness classifier before mutating connections: `node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase connect --json`.
39	- Prefer read-only discovery before connection creation.
40	- Suppress linked-plugin warning noise with `2>/dev/null` for standard usage.
41	- Remember that `connection list` requires `--connector-type`.
42	- For `connection test`, pass `--connector-type` when resolving a non-Salesforce connection by name.
43	- Discover existing connector types from streams first when the org is unfamiliar.
44	- Use curated example payloads before inventing connector-specific credentials or parameters.
45	- For connector types outside the curated examples, inspect a known-good UI-created connection via REST before building JSON.
46	- Do not promise API-based stream creation for every connector type just because connection creation succeeds.
47
48	---
49
50	## Recommended Workflow
51
52	### 1. Classify readiness for connect work
53	```bash
54	node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase connect --json
55	```
56
57	### 2. Discover connector types
58	```bash
59	sf data360 connection connector-list -o <org> 2>/dev/null
60	sf data360 data-stream list -o <org> 2>/dev/null
61	```
62
63	### 3. Inspect connections by type
64	```bash
65	sf data360 connection list -o <org> --connector-type SalesforceDotCom 2>/dev/null
66	sf data360 connection list -o <org> --connector-type REDSHIFT 2>/dev/null
67	sf data360 connection list -o <org> --connector-type SNOWFLAKE 2>/dev/null
68	```
69
70	### 4. Inspect a specific connection or uploaded schema
71	```bash
72	sf data360 connection get -o <org> --name <connection> 2>/dev/null
73	sf data360 connection objects -o <org> --name <connection> 2>/dev/null
74	sf data360 connection fields -o <org> --name <connection> 2>/dev/null
75	sf data360 connection schema-get -o <org> --name <connection-id> 2>/dev/null
76	```
77
78	### 5. Test or create only after discovery
79	```bash
80	sf data360 connection test -o <org> --name <connection> --connector-type <type> 2>/dev/null
81	sf data360 connection create -o <org> -f connection.json 2>/dev/null
82	```
83
84	### 6. Start from curated example payloads for external connectors
85	Use the phase-owned examples before inventing a payload from scratch:
86	- `examples/connections/heroku-postgres.json`
87	- `examples/connections/redshift.json`
88	- `examples/connections/sharepoint-unstructured.json`
89	- `examples/connections/snowflake-connection.json`
90	- `examples/connections/ingest-api-connection.json`
91	- `examples/connections/ingest-api-schema.json`
92
93	Typical Ingestion API setup flow:
94	```bash
95	sf data360 connection create -o <org> -f examples/connections/ingest-api-connection.json 2>/dev/null
96	sf data360 connection schema-upsert -o <org> --name <connector-id> -f examples/conne

People who liked this also viewed

6 picks

Type

data360-connect

744stars272forks

View on GitHub

How to install data360-connect?

forcedotcom/sf-skills/data360-connect

$npx -y skills add forcedotcom/sf-skills --skill data360-connect

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# data360-connect: Data Cloud Connect Phase
2
3	Use this skill when the user needs source connection work: connector discovery, connection metadata, connection testing, source-object browsing, connector schema inspection, or connector-specific setup payloads for external sources.
4
5	## When This Skill Owns the Task
6
7	Use `data360-connect` when the work involves:
8	- `sf data360 connection *`
9	- connector catalog inspection
10	- connection creation, update, test, or delete
11	- browsing source objects, fields, databases, or schemas
12	- identifying connector types already in use
13	- preparing connector definitions for Snowflake, SharePoint Unstructured, or Ingestion API sources
14
15	Delegate elsewhere when the user is:
16	- creating data streams or DLOs → [data360-prepare](../data360-prepare/SKILL.md)
17	- creating DMOs, mappings, IR rulesets, or data graphs → [data360-harmonize](../data360-harmonize/SKILL.md)
18	- writing Data Cloud SQL or search-index workflows → [data360-query](../data360-query/SKILL.md)
19
20	---
21
22	## Required Context to Gather First
23
24	Ask for or infer:
25	- target org alias
26	- connector type or source system
27	- whether the user wants inspection only or live mutation
28	- connection name or ID if one already exists
29	- whether credentials are already configured outside the CLI
30	- whether the user also expects stream creation right after connection setup
31	- whether the source is a database, an unstructured document source, or an Ingestion API feed
32
33	---
34
35	## Core Operating Rules
36
37	- Verify the plugin runtime first; see [../data360-orchestrate/references/plugin-setup.md](../data360-orchestrate/references/plugin-setup.md).
38	- Run the shared readiness classifier before mutating connections: `node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase connect --json`.
39	- Prefer read-only discovery before connection creation.
40	- Suppress linked-plugin warning noise with `2>/dev/null` for standard usage.
41	- Remember that `connection list` requires `--connector-type`.
42	- For `connection test`, pass `--connector-type` when resolving a non-Salesforce connection by name.
43	- Discover existing connector types from streams first when the org is unfamiliar.
44	- Use curated example payloads before inventing connector-specific credentials or parameters.
45	- For connector types outside the curated examples, inspect a known-good UI-created connection via REST before building JSON.
46	- Do not promise API-based stream creation for every connector type just because connection creation succeeds.
47
48	---
49
50	## Recommended Workflow
51
52	### 1. Classify readiness for connect work
53	```bash
54	node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase connect --json
55	```
56
57	### 2. Discover connector types
58	```bash
59	sf data360 connection connector-list -o <org> 2>/dev/null
60	sf data360 data-stream list -o <org> 2>/dev/null
61	```
62
63	### 3. Inspect connections by type
64	```bash
65	sf data360 connection list -o <org> --connector-type SalesforceDotCom 2>/dev/null
66	sf data360 connection list -o <org> --connector-type REDSHIFT 2>/dev/null
67	sf data360 connection list -o <org> --connector-type SNOWFLAKE 2>/dev/null
68	```
69
70	### 4. Inspect a specific connection or uploaded schema
71	```bash
72	sf data360 connection get -o <org> --name <connection> 2>/dev/null
73	sf data360 connection objects -o <org> --name <connection> 2>/dev/null
74	sf data360 connection fields -o <org> --name <connection> 2>/dev/null
75	sf data360 connection schema-get -o <org> --name <connection-id> 2>/dev/null
76	```
77
78	### 5. Test or create only after discovery
79	```bash
80	sf data360 connection test -o <org> --name <connection> --connector-type <type> 2>/dev/null
81	sf data360 connection create -o <org> -f connection.json 2>/dev/null
82	```
83
84	### 6. Start from curated example payloads for external connectors
85	Use the phase-owned examples before inventing a payload from scratch:
86	- `examples/connections/heroku-postgres.json`
87	- `examples/connections/redshift.json`
88	- `examples/connections/sharepoint-unstructured.json`
89	- `examples/connections/snowflake-connection.json`
90	- `examples/connections/ingest-api-connection.json`
91	- `examples/connections/ingest-api-schema.json`
92
93	Typical Ingestion API setup flow:
94	```bash
95	sf data360 connection create -o <org> -f examples/connections/ingest-api-connection.json 2>/dev/null
96	sf data360 connection schema-upsert -o <org> --name <connector-id> -f examples/conne

People who liked this also viewed

6 picks

Type