integration-connectivity-generate

Name: integration-connectivity-generate
Author: forcedotcom

744stars272forks

How to install integration-connectivity-generate?

forcedotcom/sf-skills/integration-connectivity-generate

$npx -y skills add forcedotcom/sf-skills --skill integration-connectivity-generate

Installs into the current project.

Summary

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials

Files · 1

View on GitHub

SKILL.md

1	# integration-connectivity-generate: Salesforce Integration Patterns Expert
2
3	Use this skill when the user needs integration architecture and runtime plumbing: Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, CDC, and event-driven integration design.
4
5	## When This Skill Owns the Task
6
7	Use `integration-connectivity-generate` when the work involves:
8	- `.namedCredential-meta.xml` or External Credential metadata
9	- outbound REST/SOAP callouts
10	- External Service registration from OpenAPI specs
11	- Platform Events, CDC, and event-driven architecture
12	- choosing sync vs async integration patterns
13
14	Delegate elsewhere when the user is:
15	- configuring the OAuth app itself → [integration-connectivity-connected-app-configure](../integration-connectivity-connected-app-configure/SKILL.md)
16	- writing Apex-only business logic → [platform-apex-generate](../platform-apex-generate/SKILL.md)
17	- deploying metadata → [platform-metadata-deploy](../platform-metadata-deploy/SKILL.md)
18	- importing/exporting data → [platform-data-manage](../platform-data-manage/SKILL.md)
19
20	---
21
22	## Required Context to Gather First
23
24	Ask for or infer:
25	- integration style: outbound callout, inbound event, External Service, CDC, platform event
26	- auth method
27	- sync vs async requirement
28	- system endpoint / spec details
29	- rate limits, retry expectations, and failure tolerance
30	- whether this is net-new design or repair of an existing integration
31
32	---
33
34	## Recommended Workflow
35
36	### 1. Choose the integration pattern
37	\| Need \| Default pattern \|
38	\|---\|---\|
39	\| authenticated outbound API call \| Named Credential / External Credential + Apex or Flow \|
40	\| spec-driven API client \| External Service \|
41	\| trigger-originated callout \| async callout pattern \|
42	\| decoupled event publishing \| Platform Events \|
43	\| change-stream consumption \| CDC \|
44
45	### 2. Choose the auth model
46	Prefer secure runtime-managed auth:
47	- Named Credentials / External Credentials
48	- OAuth or JWT via the right credential model
49	- no hardcoded secrets in code
50
51	### 3. Generate from the right templates
52	Use the provided assets under:
53	- `assets/named-credentials/`
54	- `assets/external-credentials/`
55	- `assets/external-services/`
56	- `assets/callouts/`
57	- `assets/platform-events/`
58	- `assets/cdc/`
59	- `assets/soap/`
60
61	### 4. Validate operational safety
62	Check:
63	- timeout and retry handling
64	- async strategy for trigger-originated work
65	- logging / observability
66	- event retention and subscriber implications
67
68	### 5. Hand off deployment or implementation details
69	Use:
70	- [platform-metadata-deploy](../platform-metadata-deploy/SKILL.md) for deployment
71	- [platform-apex-generate](../platform-apex-generate/SKILL.md) for deeper service / retry code
72	- [automation-flow-generate](../automation-flow-generate/SKILL.md) for declarative HTTP callout orchestration
73
74	---
75
76	## High-Signal Rules
77
78	- never hardcode credentials
79	- do not do synchronous callouts from triggers
80	- define timeout behavior explicitly
81	- plan retries for transient failures
82	- use middleware / event-driven patterns when outbound volume is high
83	- prefer External Credentials architecture for new development when supported
84
85	Common anti-patterns:
86	- sync trigger callouts
87	- no retry or dead-letter strategy
88	- no request/response logging
89	- mixing auth setup responsibilities with runtime integration design
90
91	---
92
93	## Output Format
94
95	When finishing, report in this order:
96	1. Integration pattern chosen
97	2. Auth model chosen
98	3. Files created or updated
99	4. Operational safeguards
100	5. Deployment / testing next step
101
102	Suggested shape:
103
104	```text
105	Integration: <summary>
106	Pattern: <named credential / external service / event / cdc / callout>
107	Files: <paths>
108	Safety: <timeouts, retries, async, logging>
109	Next step: <deploy, register, test, or implement>
110	```
111
112	---
113
114	## Cross-Skill Integration
115
116	\| Need \| Delegate to \| Reason \|
117	\|---\|---\|---\|
118	\| OAuth app setup \| [integration-connectivity-connected-app-configure](../integration-connectivity-connected-app-configure/SKILL.md) \| consumer key / cert / app config \|
119	\| advanced callout service code \| [platform-apex-generate](../platform-apex-generate/SKILL.md) \| Apex implementation \|
120	\| declarative HTTP ca

