integration-connectivity-generate
/integration-connectivity-generate
Planuje integracje Salesforce: Named Credentials, External Credentials, External Services, wywołania REST i SOAP, Platform Events i Change Data Capture, z oceną w skali 120 punktów.
- Autor
- forcedotcom ↗
- Repozytorium
- sf-skills ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 23.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 43
- Skrypty
- 5
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 23.10.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 5 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/configure-named-credential.sh, scripts/set-api-credential.sh, scripts/suggest_credential_setup.py, scripts/templates/setup-credentials-with-csp.sh, scripts/validate_integration.py
Co robi i kiedy
Planuje integracje Salesforce: Named Credentials, External Credentials, External Services, wywołania REST i SOAP, Platform Events i Change Data Capture, z oceną w skali 120 punktów.
Oryginalny opis (EN)
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, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use integration-connectivity-connected-app-configure), Apex-only logic (use platform-apex-generate), data import/export (use platform-data-manage), or CDC channel-m
Jak działa
- When This Skill Owns the Task
- Required Context to Gather First
- Recommended Workflow
- High-Signal Rules
- Output Format
- Cross-Skill Integration
- Reference Map
- Output Expectations
- Score Guide
- Pre-Delivery Checklist
Podgląd SKILL.md
---
name: integration-connectivity-generate
description: "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, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use integration-connectivity-connected-app-configure), Apex-only logic (use platform-apex-generate), data import/export (use platform-data-manage), or CDC channel-membership metadata such as PlatformEventChannel, PlatformEventChannelMember, or EnrichedField (use integration-eventing-cdc-configure)."
metadata:
version: "1.1"
domains: ["Integration"]
minApiVersion: "61.0"
relatedSkills:
- "agentforce-generate"
- "automation-flow-generate"
- "integration-connectivity-connected-app-configure"
- "integration-eventing-cdc-configure"
- "platform-apex-generate"
- "platform-data-manage"
- "platform-metadata-deploy"
cliTools:
- tool: ["jq"]
semver: ">=1.6.0"
- tool: ["npm"]
semver: ">=9.0.0"
- tool: ["python3"]
semver: ">=3.10.0"
- tool: ["sf"]
semver: ">=2.0.0"
---
# integration-connectivity-generate: Salesforce Integration Patterns Expert
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.
## When This Skill Owns the Task
Use `integration-connectivity-generate` when the work involves:
- `.namedCredential-meta.xml` or External Credential metadata
- outbound REST/SOAP callouts
- External Service registration from OpenAPI specs
- Platform Events, CDC, and event-driven architecture
- choosing sync vs async integration patterns
Delegate elsewhere when the user is:
- configuring the OAuth app itself → [integration-connectivity-connected-app-configure](../integration-connectivity-connected-app-configure/SKILL.md)
- writing Apex-only business logic → the `platform-apex-generate` skill
- deploying metadata → the `platform-metadata-deploy` skill
- importing/exporting data → the `platform-data-manage` skill
---
## Required Context to Gather First
Ask for or infer:
- integration style: outbound callout, inbound event, External Service, CDC, platform event
- auth method
- sync vs async requirement
- system endpoint / spec details
- rate limits, retry expectations, and failure tolerance
- whether this is net-new design or repair of an existing integration
---
## Recommended Workflow
### 1. Choose the integration pattern
| Need | Default pattern |
|---|---|
| authenticated outbound API call | Named Credential / External Credential + Apex or Flow |
| spec-driven API client | External Service |
| trigger-originated callout | async callout pattern |
| decoupled event publishing | Platform Events |
| change-stream consumption | CDC |
### 2. Choose the auth model
Prefer secure runtime-managed auth:
- Named Credentials / External Credentials
- OAuth or JWT via the right credential model
- no hardcoded secrets in code
### 3. Generate from the right templates
Use the provided assets under:
- `assets/named-credentials/`
- `assets/external-credentials/`
- `assets/external-services/`
- `assets/callouts/`
- `assets/platform-events/`
- `assets/cdc/`
- `assets/soap/`
### 4. Validate operational safety
Check:
- timeout and retry handling
- async strategy for trigger-originated work
- logging / observability
- event retention and subscriber implications
### 5. Hand off deployment or implementation details
Use:
- the `platform-metadata-deploy` skill for deployment
- the `platform-apex-generate` skill for deeper service / retry code
- the `automation-flow-generate` skill for declarative HTTP callout orchestration
---
## High-Signal Rules
- never hardcode credentials
- do not do synchronous callouts from triggers
- define timeout behavior explicitly
- plan retries for transient failures
- use middleware / event-driven patterns when outbound volume is high
- prefer External Credentials architecture for new development when supported
Common anti-patterns:
- sync trigger callouts
- no retry or dead-letter strategy
- no request/response logging
- mixing auth setup responsibilities with runtime integration design
---
## Output Format
When finishing, report in this order:
1. **Integration pattern chosen**
2. **Auth model chosen**
3. **Files created or updated**
4. **Operational safeguards**
5. **Deployment / testing next step**
Suggested shape:
```text
Integration: <summary>
Pattern: <named credential / external service / event / cdc / callout>
Files: <paths>
Safety: <timeouts, retries, async, logging>
Next step: <deploy, register, test, or implement>
```
---
## Cross-Skill Integration
| Need | Delegate to | Reason |
|---|---|---|
| OAuth app setup | [integration-connectivity-connected-app-configure](../integration-connectivity-connected-app-configure/SKILL.md) | consumer key / cert / app config |
| advanced callout service code | `platform-apex-generate` skill | Apex implementation |
| declarative HTTP callout / Flow wrapper | `automation-flow-generate` skill | Flow orchestration |
| deploy integration metadata | `platform-metadata-deploy` skill | validation and rollout |
| use integration from Agentforce | `agentforce-generate` skill | agent action composition |
---
## Reference Map
### Start here
- [references/named-credentials-guide.md](references/named-credentials-guide.md)
- [references/external-services-guide.md](references/external-services-guide.md)
- [references/callout-patterns.md](references/callout-patterns.md)
- [references/rest-callout-patterns.md](references/rest-callout-patterns.md)
- [references/security-best-practices.md](references/security-best-practices.md)
### Event-driven / platform patterns
- [references/event-patterns.md](references/event-patterns.md)
- [references/platform-events-guide.md](references/platform-events-guide.md)
- [references/cdc-guide.md](references/cdc-guide.md)
- [references/event-driven-architecture-guide.md](references/event-driven-architecture-guide.md)
- [references/messaging-api-v2.md](references/messaging-api-v2.md)
### CLI / automation / scoring
- [references/cli-reference.md](references/cli-reference.md)
- [references/named-credentials-automation.md](references/named-credentials-automation.md)
- [references/scoring-rubric.md](references/scoring-rubric.md)
- [scripts/README.md](scripts/README.md) — automation scripts overview (configure-named-credential.sh, set-api-credential.sh)
### Asset templates
- `assets/named-credentials/` — Named Credential XML templates (OAuth, JWT, Certificate, Custom auth)
- `assets/external-credentials/` — External Credential XML templates (OAuth, JWT)
- `assets/external-services/` — External Service registration template and operations guide
- `assets/callouts/` — REST sync, Queueable, retry handler, and HTTP response handler Apex templates
- `assets/platform-events/` — Platform Event definition, publisher, and subscriber templates
- `assets/cdc/` — CDC handler and subscriber trigger templates
- `assets/soap/` — SOAP callout service template and wsdl2apex guide
- `assets/endpoint-security/` — Remote Site Setting and CSP Trusted Site XML templates
### Automation hooks
- `scripts/suggest_credential_setup.py` — auto-suggests credential configuration steps when integration files are detected
- `scripts/validate_integration.py` — validates integration patterns before agent responses
---
## Output Expectations
When this skill completes an integration task, it produces:
1. **Credential metadata** — one or more files in `assets/named-credentials/` or `assets/external-credentials/` filled with org-specific values
2. **Callout Apex class** — a `.cls` file using the Named Credential pattern, with async/sync pattern chosen based on context
3. **Event/CDC artifacts** — Platform Event `.object-meta.xml`, subscriber trigger, or CDC config (when event-driven pattern is chosen)
4. **Endpoint security metadata** — Remote Site Setting and/or CSP Trusted Site XML files
5. **Scoring report** — 120-point score across 6 categories (Security, Error Handling, Bulkification, Architecture, Best Practices, Documentation)
6. **Next step** — a deployment or testing instruction for the generated artifacts
---
## Score Guide
| Score | Meaning |
|---|---|
| 108+ | strong production-ready integration design |
| 90–107 | good design with some hardening left |
| 72–89 | workable but needs architectural review |
| < 72 | unsafe / incomplete for deployment |
---
## Pre-Delivery Checklist
- [ ] Never hardcode credentials — all secrets stored in Named Credentials or External Credentials
Pliki w paczce (43)
- README.md 3 KB
- SKILL.md 9 KB
- assets/callouts/callout-retry-handler.cls 6 KB
- assets/callouts/http-response-handler.cls 9 KB
- assets/callouts/rest-queueable-callout.cls 9 KB
- assets/callouts/rest-sync-callout.cls 7 KB
- assets/cdc/cdc-handler.cls 8 KB
- assets/cdc/cdc-subscriber-trigger.trigger 5 KB
- assets/endpoint-security/example.cspTrustedSite-meta.xml 2 KB
- assets/endpoint-security/example.remoteSite-meta.xml 1 KB
- assets/external-credentials/jwt-external-credential.externalCredential-meta.xml 3 KB
- assets/external-credentials/oauth-external-credential.externalCredential-meta.xml 3 KB
- assets/external-services/external-service-operations.md 5 KB
- assets/external-services/openapi-registration.externalServiceRegistration-meta.xml 5 KB
- assets/named-credentials/certificate-auth.namedCredential-meta.xml 2 KB
- assets/named-credentials/custom-auth.namedCredential-meta.xml 2 KB
- assets/named-credentials/oauth-client-credentials.namedCredential-meta.xml 2 KB
- assets/named-credentials/oauth-jwt-bearer.namedCredential-meta.xml 2 KB
- assets/platform-events/event-publisher.cls 6 KB
- assets/platform-events/event-subscriber-action.cls 10 KB
- assets/platform-events/event-subscriber-trigger.trigger 4 KB
- assets/platform-events/platform-event-definition.object-meta.xml 4 KB
- assets/soap/soap-callout-service.cls 6 KB
- assets/soap/wsdl2apex-guide.md 6 KB
- references/callout-patterns.md 22 KB
- references/cdc-guide.md 8 KB
- references/cli-reference.md 3 KB
- references/event-driven-architecture-guide.md 10 KB
- references/event-patterns.md 27 KB
- references/external-services-guide.md 8 KB
- references/messaging-api-v2.md 18 KB
- references/named-credentials-automation.md 6 KB
- references/named-credentials-guide.md 7 KB
- references/platform-events-guide.md 7 KB
- references/rest-callout-patterns.md 9 KB
- references/scoring-rubric.md 2 KB
- references/security-best-practices.md 6 KB
- scripts/README.md 3 KB
- scripts/configure-named-credential.sh 9 KB
- scripts/set-api-credential.sh 5 KB
- scripts/suggest_credential_setup.py 9 KB
- scripts/validate_integration.py 13 KB
- scripts/templates/setup-credentials-with-csp.sh 6 KB
Wersje
W bazie nie ma innych skilli o nazwie integration-connectivity-generate.
Identyczna treść występuje jeszcze w 5 innych folderach na GitHubie. Tu pokazujemy jedną, najlepiej ocenioną kopię.
Migawka bazy z 28.10.2026 · wersja paczki 863c45c5148d (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100integration-connectivity-connected-app-configure
Konfiguruje Salesforce Connected Apps i External Client Apps: przepływy OAuth, uwierzytelnianie JWT bearer, pliki .connectedApp-meta.xml i .eca-meta.xml, z oceną w skali 120 punktów. - 100platform-salesforce-connect-adapter-generate
Generuje własny adapter Apex dla Salesforce Connect, który udostępnia zewnętrzne REST API jako zapytywalne External Objects bez ETL, z DataSource.Provider i Named Credential. - 100salesforce
Buduje integracje i automatyzacje w Salesforce: zapytania SOQL i SOSL, Apex, Flows, Lightning Web Components, API REST, SOAP i Bulk, Salesforce DX oraz wdrożenia. - 90salesforce-apex
Pisze i przegląda kod Apex: klasy, wyzwalacze, zadania wsadowe i usługi REST z limitami Salesforce i fabrykami danych testowych. - 100salesforce-webhooks
Odbiera i weryfikuje Outbound Messages z Salesforce: parsuje powiadomienia SOAP i XML, sprawdza OrganizationId i zwraca wymagane potwierdzenie; opisuje też Platform Events i Change Data Capture. - 100salesforce-integration-review-skill
Przegląda projekt integracji Salesforce pod kątem wyboru API, pozycji middleware, ponowień i idempotencji, kolejek błędów, obserwowalności, sekretów, zakresów OAuth i wzorców MuleSoft.