People who liked this also viewed

6 picks

Type

integration-connectivity-generate

744stars272forks

View on GitHub

How to install integration-connectivity-generate?

forcedotcom/sf-skills/integration-connectivity-generate

$npx -y skills add forcedotcom/sf-skills --skill integration-connectivity-generate

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# integration-connectivity-generate: Salesforce Integration Patterns Expert
2
3	Use this skill when the user needs integration architecture and runtime plumbing: Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, CDC, and event-driven integration design.
4
5	## When This Skill Owns the Task
6
7	Use `integration-connectivity-generate` when the work involves:
8	- `.namedCredential-meta.xml` or External Credential metadata
9	- outbound REST/SOAP callouts
10	- External Service registration from OpenAPI specs
11	- Platform Events, CDC, and event-driven architecture
12	- choosing sync vs async integration patterns
13
14	Delegate elsewhere when the user is:
15	- configuring the OAuth app itself → [integration-connectivity-connected-app-configure](../integration-connectivity-connected-app-configure/SKILL.md)
16	- writing Apex-only business logic → [platform-apex-generate](../platform-apex-generate/SKILL.md)
17	- deploying metadata → [platform-metadata-deploy](../platform-metadata-deploy/SKILL.md)
18	- importing/exporting data → [platform-data-manage](../platform-data-manage/SKILL.md)
19
20	---
21
22	## Required Context to Gather First
23
24	Ask for or infer:
25	- integration style: outbound callout, inbound event, External Service, CDC, platform event
26	- auth method
27	- sync vs async requirement
28	- system endpoint / spec details
29	- rate limits, retry expectations, and failure tolerance
30	- whether this is net-new design or repair of an existing integration
31
32	---
33
34	## Recommended Workflow
35
36	### 1. Choose the integration pattern
37	\| Need \| Default pattern \|
38	\|---\|---\|
39	\| authenticated outbound API call \| Named Credential / External Credential + Apex or Flow \|
40	\| spec-driven API client \| External Service \|
41	\| trigger-originated callout \| async callout pattern \|
42	\| decoupled event publishing \| Platform Events \|
43	\| change-stream consumption \| CDC \|
44
45	### 2. Choose the auth model
46	Prefer secure runtime-managed auth:
47	- Named Credentials / External Credentials
48	- OAuth or JWT via the right credential model
49	- no hardcoded secrets in code
50
51	### 3. Generate from the right templates
52	Use the provided assets under:
53	- `assets/named-credentials/`
54	- `assets/external-credentials/`
55	- `assets/external-services/`
56	- `assets/callouts/`
57	- `assets/platform-events/`
58	- `assets/cdc/`
59	- `assets/soap/`
60
61	### 4. Validate operational safety
62	Check:
63	- timeout and retry handling
64	- async strategy for trigger-originated work
65	- logging / observability
66	- event retention and subscriber implications
67
68	### 5. Hand off deployment or implementation details
69	Use:
70	- [platform-metadata-deploy](../platform-metadata-deploy/SKILL.md) for deployment
71	- [platform-apex-generate](../platform-apex-generate/SKILL.md) for deeper service / retry code
72	- [automation-flow-generate](../automation-flow-generate/SKILL.md) for declarative HTTP callout orchestration
73
74	---
75
76	## High-Signal Rules
77
78	- never hardcode credentials
79	- do not do synchronous callouts from triggers
80	- define timeout behavior explicitly
81	- plan retries for transient failures
82	- use middleware / event-driven patterns when outbound volume is high
83	- prefer External Credentials architecture for new development when supported
84
85	Common anti-patterns:
86	- sync trigger callouts
87	- no retry or dead-letter strategy
88	- no request/response logging
89	- mixing auth setup responsibilities with runtime integration design
90
91	---
92
93	## Output Format
94
95	When finishing, report in this order:
96	1. Integration pattern chosen
97	2. Auth model chosen
98	3. Files created or updated
99	4. Operational safeguards
100	5. Deployment / testing next step
101
102	Suggested shape:
103
104	```text
105	Integration: <summary>
106	Pattern: <named credential / external service / event / cdc / callout>
107	Files: <paths>
108	Safety: <timeouts, retries, async, logging>
109	Next step: <deploy, register, test, or implement>
110	```
111
112	---
113
114	## Cross-Skill Integration
115
116	\| Need \| Delegate to \| Reason \|
117	\|---\|---\|---\|
118	\| OAuth app setup \| [integration-connectivity-connected-app-configure](../integration-connectivity-connected-app-configure/SKILL.md) \| consumer key / cert / app config \|
119	\| advanced callout service code \| [platform-apex-generate](../platform-apex-generate/SKILL.md) \| Apex implementation \|
120	\| declarative HTTP ca

People who liked this also viewed

6 picks

Type